When you have too many cooks in the kitchen, managing a Salesforce environment can get messy. Just like at a popular restaurant during the dinner rush, it is easy for things to get overlooked. “Excuse me Miss, but I asked for the dressing on the side.” As Salesforce Administrators, in the rush to satisfy our Salesforce users, it can be easy to miss details, especially when under tight constraints to complete multiple projects at once.
Whether a server forgetting to make sure the dressing is on the side, or an administrator forgetting to make a newly created field accessible to a particular profile, these issues drain efficiency. It can be downright frustrating having to go back and correct something when we would rather be moving on to our next task.
Fortunately, these minor errors do not usually take too much time to correct. A server can return the salad to the kitchen and come back quickly with another and a SIDE of dressing. A forgotten field permission can also quickly be corrected. As shown below, I can quickly go to my new custom object, “Advisors”, select my fields, and check the visibility for the field in question. Bam! Done! User satisfied. Next!
But, consider a bigger problem.
“Excuse me Miss, but our party of ten all ordered Lobster Thermidor, and this is clearly an assortment of Mac and Cheese and Fish Sticks.” This gets trickier to fix, in part because of all the questions that follow. I won’t even bother wondering what is going through the poor server’s mind. What if we found ourselves in a situation where multiple profiles suddenly lost access to certain fields, tabs, or objects. It can be as confusing as going from Lobster Thermidor to Fish Sticks. Was it a bad trigger? Malicious intent?
Regardless of how the change occurred, the immediate challenge is to get it resolved. In order to fix it, we must first understand all of the changes that have occurred. Anyone who has spent time on the Profile Setup Page in Salesforce knows how daunting a task this can be, especially when we are not 100% sure of what it is that we are looking to find.
How to Identify Complex Salesforce Profile Changes in Your Metadata
Fortunately, OwnBackup offers a solution to speed this identification process. Since OwnBackup backs up Salesforce Data and Metadata, automatically, every day, it captures these changes to the configuration, and makes them available and easily identifiable in one simple report.
With OwnBackup, you can easily create a Metadata Comparison Report of your Salesforce Environment over any period of time. You can also compare different environments. The report shows removals, changes, or additions that have occurred in metadata between the two backups.
By clicking the links for any of the changed components, you can drill into the differences in the XML code to see exactly what was changed across the entire profile. OwnBackup highlights these changes in red and green so it is easy to see what has been altered or added. The example below, shows that the “Delegated Admin Profile” has lost the “Modify All Records” permission on the Account Object. Access to the “Pricebook” object has also been lost.
With this report, you can breathe a sigh of relief. It is easy to see all of the necessary changes to get these profiles back to where they were before the Gordon Ramsey-esque kitchen nightmare.
The best part is that with OwnBackup, you can push the earlier version of this profile, and all affected profiles, right back into our environment with just a few clicks.