When it comes to the standard integration of Smart CPQ with CRMs, the most common use case is that one CPQ instance is connected with one CRM instance.

However, it may happen that a more complex architecture is required and that several CRM instances must be connected to one CPQ instance, or the reverse, that one CRM instance must be connected with several CPQ instances.

The goal of this page is to surface the attention points to enable those scenarios.

The first scenario (1 CPQ - 1 CRM) is the one described in the standard documentation. The additional attention points for the two other scenarios are described below.

This page is related to the standard CRM integrations with Pros Smart CPQ, namely the Salesforce and Microsoft Dynamics integrations only. The specifics of each scenario below are detailed for both Salesforce and Dynamics integrations.

1 CPQ CONNECTED TO N CRM

This scenario - when supported - requires to respect the following constraints to be supported:

IDENTITY PROVIDER (IDP)

Constraint

Each CRM must be associated with one dedicated IDP, and one given user ID gives access to only one given CRM.

This implies that one person using the solution with that architecture must have one user ID for each

IDP linked to each CRM instance:

This assumption is valid whether the IDPs involved are all of the same type (for instance Salesforce IDP or Azure Active Directory only), or a mix of IDPs.

QUOTE VISIBILITY

Constraint

Sharing CPQ quotes in multiple CRM connected to the same CPQ tenant is not supported.

In this configuration, each CRM is isolated from the others. They are linked to the same CPQ tenant but are not dependent on one another. As a consequence, a quote created in CPQ from one of the linked CRM cannot be visible from the other CRM instances connected to the same CPQ.

CPQ MODELING

Constraint

Designing one quote model per CRM instance is a highly recommended best practice.

Plugging several CRM to the same CPQ instance requires from the CPQ Admin to define appropriate views and actions for each scenario. In detail, the CPQ Admin must define, in the Quote Designer, quote sync actions and / or views and / or components dedicated to each CRM instance. There could be several of those elements built for one CRM instance, but those elements cannot be shared across the multiple CRM instances. That is why dedicating one quote model per CRM instance is recommended to guarantee this isolation.

REALM

Constraint

A mix of a CRM production instance with a CPQ non-production instance, or the reverse, is not supported.

A CRM production instance must be linked to a CPQ production instance only. Similarly, a CRM non-production instance must be linked to a CPQ non-production instance only.

SYNC MECHANISM

Constraint

This restriction is in the case of the integration with MS Dynamics only

The integration of Smart CPQ with MS Dynamics can leverage two different data sync mechanisms:

• One using the standard CRM plugins
• The other leveraging an Azure function.

In the case of the Azure function, the URL of the CRM instance connected to Smart CPQ is stored as a setting of the Azure function itself and only one URL can be setup at a time.

Constraint

The Azure function mechanism does not allow the connection of several CRM instances on 1 CPQ instance.

This limitation does not apply to the plugin mechanism.

Note:

• This scenario is not supported for the Smart CPQ integration with MS Dynamics
• This scenario is not supported for the Smart CPQ for Agreements integration (including Mass Price Change workflow) on Salesforce, nor on MS Dynamics.

This scenario - when supported - requires respecting the following constraints:

CPQ URL

Salesforce specifics

The URL of a CPQ instance connected to the Salesforce CRM is stored in the CRM Custom Settings. Custom Settings can be defined at the user, profile or global levels.

The CPQ URL to be used for a given user is the one defined in the Custom Settings at the lowest level:

• The CPQ URL defined at the user level is used in priority.
• If no CPQ URL is defined at the user level, then the profile level has higher priority.
• If no CPQ URL is defined at the user or profile level, then the one defined at the global level is used.

QUOTE VISIBILITY

Constraint

As one CRM user can access only one CPQ instance (see above), the CRM and IDP Admins must make sure that one CRM user can only see the CRM quotes linked to the CPQ Quotes of his/her CPQ instance and cannot access the CRM Quotes linked to CPQ Quotes on other CPQ instances.

REALM

Constraint

A mix of realms (Prod / Preview) or types (production / non-production) for CPQ is not supported.

The multiple CPQ instances must be in the same realm and have the same type (production / non-production). Therefore, n different CPQ instances linked to the same CRM must be on the same realm and must all be production instances or must all be non-production instances.

Constraint

A mix of a CPQ production instance with a CRM non-production instance, or the reverse, is not supported.

A CPQ production instance must be linked to a CRM production instance only. Similarly, a CPQ non-production instance must be linked to a CRM non-production instance only.