Back to the blog

bug.pngA SOFTWARE BUG WALKS INTO A PRODUCTION BAR...

About 15% of bugs created during software development end up in Production[1]. This alarming number is only shadowed by the fact that this statistic has not changed in the past 25 years. If you ask developers or QA engineers why this happens, you’ll realize that most of the time, it’s to do with differing data sets in production versus the testing environments. They just don’t match.


WHAT IS DATA REPLICATION?

To overcome this challenge, developers and QA engineers find themselves replicating data to testing environments. Usually this involves multiple data export, movement, and upload steps, expending precious time on an often complex and error-prone process.

WHO NEEDS DATA REPLICATION?

 

Anyone who is developing new capabilities and testing them before they get to the production environment will benefit from test data replication. Typically with software development, it’s a combination of the developers and the QA engineers that want to test new features or integrations to other products who will appreciate the benefits afforded by data replication: fewer errors and less test preparation time.

With Salesforce,  Administrators also find it necessary to test their ‘developments’ before they ‘release’ them into production. These may include reports, dashboards, smart workflows and validation rules that “save” development efforts and to name a few! I will never forget the time, as a Salesforce Consultant, that I made changes in a report on a client’s production environment. Not five minutes later, I had three angry finance department users knocking on my door asking for my head. Luckily, I had a backup and could fix my mistake within minutes. Had I actually used a sandbox with proper test data, this drama would have been averted.

HOW DOES OWNBACKUP DATA REPLICATION WORK?

Like other OwnBackup capabilities, the replication feature is focused on the user, keeping it simple and at the same time enabling complex actions.

Using the OwnBackup Replicate tool is powerfully simple:

  1. Choose the source environment.
    • Choose the data set you want to replicate: You can choose multiple-objects or the entire data set.
  2. Choose the backup snapshot
    • This enables you to copy data from the past - not only the current version! Unlike a “restore” operation, there is no driving data corruption/loss event. In fact, there may be nothing to ‘fix’ at all. You  simply want to copy data from one environment, to another. The ability to choose a past snapshot is a unique convenience of the OwnBackup solution.
  3. Choose the destination environment.

That’s all it takes. You’ll then be presented with the details object subset to be replicated and you may make some final tweaks to the replication job as desired. These may include: removing unwanted objects, or even changing the amount of replicate records per object.



SUMMARY:

I wish I had a great story about how I had this brilliant product innovation revelation while hiking through a desert mountain. But in truth, how we came up with this great capability is much more mundane, and far more important. We listened to our customers. We listened as they described their data management pain. When we heard again and again about bugs making it into production and the pain of testing everything, we knew it was time to start building a replication capability! We knew we could help every Salesforce administrator, developer and QA engineer by making it fast and easy for them to test anything and everything.

SEE OWNBACKUP REPLICATION FOR YOURSELF:


If you would like to learn more about the OwnBackup Replicate capabilities, please watch our Replication Demo Webinar, request a demo: REQUEST DEMO , or even sign-up for a 14-day trial:  14-DAY FREE TRIAL


We pride ourselves being a customer-first company. Feel free to contact us with any feedback you have about our products or services: info@OwnBackup.com

 

 

 

 

 

 

 

 

 

[1] Capers Jones, SOFTWARE DEFECT ORIGINS AND REMOVAL METHOD, 2012