Tag Archives: data deployment

An vector diagram depicting running a Salesforce CPQ deployment

How to Easily Run a Salesforce CPQ Deployment

Learn how to easily run a Salesforce CPQ deployment using Prodly’s automation templates. It takes 80 percent less time than manual deployment—while simultaneously eliminating errors.

Automate Salesforce CPQ Deployments

Few of us get excited about tedious manual labor. That’s why Prodly created the first DevOps tool for Salesforce CPQ to automate what is otherwise hours of manual, error-prone work. 

Here’s how to easily run a Salesforce CPQ deployment with Prodly’s automation:

  1. Select where the ready-to-go changes are and where they need to go—whether that’s the next org in your release path or a branch in your repository.
  2. Select whether all of CPQ needs to be deployed or just a part of CPQ (i.e. all Price Rules or a new Product)
  3. Deploy.

Prodly’s Salesforce CPQ Automation Features

Proven Templates for the Entire CPQ Configuration Data Model

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.

Customize Data Set Templates

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.

Temporarily Deactivate Platform Events in Salesforce

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.

Progress Report

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.

Audit History

Does 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.

Promoting CPQ Configuration Data Changes Without Prodly

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.

The Market-Leading Salesforce CPQ DevOps Tool

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.

Discover how Prodly DevOps can streamline your Salesforce CPQ instance and accelerate your digital transformation!

Streamline Salesforce CPQ deployment

Prodly Boosts Salesforce CPQ Data Deployment

In this blog, we explain how Prodly accelerates your Salesforce CPQ data deployments.

Boost Salesforce CPQ Deployments

With Prodly, you can quickly and easily deploy Salesforce CPQ data to production.

Created by the team that developed Salesforce CPQ, Prodly is the # 1 data migration tool for Salesforce. It streamlines the process of deploying Salesforce CPQ configuration data for seamless release management. 

With Prodly, you can deploy changes 66 percent faster than other solutions. What’s more: You can ramp up productivity by an astounding 80 percent!

Prodly streamlines Salesforce CPQ deployments because it offers several distinct benefits for users.

Streamline Salesforce CPQ deployment

Its Algorithms Are Optimized for Salesforce CPQ Data Migration

We’ve been perfecting our data deployment algorithms since 2015. Although Prodly was originally developed as a tool to streamline Salesforce CPQ deployments, we’ve developed our tool so it can be used with any Salesforce application. It’s still our core focus and main product.

It’s also important to note that we’re the only company in this space that originally focused on data. Other companies began with metadata and have only recently started to build out their data capabilities. As such, Prodly’s data migration capabilities are much more advanced.

It Provides Full Support for Any User From Start to Finish

Prodly is extremely user-friendly. It’s easy to navigate for admins and revenue operations, yet robust enough for developers. It’s a “clicks, not code” tool with a powerful DX plugin that allows you to move all data within Salesforce, without limits. 

Prodly offers fully automated data deployments, even for highly complex, Salesforce CPQ object models. It automatically determines the correct sequence for multi-object data loads. You don’t need any knowledge of CPQ schema, so everyone on your team can use the tool.

It Knows Which Records to Insert and Which to Upsert

Prodly makes sure your data upserts correctly. Automatic record matching understands the relationships between your records and maintains them in the destination org. This prevents duplicates. 

Recursive processing takes multiple passes through the data to make sure it updates with the correct information. Sometimes this requires the addition of a temporary value so the record can upsert. Later, Prodly goes back and updates the record to the real value.

For example, Price Rules of the type “Custom” require child conditions. So Prodly is smart enough to create Price Rule records in the default type and insert child condition records. Then it goes back and updates the Price Rule records to Custom.

With Lookup relationships and hardcoded IDs, Salesforce stores a record ID. This record ID changes in the destination org, which breaks the relationship between records. Prodly determines which record matches in the destination org and simply updates the IDs accordingly.

It Offers Superior Functionality for Every User Without Compromising Ease of Use

Prodly is completely reliable for Salesforce CPQ deployments. The Diagram View allows non-technical users to easily see what’s being moved. You control all settings down to the field level with a single click. 

It provides pre-built templates that empower you as your needs mature. You can even customize the templates so they’re specifically geared towards your needs.

It Offers Peace of Mind During Development From Start to Finish

Prodly lets you securely move any data to any org within Salesforce. It provides one-click data masking, as well as automatic duplicate, override, and error prevention. 

Prodly also offers easy Git integration for source control because it’s critical for commerce businesses to be SOX compliant,  This helps you enhance your governance and release process with version control.

