This content and service to the Salesforce community are essential to us here at CapStorm. When it comes to helping maximize your data, we feel a sense of duty to help others solve some of the most common and complex challenges related to their Salesforce data. Join us on LinkedIn, Youtube, Twitter, or CapStorm.com!
How do you currently deploy or version your Salesforce metadata? In Episode 12 of Data Unleashed, Drew guides you through some of the processes organizations may have in place – from using changesets or manually rebuilding across orgs. But what if there was a way to automatically detect and replicate changes to your Salesforce metadata down to a local SQL environment behind your firewall?
Luckily there is a way to go about this process even today. With CapStorm, you can replicate those changes to your Salesforce metadata down to your local environment and even automatically detect those changes and have it version a metadata history for you. This means you can essentially go back in time, and identify subsets of metadata that you want to deploy across orgs. You can capture all the changes to Salesforce metadata and versions them in your database so you can employ whichever components you need.
Tune in each Tuesday for more episodes of Data Unleashed, and discover all the tips and tricks to help you get more value from your investment in Salesforce. We would love to hear from you if you are looking for a fast, easy, and highly secure way to protect your Salesforce data & metadata! Reach out to an SFDC data expert or send us a message on LinkedIn!
Video Transcription
Hi, my name is Drew Niermann, and you’re watching Data Unleashed, the video blog series dedicated to helping you get more out of your investment in Salesforce.
How do you currently version or deploy metadata? Do you use change sets? Or maybe you just manually rebuild something that you had in Org A over Org B, because it’s faster, easier than trying to find a ISV partner to partner with.
What if you had a way to automatically detect and replicate changes to your Salesforce metadata down into a local SQL environment, that is behind your firewall where you can get at that, that metadata, analyze it, deploy it, compare it, that type of thing?
There is a way to do this today. And not only does it allow you to replicate changes to metadata down to your local environment, but it automatically detects those changes in versions of metadata history for you so that you can go back in time to identify specific subsets of metadata that you may want to deploy from org A or B, it could be from prod one to prod two sandbox one to two to three, eventually up into pre-prod, prod.
But the main idea is it captures all changes to metadata, versions them in your database, giving you the ability to granularly go back in time, and deploy the entire metadata object or even just sub components of it.
If this is something that would be interested in interesting or useful to you for DevOps for org migrations or partners or splits, please drop me a note on LinkedIn, I’d be more than happy to share some resources or even connect you to an engineer that could talk to you about how this works.
And as always, thank you so much for watching Data Unleashed. My name is Drew Niermann,. have a good day.
