Resource exposure policies for apps are on by default
This content is archived and is not being updated. For the latest documentation, go to What's new and planned for Dynamics 365 Business Central. For the latest release plans, go to Dynamics 365 and Microsoft Power Platform release plans.
|Enabled for||Public preview||General availability|
|Admins, makers, marketers, or analysts, automatically||Sep 1, 2022||Oct 1, 2022|
With the recent introduction of the resourceExposurePolicy app.json property, the generated setting when using the AL:Go! template was to lock down access to all source.
To ensure that this is a deliberate choice—for example, most per tenant extensions ought to be open for customer source access (unless source is shared elsewhere)—we are reverting to the default used for many years with showMyCode. That is, when using the AL:Go! template, resourceExposurePolicy options will allow access by default. For more about resource exposure policy, see Resource Exposure Policy Setting.
The AL:Go! project template now has allowDebugging, allowDownloadingSource, and includeSourceInSymbolFile switched on by default. This is visible in the app.json file where the project resourceExposurePolicy property is set.
You can always override this for your AppSource or per-tenant extension by changing the setting.
Tell us what you think
Help us improve Dynamics 365 Business Central by discussing ideas, providing suggestions, and giving feedback. Use the forum at https://aka.ms/bcideas.