When to Choose Prodly for Salesforce CPQ Deployments

Prodly is best used when you need to migrate large volumes of highly complex relational data. This occurs frequently in Salesforce CPQ. Just consider how often you need to make changes to reflect factors like seasonal promotions, sales in new territories, etc. And then consider across how many different products or artifacts you need to make those changes.

Clearly, you need a powerful Salesforce CPQ deployment tool that lets you focus on making the changes to the data. 

To see Prodly in action, request a personalized demo. 

The problem with Salesforce CPQ configuration data deployment

The Problem With CPQ Configuration Data

In this blog, we’ll examine the issue with deploying Salesforce configuration data and discuss why deploying metadata is easier. We’ll explain why Salesforce managed packages use configuration data in the first place—plus, we’ll mention how to streamline Salesforce CPQ configuration data deployment.

The problem with Salesforce CPQ configuration data deployment

The Issue With Deploying Configuration Data in Salesforce

Configuration data, or reference data, achieves a specific functionality in a Salesforce app. It’s like metadata in that it describes how the system behaves. However, it’s stored as transactional data in Salesforce’s databases. 

Because Salesforce doesn’t have tools to manage reference data, it’s critical for Salesforce CPQ users to understand why it exists and how it works.

It becomes particularly challenging when you need to promote many changes with complex relational data from a sandbox to production. You can’t use change sets, because they only work for actual metadata types.

You can use Data Loader–but that can be a laborious, lengthy, and painstaking process. Especially when you have a high volume of complex relational data, like in Salesforce CPQ, you can spend hours mapping objects. And that’s before mistakes and do-overs.

Why Is Migrating Metadata Easier?

In Salesforce, metadata is native to the platform. Salesforce can create new types of metadata when needed and has hundreds of types of metadata to power its applications.

For example, Salesforce created Einstein bots—with dialog as a new custom metadata type within the platform. 

Once the dialog was added as a metadata type, customers could develop their own bots in a sandbox. Then they could define the bots’ interactions with end-users based on the dialog metadata provided. 

Now, when they wanted to deploy those bots from a sandbox to production, they could simply use change sets. Why? Because the metadata types are already included in org migration tools that the platform provides. 

Why Does Salesforce CPQ Use Configuration Data?

If deploying metadata is relatively easy, why do some Salesforce apps use configuration data?

The answer is simple. Many apps are made by Salesforce App Partners (otherwise known as ISVs) who don’t have the ability to create new types of metadata. So when they want to specify behaviors in their applications, they need a solution. That’s where configuration data comes in.

Configuration data are records that serve as the code used by managed packages to produce some type of application behavior for applications built on Salesforce. 

For example, Salesforce CPQ is an AppExchange product originally created by Salesforce App Partner, Steelbrick. Even after Salesforce acquired Steelbrick, you still need to install the CPQ managed packages in your org to gain access to its many powerful features and functionalities.

One of these functionalities is Price Rules—conditions and actions that update prices. However, when Steelbrick developed Price Rules, it wasn’t an option to create a new type of metadata like with our Einstein dialog example. So they needed a different solution. 

Instead, they developed Price Rules as a custom Object made with configuration data. 

However, when you, the user, make changes to Price Rules, you can’t use change sets to promote those changes to production. Because they’re configuration data, you need to promote them as data.

Read Prodly Accelerates Salesforce CPQ Data Deployment to discover how to do this quickly and easily. 

Skyrocket salesforce data deployment with Prodly AppOps

Skyrocket Salesforce Data Deployment With Prodly

Discover a Better Alternative to the Salesforce Status Quo

Skyrocket salesforce data deployment with Prodly AppOps

Salesforce is a comprehensive platform to manage your marketing, sales, and customer support processes. But when it comes to change management, traditional Salesforce data deployment tools have their drawbacks. And those drawbacks can threaten your business progress. 

Perhaps you’re thinking, “But we’ve always done it this way. Why should we change?” The answer is simple: To streamline and ramp up your change management process.

Current Salesforce Data Deployment Tools Are Problematic

Just think about it: How many times have you had to delay adding a new feature or flow due to issues with Data Loader or change sets? These tools might be free, but they’re also labor intensive, error prone, and time consuming. So if you want to use them for a time-sensitive project, you’ll need to add headcount to meet your deadline. 

Of course, developers are known for their ingenuity, and many write their own scripts for promoting data through the release chain. This can certainly save them hours on an individual data migration project. 

