How to appropriately map object reference fields in Veeva Align using the Align Data Loader?
The purpose of this article is to explain and show how to map and match on references used in Veeva Align appropriately and how these references are working. In order to be able to view the images, left click on the images and open them in new tabs in the web browser.
Supposing we have the following simple CSV load file, the record may or may not exist:
Using the Align Data Loader - Vault UI -> Import -> Production Objects / Modeling Objects / MCCP Objects, it is either common to match on the:
1. External ID field:
2. Or the ID Field:
In the first case, Align is going to try to find the External ID field and try updating the rest of the fields of that particular record. If it is not found, the record is attempted to be created. In the second case, this is the same logic for the ID field.
Related Object References:
In the event, the following Account Territory load file is considered, which contains related object references, in this case the:
1. External ID field, the proper way to map the references:
In case the Territory and Account columns are named as: territory__alnr.external_id__aln and account__alnr.external_id__aln in the load file, these fields are automatically mapped.
2. Regarding the ID Field, the proper way to map the reference fields:
In case the Territory and Account columns are named as: territory__aln and account__aln in the load file, these fields are automatically mapped.
- This is also working the same way using Vault Loader.
- The same logic is applied to every objects in Veeva Align, which can be data loaded.
Align Help Documentation:
Vault Help Documentation: