BC Observatoryunofficial, made by waldo
community postAL Developmentcommunity - not Microsoftreviewed - checked by Opus

Dynamics 365 Business Central on-premises: accessing embedded in-app resources from runtime packages.

From version 25.2 (2024 Wave 2), Business Central extensions can embed resources: you declare them with resourceFolders in app.json and read them with NavApp.GetResource. On-premises runtime packages made with Get-NavAppRuntimePackage could not load embedded resources up to version 26.2, so the full package had to be published. Support arrived in 26.3 (platform 26.0.35604.0).

Open in Claude12422.md

post Stefano Demiliani

Stefano Demiliani · 2025-08-27 · 367 words · about 2 min

"Embedded resources on runtime packages are not supported in Dynamics 365 Business Central with version <= 26.2."
Show the post hereRead on Stefano Demiliani

Key points

  • Extensions can declare resource folders using the resourceFolders property in app.json
  • AL code accesses embedded resources via the NavApp.GetResource method
  • Runtime packages did not support embedded resources until version 26.3 on-premises
  • Partners often use runtime packages to protect intellectual property by excluding AL code
  • Full extension packages were required as a workaround on versions 26.2 and earlier

Quotes

  • “Embedded resources on runtime packages are not supported in Dynamics 365 Business Central with version <= 26.2.” (Clarifies the limitation that existed and caused troubleshooting issues)

AL objects mentioned

As named in the post. A name that matches one object page by exact type and name links to it; the others stay as named.

  • other “NavApp.GetResource”

Context

  • Features: Resource folders in extensions, Embedded resources support, Runtime packages, Resource access from AL code
  • Versions: 2024 Wave 2, 25.2, 26.2, 26.3, 26.0.35604.0

Source: Stefano Demiliani, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.