Duplicate Check: JSON import interface

With the import interface for JSON files, the module “Duplicate check” offers you a way to check your entire data set from your master data.

We make sure that compatibility is always maintained when extending the JSON duplicate interface. This means that you can always use the latest version without generating additional effort when integrating it into your ERP system.

In order to be able to uniquely assign a JSON data record from your ERP system in the duplicate check, you have the option of specifying up to two unique keys in the import file. These will be returned in the export file and can be used for re-import into your ERP system. However, you can also leave these two fields (key1 and key2) blank. They are not necessary for processing.

Please note that all bold fields must be specified in the import file.

Structure - Duplicate Check JSON Import File

field format example
key1 String
key2 String
firstname String
lastname String
name1 String
name2 String
name3 String
name4 String
street String
number String
postcode String
town String
department String
country String

Example in the form of a JSON file:

[
    {
        "key1":"val_key1",
        "key2":"val_key2",
        "firstname":"val_firstname",
        "lastname":"val_lastname",
        "name1":"val_name1",
        "name2":"val_name2",
        "name3":"val_name3",
        "name4":"val_name4",
        "street":"val_street",
        "number":"val_number",
        "postcode":"val_postcode",
        "town":"val_town",
        "department":"val_department",
        "country":"val_country"
    },
    {...}
]

Structure - Duplicate Check JSON Export File

The Duplicate Check JSON export file contains the previously imported data, also in the same data format unless otherwise specified. Please note that the JSON interface outputs all available fields and thus represents the most complete format.

field format example
internalid String
key1 String
key2 String
firstname String
lastname String
name1 String
name2 String
name3 String
name4 String
street String
number String
postcode String
town String
department String
country String
// cleaned data
cleaned firstname String
cleaned lastname String
cleaned name1 String
cleaned name2 String
cleaned name3 String
cleaned name4 String
cleaned street String
cleaned number String
cleaned postcode String
cleaned town String
cleaned department String
cleaned country String
// applied cleaners
applied cleaners String
// applied duplicates
duplicate ids String
address group String

In contrast to XLSX or CSV, we have agreed on the pure English notation of the Duplicate Check keys within JSON. This allows us to avoid runtime errors in the event of an incorrect conversion from the outset.

Please note that the fields in the Duplicate Check export file are not always output in the same order as specified in the table above.