To match the appropriate Product references from PromoMats/MedComms to the Product records in Vault CRM, the external IDs must be specified for both PromoMats/MedComms Products (product_v) and Vault CRM Products (product__v). These Products include detail products and detail topics.

Product External IDs can be set up in two ways:

• Scenario 1: Country is used
• In PromoMats/MedComms, External IDs need to be setup for Product and Country (i.e. Cholecap External ID = 1001 and France External ID = FR)
• In CRM the Product Veeva External ID needs to be: Cholecap Veeva External ID = 1001::FR
• Scenario 2: Country is not used
• In PromoMats/MedComms, External IDs need to be setup for Product (i.e. Cholecap External ID = 1001)
• In CRM, the Product Veeva External ID needs to be Cholecap Veeva External ID = 1001

See Syncing Metadata Between Vault PromoMats/MedComms and Vault CRM for more information.

Detail Groups are disabled by default in PromoMats/MedComms. If Detail Groups are used in Vault CRM, Detail Groups must be enabled in PromoMats/MedComms.

To enable Detail Groups in PromoMats/MedComms, add the Detail Group picklist to the Multichannel Slide Document Type:

1. Navigate to Admin > Configuration > Document Fields.
2. Select Multichannel Slide.

   

3. Select Add.

   

4. Select Existing Shared Field.
5. Select Detail Group.

   

6. Select OK.
7. Navigate to Admin > Configuration > Field Layout > Property Layout.
8. Select Product Information from the list.

   

9. Select Edit and order the fields so Detail Group is first.
10. Select Save.

To define Detail Groups in PromoMats/MedComms:

1. Navigate to Business Admin > Picklists > Detail Group.

   

2. Select Edit to add new Detail Groups. Do not delete the Common entry. This is required to map to the default Common group delivered in Vault CRM. The key of the picklist value in PromoMats/MedComms must be populated in the vexternal_id__v field on the Detail Group Product record. For example, the picklist value Neurology in PromoMats/MedComms creates the picklist key neurology__c. This key should be entered in the vexternal_id__v field for the Neurology Detail Group record in Vault CRM.

To map fields:

1. Navigate to CRM Set > Content Setup > CLM.
2. Select View Mapped in the Vault Connection Management section to review the fields involved in the CLM integration with PromoMats/MedComms.

   

3. Select Compare CRM to Vault any time one of the following occurs:
   • Set up a new integration
   • Changes you want to reflect in Vault CRM are made to CRM Rendition Settings in PromoMats/MedComms
   • There are updates to the mapped fields, for example, adding a custom field

     Out-of-the-box PromoMats/MedComms fields cannot be mapped to custom Vault CRM fields.

4. Select the Show Mapped option from the CRM Fields drop-down list to view a condensed list of clm_presentation__v and key_message__v fields with a field match between Vault CRM and PromoMats/MedComms. The Show All option displays a full list of clm_presentation__v and key_message__v fields. Show Mapped is the default value.

The System CLM Fields section lists the core CLM fields for the clm_presentation__v and key_message__v objects. Certain fields do not have a PromoMats/MedComms field match but are still used in integration. Cannot Map displays in the Vault Field Label column for these fields. The Optional CLM Fields section lists custom fields as well as unrelated and/or depreciated fields for the clm_presentation__v and key_message__v objects.

When comparing Vault CRM to PromoMats/MedComms for a Single-Doc or All connection type, Vault CRM identifies the document types specified within the active CRM Rendition Settings in PromoMats/MedComms. This allows the integration to map fields available on any of the document types. The Vault Doc Type column displays which document types apply for system-mapped and optionally-mapped fields. The Vault field permission column lists field permissions with respect to Vault Doc Type display order. PromoMats/MedComms admins should ensure the appropriate multichannel fields are available on document types defined within the CRM Rendition Settings in PromoMats/MedComms. Refer to the Vault documentation for more information.

Content admins can define custom mapping between Vault Object Framework (VOF) records and fields and Vault CRM fields. For example, you need to map a Country VOF lookup on a CLM document in PromoMats/MedComms to a custom text field on CLM records in Vault CRM.

To define a custom field mapping:

1. Select Edit Mapping.
2. Select the appropriate PromoMats/MedComms field from the Vault Field Name dropdown menu for the Vault CRM field you want to map.

   

3. Select Save Mapping. Review eligible mappings to ensure they are correct.

By default, the integration maps fields between Vault CRM and PromoMats/MedComms with matching field names. Select do not map if the field names match between the PromoMats/MedComms and Vault CRM fields, but you do not want values from the PromoMats/MedComms field to be synced to Vault CRM. This is used when a mapping is no longer relevant to the integration, but the fields are still accessible in PromoMats/MedComms and Vault CRM. Select the blank entry if you do not want to make any other selection.

The following table includes common field mapping errors and how to fix them:

There is the potential for incomplete data because of mismatched field lengths or ability to select multiple VOFs in PromoMats/MedComms. If the Vault CRM field character length is less than the PromoMats/MedComms character length, and/or if Allow user to select multiple values is true on the VOF, then a warning icon displays next to the Vault Field Type.

The warning indicates a potential for truncation if the PromoMats/MedComms field length exceeds the Vault CRM field length. For example, if a PromoMats/MedComms field supports up to 25 characters and is mapped to a Vault CRM field that supports only 20 characters, the warning icon displays. If the PromoMats/MedComms field contains a 25-character value, only the first 20 characters are inserted into the Vault CRM field when the sync runs.

In Vault CRM, the cdn_path__v field on the key_message__v object is limited to 255 characters. If the CDN file path for a key message containing a long file name exceeds 255 characters, the file path is truncated when the content is synced from PromoMats/MedComms, which causes errors when end users present content.