You are here:
< Back

Introduction

Matchbook Services “Import Data Process” allows you to import data using the below options. Both Admin/Data Steward users will be able to import data into Matchbook Services and the data import validation process will always assist the users while entering any invalid data or connections.

Import Data Details

To process records through the Matchbook Portal, users must import their data (records) either through the portal, command line, or the REST API interface. Users have two different import options via Portal using multiple file formats:

  • Cleanse, Match and Enrichment
  • Enrichment only

Users can check the status of all the files brought into the portal in the Import Data section. It contains File Name, Import Type, Requested Date, Status, Message, and Error Message:

Key Information related to the Data Import Process

  • Both Admins and Data Stewards can import data
    • There are two types of administrators:
      • Enterprise Admin – have access to the complete system’s rules and data, and can import data belonging to any LOB defined within the system
      • LOB Admin – have access only to their LOB’s rules and data, and in turn, can only import data related to their specific LOB group
  • Data Validation takes place before data is loaded into the portal:
    • Country Standardization – Country field data is standardized to a 2-character ISO code required by the D&B Cleanse Match API
    • De-duplication within a loaded file – This process occurs at the SrcRecordId level and works by using the last imported record within the file

In the same file, the following details exist in the order presented below:

RecordID
ImportProcessId
SrcRecordID
Company Name
#1 1 ABC123 Company1
#2 1 DEF123 Cmp2
#3 1 ABC123 Company3

 

In the example above, records #1 and #3 would be considered duplicates. Both have the same SrcRecordId (ABC123), although the company names are different. During the import process, the only records that would be imported are records #2 and #3. Record #1’s data would not be imported into MBS.

**Note: It is imperative that all the imported records have a unique SrcRecordId**