Skip to main content

Track Changes to CPQ Rules and Revert When Necessary

A guide on how to monitor, audit, and revert changes to Salesforce CPQ configurations using Elements.cloud.

Updated over a week ago

Why track changes to CPQ configuration?

Salesforce CPQ configurations are complex and frequently modified to meet evolving business needs. Without proper tracking, even small changes to rules, pricing, or product configurations can introduce unexpected behavior, cause quoting errors, or disrupt approval workflows. Failing to monitor changes leads to:

  • Difficulty in pinpointing the root cause of issues

  • Lack of accountability for unauthorized or unintended modifications

  • Challenges in reverting to stable configurations after a problematic change

Proactively tracking changes and maintaining visibility ensures CPQ stability, speeds up troubleshooting, and enables quick reversions to previous configurations when necessary.

When to monitor and revert CPQ configuration changes?

Change tracking should be ongoing, but is especially crucial:

  • After scheduled or ad-hoc deployments to production

  • When unexpected quoting errors or pricing anomalies occur

  • Following large-scale updates to product, pricing, or approval rules

  • During audits or compliance reviews requiring change documentation

Immediate investigation and reversion are recommended when unauthorized or unintended changes are detected.

Prerequisites

Before proceeding, ensure you have:

Track and Revert CPQ Configuration Changes

Step 1: Review change notifications via daily sync emails

On a daily basis, Elements syncs your Salesforce Org. After the sync is finished, we send an automated email to users about what has changed in their Org and who made the changes.

Changes are grouped by metadata type and by user. If you see changes to ay 'records' (which means configuration records) that you weren't expecting, you can click on the link to open the detailed report and review the updated, created, or deleted configuration records.

Step 2: Investigate recent changes using custom views

From the 'what's changed' email, when you click on the given metadata type or user, you will open a list of metadata that were changed since last sync. You can see the type of metadata, type of change, when was it modified, and by whom.

When you select an item from the list, open the right panel and in the 'Changes' tab select the 'Change log' sub-tab. It will displayed all logged changes. If you click the eye icon, you can review the before and after comparison of metadata changes to understand what was altered.

Step 3: Investigate historical changes using custom views

If you are alerted to the fact that price calculations or other part of your CPQ setup suddenly stopped working as expected, follow these steps:

  1. Confirm with stakeholders when last the CPQ was working as expected and when it stopped working as expected

  2. Create custom view of metadata with following attributes:

    1. Scope: Records

    2. Columns:

      1. Parent Object

      2. Name

      3. API name

      4. Created Date

      5. Last Modified Date

    3. Filter:

      1. Last modified date: whatever you agreed with stakeholders

      2. Parent managed package: SBQQ



This way, you will see all metadata that were changed in the time period you specified, for the CPQ objects. You need to go through the list and for each record open the right panel and in the 'Changes' tab select the 'Change log' sub-tab. It will displayed all logged changes. If you click the eye icon, you can review the before and after comparison of metadata changes to understand what was altered.


Step 4: Revert to previous configurations

  1. Locate the relevant configuration record in the change log.

  2. Compare the before and after values.

  3. Manually update the Salesforce CPQ configuration to match the previous (before) values highlighted in the change log.

  4. Save and test the updated configuration to confirm the issue is resolved.

Did this answer your question?