The Use Case: The Need for Better Field History Tracking
While the possibilities can be nearly endless, custom development can take a lot of time, and leave your client with more technical debt than they can handle once you’re gone. Time is typically your most valuable resource when on a project cycle, and every hour you save can be precious. In any line of consulting, building off an already great idea can be a great way to avoid starting from scratch. Whether it’s using reusable code, pulling from past experience, or adding your own improvements to a problem someone else has already solved, there are many ways to leverage Salesforce features to extend functionality.
In a recent use case, a client needed the ability to track when fields in Salesforce were changed, and by whom. While your first guess might be to just turn on Salesforce’s built in field history tracking, the standard functionality wasn’t enough. Unfortunately, some areas of Salesforce have less wiggle room when it comes to customization, and field tracking is one of them.
Our client needed the ability to go back into history logs and edit historical data. This isn’t a common use case, but it was a necessity that the client have the tools to do so. While creating a custom solution, we had to do so in a way that was dynamic and easy enough to maintain, as well as friendly enough to mass import hundreds of thousands of historical records from a legacy system.
Starting from ground zero, a custom solution that meets all these requirements could take several resources and time that may have been needed elsewhere. Luckily, half the work was already done for us. Salesforce already had a tool that did nearly everything we needed. So, what if we took their ideas and added a few layers of our own on top?