Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Multichannel/CLM/CreatingContent/MultiProdCLM.htm

## Supporting Multi-Product CLM Presentations

* Object Model

Content creators can assign multiple products to Multichannel Presentations (binders), Multichannel Slides, and document records created via auto-publishing. Multi-product content then generates in Vault CRM as one clm\_presentation\_\_v and key\_message\_\_v record per assigned product, ensuring accurate product information is associated with each presentation. This prevents end user media libraries from being overcrowded and makes it easier for content creators to manage and maintain the content in PromoMats/MedComms.

Each clm\_presentation\_\_v and key\_message\_\_v record in Vault CRM associates with only one product, determined by their product\_\_v fields. For example, if one Multichannel Presentation with one Multichannel Slide is assigned to five products in PromoMats/MedComms, five clm\_presentation\_\_v and key\_message\_\_v records are created in Vault CRM, one for each product.

**Who can use this feature?**

* Admin Users in PromoMats/MedComms - Browser
* [Assign multiple products to CLM content](#Assignin)
* Content Admin Users in Vault CRM - Browser
* [Sync multi-product CLM presentations](#Syncing)
* End Users - CRM Desktop (Windows), iPad, iPhone, Windows
* Users do not require an additional license

### Configuring Multi-Product CLM Presentations for

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)Admin Users in PromoMats/MedComms](#)

To allow PromoMats/MedComms admins to assign multiple products or product groups to documents:

1. Navigate to **Admin > Configuration > Document Fields**.
2. Change the following shared fields to multi-select picklists:
   * crm\_product\_\_v
   * crm\_product\_group\_\_v

   ![](../../../../Resources/Images/Multichannel/CLM/MultiProd.png)
3. Navigate to **Admin > Configuration > Document Types**.
4. Add the following shared fields to the **Multichannel Presentation** and **Multichannel Slide** document types, along with document types configured for auto-publishing:
   * crm\_product\_\_v
   * crm\_product\_group\_\_v

   ![](../../../../Resources/Images/Multichannel/CLM/MultiProd2.png)

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)Content Admin Users in Vault CRM](#)

To allow content admins to manage multi-product CLM content in Vault CRM:

1. Ensure [Configuring CLM as Object Model](../ConfiguringCLM/CLMBasicConfig.htm) is complete.
2. Ensure [Syncing Metadata Using the CRM Metadata Integration](../../../Getting_Started/CRMMetadataIntegration.htm) is configured.
3. Navigate to **Admin > Configuration > Objects**.
4. Ensure the **Values must be unique** checkbox in the Options section is deselected for the following fields:

   | Object | Field |
   | --- | --- |
   | clm\_presentation\_\_v | * presentation\_id\_\_v * vault\_external\_id\_\_v |
   | key\_message\_\_v | vault\_external\_id\_\_v |

   ![](../../../../Resources/Images/Multichannel/CLM/MultiProd3.png)

### Assigning Multiple Products to CLM Content as

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)Admin Users in PromoMats/MedComms](#)

CRM Products and CRM Product Groups can be added to CLM content via the corresponding picklists on the appropriate documents in PromoMats/MedComms.

Each presentation and all of its slides must be assigned the same CRM Products and CRM Product Groups in PromoMats/MedComms. If a presentation or its slides are assigned to different CRM Products or CRM Product Groups, a CLM sync failure occurs and the entire presentation is not synced to Vault CRM.

To assign values to Multichannel Presentations (binders) and Multichannel Slides in PromoMats/MedComms:

1. Navigate to the appropriate **Multichannel Presentation** record in PromoMats/MedComms.
2. Select **Edit**.
3. Populate the appropriate picklists:
   * crm\_product\_\_v
   * crm\_product\_group\_\_v – Represents a pairing of a CRM Product and a CRM Detail Group
4. Select **Save**.
5. Navigate to each related **Multichannel Slide** record.
6. Select **Edit**.
7. Populate the appropriate picklists with the same values selected for the Multichannel Presentation record.

To assign values to documents created via auto-publishing:

1. Navigate to the appropriate document record in PromoMats/MedComms.
2. Select **Edit**.
3. Populate the appropriate picklists:
   * crm\_product\_\_v
   * crm\_product\_group\_\_v – Represents a pairing of a CRM Product and a CRM Detail Group
4. Select **Save**.

#### Interaction of the Picklists

When migrating content from single-product to multi-product, content creators should be aware of how the picklists interact using the examples below.

The picklists interact to determine the values of the product\_\_v and detail\_group\_\_v fields of the resulting clm\_presentation\_\_v and key\_message\_\_v records in Vault CRM.

Use the crm\_product\_group\_\_v multi-select picklist to designate product-detail group pairs. Optionally, use the crm\_product\_\_v picklist to create records in Vault CRM unaffiliated with a detail group.

For example, your company has a multi-product CLM presentation with two slides assigned the CRM Products Product A and Product B. When the presentation is synced to Vault CRM, two clm\_presentation\_\_v records and four key\_message\_\_v records are created:

| Input (PromoMats/MedComms) | | | Output (Vault CRM) | |
| --- | --- | --- | --- | --- |
|  | CRM Products | CRM Product Groups | Product A Presentation | Product B Presentation |
| Multichannel Presentation | * Product A * Product B | n/a | clm\_presentation\_\_v:   * product\_\_v = Product A * detail\_group\_\_v = blank | clm\_presentation\_\_v:   * product\_\_v = Product B * detail\_group\_\_v = blank |
| Multichannel Slide 1 | * Product A * Product B | n/a | key\_message\_\_v 1:   * product\_\_v = Product A * detail\_group\_\_v = blank | key\_message\_\_v 1:   * product\_\_v = Product B * detail\_group\_\_v = blank |
| Multichannel Slide 2 | * Product A * Product B | n/a | key\_message\_\_v 2:   * product\_\_v = Product A * detail\_group\_\_v = blank | key\_message\_\_v 2:   * product\_\_v = Product B * detail\_group\_\_v = blank |

In another example, your company has a multi-product CLM presentation with two slides assigned the CRM Product Groups Product A-Detail Group A and Product B-Detail Group B. When the presentation is synced to Vault CRM, two clm\_presentation\_\_v records and four key\_message\_\_v records are created:

| Input (PromoMats/MedComms) | | | Output (Vault CRM) | |
| --- | --- | --- | --- | --- |
|  | CRM Products | CRM Product Groups | Product A Detail Group A Presentation | Product B Detail Group B Presentation |
| Multichannel Presentation | n/a | * Product A-Detail Group A * Product B-Detail Group B | clm\_presentation\_\_v:   * product\_\_v = Product A * detail\_group\_\_v = Detail Group A | clm\_presentation\_\_v:   * product\_\_v = Product B * detail\_group\_\_v = Detail Group B |
| Multichannel Slide 1 | n/a | * Product A-Detail Group A * Product B-Detail Group B | key\_message\_\_v 1:   * product\_\_v = Product A * detail\_group\_\_v = Detail Group A | key\_message\_\_v 1:   * product\_\_v = Product B * detail\_group\_\_v = Detail Group B |
| Multichannel Slide 2 | n/a | * Product A-Detail Group A * Product B-Detail Group B | key\_message\_\_v 2:   * product\_\_v = Product A * detail\_group\_\_v = Detail Group A | key\_message\_\_v 2:   * product\_\_v = Product B * detail\_group\_\_v = Detail Group B |

In a final example, your company has a multi-product CLM presentation with two slides assigned the CRM Products Product A and Product B and the CRM Product Groups Product A-Detail Group A and Product B-Detail Group A. When the presentation is synced to Vault CRM, four clm\_presentation\_\_v records and eight key\_message\_\_v records are created:

| Input (PromoMats/MedComms) | | | Output (Vault CRM) | | | |
| --- | --- | --- | --- | --- | --- | --- |
|  | CRM Products | CRM Product Groups | Product A Presentation | Product B Presentation | Product A Detail Group A Presentation | Product B Detail Group A Presentation |
| Multichannel Presentation | * Product A * Product B | * Product A-Detail Group A * Product B-Detail Group A | clm\_presentation\_\_v:   * product\_\_v = Product A * detail\_group\_\_v = blank | clm\_presentation\_\_v:   * product\_\_v = Product B * detail\_group\_\_v = blank | clm\_presentation\_\_v:   * product\_\_v = Product A * detail\_group\_\_v = Detail Group A | clm\_presentation\_\_v:   * product\_\_v = Product B * detail\_group\_\_v = Detail Group A |
| Multichannel Slide 1 | * Product A * Product B | * Product A-Detail Group A * Product B-Detail Group A | key\_message\_\_v 1:   * product\_\_v = Product A * detail\_group\_\_v = blank | key\_message\_\_v 1:   * product\_\_v = Product B * detail\_group\_\_v = blank | key\_message\_\_v 1:   * product\_\_v = Product A * detail\_group\_\_v = Detail Group A | key\_message\_\_v 1:   * product\_\_v = Product B * detail\_group\_\_v = Detail Group A |
| Multichannel Slide 2 | * Product A * Product B | * Product A-Detail Group A * Product B-Detail Group A | key\_message\_\_v 2:   * product\_\_v = Product A * detail\_group\_\_v = blank | key\_message\_\_v 2:   * product\_\_v = Product B * detail\_group\_\_v = blank | key\_message\_\_v 2:   * product\_\_v = Product A * detail\_group\_\_v = Detail Group A | key\_message\_\_v 2:   * product\_\_v = Product B * detail\_group\_\_v = Detail Group A |

### Syncing Multi-Product CLM Presentations as

[![Closed](../../../../../Skins/Default/Stylesheets/Images/transparent.gif)Content Admin Users in Vault CRM](#)

When multi-product presentations are synced to Vault CRM and created, each copy is stamped with a unique identifier (vexternal\_id\_\_v).

Since CLM presentations in Vault CRM created from one multi-product PromoMats/MedComms presentation may have the same presentation ID, the gotoSlide, gotoSlideV2, and launchSelector JavaScript methods use the product\_\_v and detail\_group\_\_v values to navigate to the correct presentation. See the [Developer Portal](https://developer.veevacrm.com/) for more information.

If a product is removed from a presentation, the sync expires the copy of the presentation, slides, and key messages created for that product. If the product is added back to the presentation, the expired records are recovered and relinked.

If a new product is added to an existing presentation, the sync creates a copy of the presentation, slides, and key messages for that product.

If a CRM product is added to an existing presentation with one PromoMats/MedComms product, and both products have the same external ID, the sync updates the existing presentation, slides, and key messages to reference the CRM product.

### Considerations

* The CLM sync ignores any product\_\_v records assigned to presentations in PromoMats/MedComms when CRM Products and/or CRM Product Groups are added. Only presentations with multiple CRM Products and/or CRM Product Groups are copied in Vault CRM.
* The CLM sync ignores any CRM Detail Groups assigned to presentations when CRM Product Groups are added
* CRM Detail Groups can still be used for single-product content
* The following information from CRM should display in PromoMats/MedComms:
* CRM Products
* CRM Product Groups – Represents pairings of CRM Products and CRM Detail Groups
* Multi-product presentations created via [auto-publishing](../ConfiguringCLM/AutoPublishing.htm#SingleDoc) are supported
* Multi-product presentations containing sub-presentations and shared resources are supported as long as one of the following is true:
* There are no CRM Products or CRM Product Groups assigned to the sub-presentations and shared resources
* All available CRM Products or CRM Product Groups are assigned to the sub-presentations and shared resources added to their linked presentations
* Multi-product presentations with assigned CRM Products and/or CRM Product Groups from different CRM Vaults are supported
* Multi-product presentations uploaded via FTP are not supported

### Related Topics

[Using Auto-Publishing for CLM](../ConfiguringCLM/AutoPublishing.htm)

[Managing CLM Syncs in the CLM Administration Console](../ConfiguringCLM/ManageCLMSync.htm)