CRM Mapping Tables

Mapping Tables in Nitro allow custom tables to be mapped from Nitro’s standard dimensions. There are multiple sources of data stored in Veeva CRM used to map to custom data sources. The demographic files from data providers, for example, Symphony & Iqvia, contain data that must be retained for reporting reasons. However, it is important to be able to display sales data at the CRM account level. These mapping tables allow linking from the source delivered dimension to the CRM standard dimension.

Map CRM Account

This table contains a row for each id stored on the account record in Veeva CRM. The fields that contain the ID in CRM must be identified in the .yml file as well as the source file. By using this structure in the dds, Nitro allows mapping external data sources to a Veeva CRM standard dimension.

Example

Copy

map_crm_account__v.yml
//existing metadata
crmExternalIdConfig:
- objectName: <OBJECT NAME>
externalIdcolumns:
- name: <NAME OF FIELD>
source: <NAME OF SOURCE>

Map CRM Product

This table contains a row for each id stored on the product record and related records in Veeva CRM. The fields containing the ID in CRM must be identified in the .yml file as well as the source file. By using this structure in the dds, Nitro allows mapping external data sources to a Veeva CRM standard dimension.

Example

Copy

map_crm_product__v.yml
//existing metadata
crmExternalIdConfig:
- objectName: product_vod__v
externalIdcolumns:
- name: external_id_vod__v
source: EXTERNAL_ID_VOD
- name: vexternal_id_vod__c
source: VEXTERNAL_ID_VOD