Public package resources
Public package resources
Resource folders can be marked public so other apps can list and read them as JSON or text by provider app ID, without a dependency. Private resources still work with the normal functions without an app ID.
Area: Developer tools. Status: GA. Developer relevance: high. Airtime: 4 min across 1 video, demoed.
Status evidence
- Nothing said about status; launch event convention: generally available unless stated otherwise.
Where they talk about it
- What's new in AL and Tools: 9:47 to 13:40, demo at 11:45
Quotes
- 10:19 "they're actually merged into uh the the base uh table and that means that a key can now span uh both base and extension fields at the same time" - A design change in table extensions that enables keys across base and extension fields.
- 11:34 "The public resources are actually consumable without a dependency." - Consumers of public resources do not need a dependency on the providing app.
- 12:55 "if you try to get a private resource by and providing the app ID, you will get an error." - A limitation: only resources in public folders can be fetched with a provider app ID.
- 13:07 "So be mindful about taking hard dependencies on specific apps on public resources because if they stop shipping it," - Warns that runtime errors occur if a provider app stops shipping a resource.
- 13:40 "that sometimes the ledger entries or some of the other the sequence entries run out of numbers." - Gives the real-world reason for the integer to big integer change.
Caveats mentioned
- Getting a private resource with an app ID gives an error
- Getting a resource that does not exist gives an error
- Be careful with hard dependencies on a specific app's public resources, since they may stop shipping it
Prerequisites mentioned
- Publisher marks the resource folders as public
Documented features match
- No documented item matched. No documented item
- Product documentation: Adding and accessing resources in Business Central extensions, checked 2026-10-02. declare the folder that contains it in the "publicResourceFolders" property of the manifest file (app.json) Note: Section marked 'APPLIES TO: Business Central 2026 release wave 2 and later'. Also covers NavApp.GetResource/ListResources overloads with AppId and the identical not-found error for private resources.
Docs checked on 2026-10-02: the match is against Microsoft's what's new pages for the wave as they were on that date. Microsoft keeps filling the documentation, so "no documented item" can go stale.
Tags: al, resources, packages, extensibility, dependencies
Generated by pipeline step 06. Source: YouTube auto-captions of the launch event videos, see the deep links. Not official.