Salesforce CPQ data is data that wants to be metadata, and at Salto, we treat it as such. But this goes beyond CPQ deployments and comparing CPQ data across different orgs.

Sometimes you need to find the right configuration before you can make changes to it, or sometimes you need to find where a CPQ field is used (if you know Salesforce CPQ, you know of the horrible strange practice of hardcoding field API names as picklist values or text fields…).

And here's where Salto’s 100% FREE tier comes in. You can use it to find hardcoded CPQ field values, hardcoded Ids and find relationships and dependencies between CPQ data.

Let’s see how!

‍

‍

‍

Enabling Salto for Salesforce CPQ

First, make sure you enable Salesforce CPQ in your Salto environment. You’ll see the “Include CPQ” checkbox when you create a new one

‍

‍

If you have an existing Salto environment and want to enable CPQ for it, the easiest way to do so is to delete the environment and create it again and tick the checkbox mentioned earlier. If you are using Salto for CPQ deployments, don’t do that! Contact us instead 🙂 

‍

Browsing your Salesforce CPQ Data

Now that you’ve enabled CPQ for your Salto environment, you can find all your CPQ data in the Element Tree, just alongside your Salesforce metadata

‍

‍

From here, you can open up any CPQ record and see its details in a low-code UI

‍

‍

In the example above, I can see a Configuration Rule. Clicking the tiny cloud icon will open the record in your Salesforce org.

‍

Where is this used for Salesforce CPQ

You may be familiar with the “Where is this used?” functionality that Salesforce provides for custom fields, which allows you to see where a custom field is referenced in the org metadata.

With Salto, you can do the same for CPQ data. This time let’s look at a Product record.

‍

‍

Here I can see the Product is used in 3 places in my Salesforce CPQ data: a Configuration Attribute, a Configuration Rule, and a Product Feature.

This way, you know if you are making a change to this product, what other areas of your org could be impacted. 

‍

Finding Hardcoded Values

Salesforce CPQ heavily relies on using the API name of custom fields on configuration data records. For example, see the below Configuration Attribute

‍

‍

Because the field name Usable_Capacity__c is simply a string, there's no way for the standard "Where is this used" button to reveal that this field is used here.

What this means is if you change some attribute of this field, you could impact a ton of Salesforce CPQ configuration data, and you wouldn’t know until the logic fails at run-time. 

This is not a problem in Salto because you can simply search for the field API name and we'll reveal its usage, whether its metadata or configuration data. Just search for the field API name and click the Content tab.

‍

‍

In the example above, I can see the field is being used in a Configuration Attribute. 

The same applies to any Salesforce CPQ object that has SBQQ__TargetField__c and SBQQ__TargetObject__c fields. You can find where these fields and objects are used by doing a simple text search.

‍

‍

Search anything else

And that’s it! Remember with Salto’s free tier, you can also search anything else in your org, such as hardcoded IDs, email addresses, URLs, and anything in between. 

‍