CPQ
April 26, 2024
How to run a Salesforce CPQ deployment in 3 steps
Pre-made deployment templates make it fast and easy!
.jpeg){kind=avatar}
Prodly automatically maintains all parent-child relationships for you, so you never have to spend hours mapping relational data again.
Few of us get excited about tedious manual labor. That’s why Prodly created the first DevOps tool for Salesforce CPQ to automate what’s otherwise hours of manual, error-prone work. This video shows how to run a Salesforce CPQ deployment in three easy steps using our pre-made templates. Deploy CPQ records in 80% less time than manual deployment—while simultaneously eliminating errors.
Prodly DevOps comes with data set templates—think prebuilt automations—that capture the entirety of the Salesforce CPQ configuration data model. That means you can be up and running in no time. Our templates have been battle tested on over 55 million CPQ deployments.
All you have to do is make your CPQ changes in your development org, select the appropriate template—and Prodly DevOps does the rest for you. It knows all the parent-child relationships and selects them automatically for deployment. You can even deploy the entire CPQ configuration in one click using our automation templates.
You might also like: The problem with CPQ configuration data
If you like, you can even customize data set templates to add additional relationships with configuration data.
By going deeper into the data set templates, you can get really granular as to what you want to deploy and what not. Then you can preview the deployment to make sure it has everything you need in it—and nothing else.
Many of our customers say their favorite feature in Prodly DevOps is the ability to temporarily deactivate—and, importantly, reactivate—platform events and automations like Validation Rules and Flows during a deployment.
While great for running your business and maintaining data hygiene in your org, these events can cause unnecessary and frustrating deployment errors during the development process. Prodly DevOps automatically reactivates the events when the deployment is completed.
Prodly’s ability to automate this during a deployment saves you heaps of time compared to manually turning events on and off. Plus, it ensures you don’t overlook an event—which could have serious consequences.
For example, if you forget to reactivate a Validation Rule, it could result in bad data being entered into the system. Or if you forget to reactivate a Flow, it could mean that a critical part of a business workflow doesn’t get executed.
Prodly DevOps shows you in the UI how the deployment is progressing, and it sends you an email notification when it’s complete. That way, you don’t have to keep an eye on it yourself.
Do governance and SOX compliance keep you or your management up at night? Prodly DevOps provides automatic change tracking that provides an audit report of every change. This easily-generated audit report includes who made what changes, when, and why—and it can easily be sent, too. Your next SOX audit will fly by.
Without automation, deploying a change to your product catalog or other configuration data in Salesforce CPQ can be a complicated, painstaking, and time-consuming process.
For every root object, you have to migrate all the related objects–so both the parent and child objects—to ensure the configuration changed works when it is deployed to production.
Let’s say you’ve made changes to your Product object, which has dozens of parent and child relationships.
When you have to move the newly-configured Product records from your Developer sandbox or scratch org to integration, you also have to move related records in all those parent and child objects. And because Salesforce record IDs change between environments, you'll need to map IDs to maintain those relationships.
Manually.
For every single record. One object at a time.
Then you have to do it again when you move the changes to UAT. Manually. For every single record. One object at a time.
And again when you move them to staging.
And again when you promote them to production.
How long does this take? Hours, if not longer. Oh, and that’s assuming everything went according to plan and there weren’t any errors that required a do over.
See how easy it is to run a Salesforce CPQ deployment with Prodly DevOps compared to without?
Prodly is truly the best-in-class DevOps tool to enhance the benefits of Salesforce CPQ, and it offers even more brilliant features than described above! Our state-of-the-art platform includes work management integration, version control, effortless work deployment, and easy compliance.
Getting up and running is a breeze—and super fast. Plus, if you have any questions at all, our support team is rated one of the best in the industry.
Automating CPQ change delivery can enhance efficiency, reduce human error, and accelerate the deployment of new pricing models and configurations. It also ensures consistency across development environments, which improves the quality of change delivery.
To ensure the quality of CPQ data when using automation, it’s important to implement robust testing procedures including regression testing and user acceptance testing. In addition, maintain a clear audit trail of changes and approvals to help track and verify data integrity.
Prodly automatically maintains all parent-child relationships for you, so you never have to spend hours mapping relational data again.
Few of us get excited about tedious manual labor. That’s why Prodly created the first DevOps tool for Salesforce CPQ to automate what’s otherwise hours of manual, error-prone work. This video shows how to run a Salesforce CPQ deployment in three easy steps using our pre-made templates. Deploy CPQ records in 80% less time than manual deployment—while simultaneously eliminating errors.
Prodly DevOps comes with data set templates—think prebuilt automations—that capture the entirety of the Salesforce CPQ configuration data model. That means you can be up and running in no time. Our templates have been battle tested on over 55 million CPQ deployments.
All you have to do is make your CPQ changes in your development org, select the appropriate template—and Prodly DevOps does the rest for you. It knows all the parent-child relationships and selects them automatically for deployment. You can even deploy the entire CPQ configuration in one click using our automation templates.
You might also like: The problem with CPQ configuration data
If you like, you can even customize data set templates to add additional relationships with configuration data.
By going deeper into the data set templates, you can get really granular as to what you want to deploy and what not. Then you can preview the deployment to make sure it has everything you need in it—and nothing else.
Many of our customers say their favorite feature in Prodly DevOps is the ability to temporarily deactivate—and, importantly, reactivate—platform events and automations like Validation Rules and Flows during a deployment.
While great for running your business and maintaining data hygiene in your org, these events can cause unnecessary and frustrating deployment errors during the development process. Prodly DevOps automatically reactivates the events when the deployment is completed.
Prodly’s ability to automate this during a deployment saves you heaps of time compared to manually turning events on and off. Plus, it ensures you don’t overlook an event—which could have serious consequences.
For example, if you forget to reactivate a Validation Rule, it could result in bad data being entered into the system. Or if you forget to reactivate a Flow, it could mean that a critical part of a business workflow doesn’t get executed.
Prodly DevOps shows you in the UI how the deployment is progressing, and it sends you an email notification when it’s complete. That way, you don’t have to keep an eye on it yourself.
Do governance and SOX compliance keep you or your management up at night? Prodly DevOps provides automatic change tracking that provides an audit report of every change. This easily-generated audit report includes who made what changes, when, and why—and it can easily be sent, too. Your next SOX audit will fly by.
Without automation, deploying a change to your product catalog or other configuration data in Salesforce CPQ can be a complicated, painstaking, and time-consuming process.
For every root object, you have to migrate all the related objects–so both the parent and child objects—to ensure the configuration changed works when it is deployed to production.
Let’s say you’ve made changes to your Product object, which has dozens of parent and child relationships.
When you have to move the newly-configured Product records from your Developer sandbox or scratch org to integration, you also have to move related records in all those parent and child objects. And because Salesforce record IDs change between environments, you'll need to map IDs to maintain those relationships.
Manually.
For every single record. One object at a time.
Then you have to do it again when you move the changes to UAT. Manually. For every single record. One object at a time.
And again when you move them to staging.
And again when you promote them to production.
How long does this take? Hours, if not longer. Oh, and that’s assuming everything went according to plan and there weren’t any errors that required a do over.
See how easy it is to run a Salesforce CPQ deployment with Prodly DevOps compared to without?
Prodly is truly the best-in-class DevOps tool to enhance the benefits of Salesforce CPQ, and it offers even more brilliant features than described above! Our state-of-the-art platform includes work management integration, version control, effortless work deployment, and easy compliance.
Getting up and running is a breeze—and super fast. Plus, if you have any questions at all, our support team is rated one of the best in the industry.
Automating CPQ change delivery can enhance efficiency, reduce human error, and accelerate the deployment of new pricing models and configurations. It also ensures consistency across development environments, which improves the quality of change delivery.
To ensure the quality of CPQ data when using automation, it’s important to implement robust testing procedures including regression testing and user acceptance testing. In addition, maintain a clear audit trail of changes and approvals to help track and verify data integrity.
.png)