{"id":9726,"date":"2023-02-28T11:53:35","date_gmt":"2023-02-28T10:53:35","guid":{"rendered":"https:\/\/texei.com\/?p=9726"},"modified":"2024-09-30T11:32:29","modified_gmt":"2024-09-30T09:32:29","slug":"uncovering-salesforce-settings-scratch-org-settings","status":"publish","type":"post","link":"https:\/\/texei.com\/en\/advices\/uncovering-salesforce-settings-scratch-org-settings\/","title":{"rendered":"Uncovering Salesforce Settings: A Step-by-Step Guide for Scratch Orgs"},"content":{"rendered":"

Today, it’s pretty easy to build your Scratch Org definition file<\/a> when you know what Settings<\/a> you want to activate, as they are mapped with the same setting names from the Metadata API<\/a>. But what happens when you want to activate a new setting that has either not yet been documented or that has a weird technical name that you can’t relate to the actual feature ? Let’s have a look on how to find it !<\/p>\n

Give me that setting<\/h2>\n

You may be very excited by new features, be it the new option to let you set Field-Level Security for a field on Permission Sets instead of Profiles during field creation<\/a>, or the powerful new Lightning Web Security<\/a>. But how do you activate them in your Scratch Orgs ? As you can see, the related setting name isn’t always listed in the Release Notes (LWS has been added recently after being asked many time in the Trailblazer Community<\/a>), and finding them in the Metadata API Developer Guide can be tricky. Some settings have cryptic names, whereas some other won’t be documented until the release is out in Production environments or the feature becomes GA.<\/p>\n

What I do is actually pretty simple:<\/p>\n