This content and service to the Salesforce community are essential to us here at CapStorm. However, 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!
Most Salesforce admins are familiar with the Field History Tracker feature, but did you know there are ways around the limits to tracking field changes? In this week’s episode of Data Unleashed, Drew goes over how CapStorm’s solutions offer limitless tracking. This can come in handy if you’ve ever had to deal with disgruntled employees or other incidents where field data changes.
With CapStorm, you can work around the operational limitations of 20 fields per object by replicating the data model in Salesforce down into a local SQL database – everything from data, metadata, and schema. All of this happens in real-time, around 3 minutes. This offloads the field history tracking to the SQL layer, allowing you to keep track of all the changes. What you end up with is a limitless, exhaustive Field History Tracking solution.
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. In addition, 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! Contact an SFDC data expert or send us a message on LinkedIn!
Video Transcription
Hey, 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.
Today we’re going to talk about a common Salesforce feature called Salesforce field history tracking. If you’re a Salesforce administrator, you probably know what this is already. And my guess is that you’re also probably aware that you can track up to as many as 20 fields per Salesforce object. But what if you have a disgruntled employee that’s about to change jobs, or that one sales rep that’s notorious for inflating pipeline, changing the amounts or reverting stages on an opportunity for monthly forecast reviews. Either way, it can be common to hit a limitation on those 20 fields per object.
But there is a way to work around that. And we’re going to share a bit of a tip from Capstone today. So with CapStorm, you can actually work around this operational limit of 20 fields per object by replicating the data model Salesforce down into a local SQL database that includes data schema and metadata. And with a near real-time copy, within three minutes of real-time, have your entire data model in your own database that you can offload the auditing or the field history tracking to the sequel layer as often as every three to five minutes.
So it’s an incremental pull constantly taking, keeping track of all the changes that are made in Salesforce, and giving you the ability to use your own storage and compute to run your own queries against that database. So what you end up with is basically a limitless or exhaustive field history tracking feature. If this is something of interest to you, please shoot me a note on LinkedIn.
My name is Drew Niermann, or send one of our experts on notes at www.capstorm.com. Thank you so much for watching Data Unleashed.
