Abhijit,
Currently, in the data loader mapping we can't conditionally map an attribute based on the availability of another attribute. So, the way we have solved a similar type of problem in the implementations are by creating the source file like below where we will add a new field "NPI Type" and populate the field value to "NPI" only when we have NPI ID available.
Then the data loader mapping should look like the above screenshot. So here, instead of hard coding the Identifiers.Type, We will map the field NPI Type to it. This will ensure that you will not load Identifiers Object without NPI ID.
------------------------------
Diparnab Dey
Technical Consultant
Reltio
Kolkata, West Bengal
------------------------------
Original Message:
Sent: 08-30-2024 06:18
From: Abhijit Auddy
Subject: Data loader identifier mapping
While loading IQVIA extract via data loader we found there are some records having NPI ID and some records does not.
While creating the data loader mapping for identifier, we hardcoded the Type = 'NPI' and the value=what is in NPI column of the file. As a result, it loaded the NPI value under identifier Type NPI. But for the records having no NPI value, the Type get populated as NPI with Null .
How to avoid that in data loader mapping so that if there is no corresponding value, the Type should not get populated?
------------------------------
Abhijit Auddy
Cognizant
------------------------------