![salesforce person accounts vs standard accounts salesforce person accounts vs standard accounts](https://venturebeat.com/wp-content/uploads/2019/06/chrome-suspicious-site-reporter-extension.png)
The user must understand at this point that they are indeed carving their decision in stone and there is no going back (at the time of writing of this article). When enabling person accounts, Salesforce shows a warning message indicating that you can not undo the step. And if you don’t have well defined processes and role structures, you’re asking for trouble. Accidentally turning on these features is not very common in Salesforce orgs that have well defined release processes and role structures (but I’ve heard it happen). However, before arriving at that conclusion, do your due diligence in researching the feature capabilities, dependencies, long term implications and test out the solution in sandbox environments following best practices. Some of these features might be a great fit for your solution and that perfect answer to all your business requirements prayers. This post details a list of a few popular “you’re about to set this in stone” features that you need to treat with caution before enabling in your Salesforce org or when considering incorporating into your solution. Thou shalt not alter what is set in Salesforce org’s foundation stone!Ī Salesforce administrator, an Apex developer, a technical architect or an implementation expert – whatever your role is in our Salesforce ecosystem, you’ve come across the phrase “once enabled, this feature can NOT be turned off” in implementation guides and release notes.