Files structures of DnB Connector Mapping

The connector uses mapping files to convert DnB responses to Reltio entities. Also, the connector converts Reltio entities to a set of parameters that are passed to DnB in a request.

The following Table1: Required files lists the type of files that are used in mapping.

Table 1. Required Files
Name Direction Description Result
batch.json In This file converts a list of CSV to JSON formatted entities to list the Reltio entities with required attributes and hierarchy entities. [[GU, DU, HQ, Trg], [GU, DU, P, Trg], [Trg], …]
batch_plus.json In This file converts DnB Direct+ batch response item to Reltio entities with all required attributes and hierarchy entities. [GU, DU, Trg]
corporate_linkage_upward.json In This file creates a list of the upward hierarchy tree. [FT member, FT member, FT member, Target]
corporate_linkage_upward_plus.json In This file creates a list of upward hierarchy tree for Direct+ [FT member, FT member, FT member, Target]
enrichment.json In This file converts DnB response to Reltio entities with all required attributes and hierarchy entities [GU, DU, HQ(Parent), Target]
enrichment_contact.json In Not used --
enrichment_plus.json In This file converts DnB Direct+ response to Reltio entity with all required attributes and hierarchy entities [GU, DU, HQ(Parent), Target]
filter.json Out This file extracts attributes that will be passed to the DnB in match request. It can contain any additional user-defined parameters { “x1“: “z1“, “x2“: “z2“, …}
filter_plus.json Out This file extracts attributes that will be passed to the DnB in Direct+ match request. The file can contain any additional user-defined parameters. { “x1“: “z1“, “x2“: “z2“, …}
match.json In This file converts DnB response to the list of Reltio entities with all required attributes. The Reltio entities are sent to Data Tenant as potential matches. [Potential Match1, Potential Match2, …]
match_plus.json In This file converts DnB Direct+ response to the list of Reltio entities with all required attributes. The Reltio entities are placed to Data Tenant as potential matches. [Potential Match1, Potential Match2, …]
update_status.json In Represents the service mapping file. The file is used for switching between nested and simple VendorVerificationStatus and VendorVerificationDate attributes. Reltio entity with flag attributes only. The connector set partialOverride as true.