But the time investment needed to initially write the script and subsequently maintain it can be considerable—and take them away from their core work. Not to mention, every script is unique. That can create problems when syncing all the changes in a shared sandbox, leading to hours of troubleshooting. Is this really the best use of developers’ time?

Alternatively, you can use a Full Copy sandbox to recreate your production org. However, that’s often cost prohibitive. Plus, a Full Copy sandbox doesn’t refresh frequently enough to be an actual reproduction of your production environment. The resulting data degradation can even have a negative effect on the project.

The final option is to outsource your projects—but that’s expensive. Moreover, contractors don’t have the knowledge of your business that your own team has. This can result in errors and delays. On top of that, if you need to change or fix something after the contractor has delivered the work, it can rack up additional costs. 

Accelerate Salesforce Data Deployment With Prodly

Fortunately, there’s a better way to do things. Our low-code Prodly DevOps suite automates Salesforce data deployment while maintaining complex relationships. Thanks to its top-notch automation, it offers significant time savings.

In fact, it reduces data migration time by 85 percent and is 12 times faster than change sets. On top of that, it eliminates the need to write and maintain custom scripts. This results in significantly faster, 100% accurate release processes that can be managed by both declarative and programmatic users. 

Our solution lets you rapidly move data up and down the pipeline, as well as to parallel orgs. You can use either the production environment or a VCS as the source of truth. 

For metadata deployments, Prodly provides automatic duplicate prevention. It also provides versioning and conflict resolution with a rollback feature.  

When it comes to metadata migration and deployments, the Prodly DevOps suite allows you to visually compare orgs. You can also leverage the subcomponent drill-down point-and-click feature.

Check out this table to see how Prodly outperforms Data Loader, change sets, and custom scripts.

Prodly AppOps vs change sets, dataloader, and custom scripts

Drive Your Business Forward with Prodly DevOps

With the powerful Salesforce data deployment tools Prodly provides, you can keep your projects on track and significantly ramp up velocity. 

You can save literally hundreds of employee hours on frustrating, headache-inducing manual labor—and let your team get right down to what they do best. As a value add, you can unburden your employees and increase their job satisfaction, which in turn improves retention. 

Combined, these factors will make your organization more agile—and help propel your business forward.  

Get in touch

Templates simplify Salesforce CPQ data deployment

Templates Simplify Salesforce CPQ Data Migration

Using templates can significantly simplify the data migration process in Salesforce CPQ. In this blog, we’ll discuss the challenges associated with remapping lookup relationships. We’ll also explain how Prodly makes this process easier, faster, and more accurate. 

Why You Need Pre-Made Data Set Templates

There are 45 Salesforce CPQ reference data objects. It’s fiendishly difficult to deploy them from staging to production. The biggest challenge is remapping the lookup relationships among records in the destination org. Going back and forth with a data loader and spreadsheet is extremely tedious.

Prodly is purpose-built to solve this issue. It automatically reestablishes the source record relationships in the destination org. But there are still other challenges to quick and easy CPQ Salesforce data migration.

It’s time consuming to build a data set that involves dozens of Salesforce CPQ reference data objects, even for an expert. The first time around, it can take two weeks to perfect a Prodly data set for Salesforce CPQ reference data migration. 

Templates simplify Salesforce CPQ data deployment

This is time that most implementation consultants and in-house Salesforce CPQ admins would much rather spend on other things.

Another issue is establishing external IDs for every object to support updating records without creating duplicates. Salesforce CPQ doesn’t come with external IDs. That means implementation teams have to add them themselves.

So what to do? How about using our new pre-configured Prodly data set templates? They’re specifically designed for Salesforce CPQ. You’ll save a ton of time and avoid errors.

Salesforce CPQ Data Migration Templates From Prodly

Prodly has developed a suite of 16 data set templates that cover every aspect of Salesforce CPQ’s reference data—all 45 objects. This was with the help of Gilles Muys, former head of professional services at SteelBrick, now VP of Customer Solutions at Simplus. In addition, it was with demo data provided by the Salesforce CPQ team.

These templates are available at no charge to any Prodly user.

You can easily access the templates from GitHub. You can also download them as a zip file from the Prodly Resources page on our website.

The templates use the standard JSON file format, and you can import them into Prodly with a few clicks. Once you’ve installed them, you’ll see that all the object relationships are preconfigured. Additionally, composite external IDs are assigned to every object.

We’ve also developed the Prodly Salesforce CPQ Data Migration Guide. This is a comprehensive document that provides a detailed explanation of how the data sets are configured.

For more details about the templates, request a personalized demo.