Use PDIs? Take our 5-minute survey to help shape the PDI roadmap.

Salesforce Integration in SAM Pro Issue

DiotimaB8945053
Mega Contributor

Hi All,

I have been facing an issue with Salesforce since we recently integrated Salesforce CRM Subscription data into SAM Pro.

I reviewed the list of known Salesforce CRM Subscription Product Definitions (PSL identifiers) and found confirmed matches for 13 out of the 16 identifiers.

When I open each Salesforce CRM Subscription integration profile, I can see the software models associated with the profiles. There are approximately 13 software models that currently do not have entitlements associated with them. My assumption is that these products are bundled under the Sales Cloud Agentforce subscription.

To address this, I attempted to create suite component relationships by adding the individual software models as components under the Sales Cloud Agentforce suite model. However, after running reconciliation, the component products continue to appear as separate software models and are not being recognized or consumed as part of the Agentforce suite.

Could you please advise on the correct approach to handle this scenario?

Specifically:

  • Is creating suite component relationships the correct method for Salesforce CRM Subscription integrations?
  • Are there any additional settings required for the suite model to consume the component software models during reconciliation?
  • Should the software models be linked through a different relationship type or consumption rule?
  • Is there a recommended configuration for Salesforce PSL-based subscriptions to ensure the products are recognized as part of the Agentforce entitlement?

Any guidance on the required steps to correctly model and reconcile these subscriptions would be greatly appreciated.

 

4 REPLIES 4

MikeW0609686430
Giga Guru

One thing I do know is that for subscription software models, there currently isn't a solution for bundling suite components. I've encountered this issue before with Salesforce.

Maniteja_2003
Tera Guru

Hi @DiotimaB8945053,

 

I hope my answers helps.

 

Q1: Is creating suite component relationships the correct approach?
A: If the organization has purchased only the Sales Cloud Agentforce subscription and the remaining Salesforce products are included under the same contract, then creating Suite Components would be the correct approach.

 

Note: Make sure the Parent Software Model is correctly mapped to the corresponding Entitlement and that all the products are licensed using the same licensing metric.

 

Q2: Are there any additional settings required for the suite model?
A: Ensure that the Apply to Subscriptions checkbox is selected for the Software Model (applicable to subscription software). Also, make sure that the Inference Number or Inference Percentage is populated.

 

Q3: Should the software models be linked through a different relationship type or consumption rule?
A: In most cases, creating a Suite Model should be sufficient to calculate the license consumption of different Software Models under a single suite. Additional consumption rules should not be required.

 

Q4: Is there any other recommended configuration for Salesforce PSL-based subscriptions?
A: In my view, no additional configuration should be required. Properly configuring the Entitlements, Software Models, and Suite Model relationships should be sufficient for the subscriptions to be recognized and consumed correctly.

 

Regards,
Maniteja.

Thanks @Maniteja_2003 , this would be really helpful for other users facing issues with SaaS bundles. The software model attribute “apply to subscriptions” is the key adjustment.

 

best, Dennis 

Should my response prove helpful, please consider marking it as the Accepted Solution/Helpful to assist closing this thread.

MikeW0609686430
Giga Guru

Unless there has been a recent enhancement, the reconciliation engine doesn't take into account suite components for subscription software models. The best way of addressing this is to create individual software models for all of the models created via the integration and create dummy entitlements for each of the models based on the quantity of the Sales Cloud Agentforce subscriptions in the agreement. I would then create a contract record for the  Sales Cloud Agentforce contract (referencing the full cost of the subscription agreement) and link the entitlements to the contract.