Translate objects with the same name in different namespaces
Development: Translate objects with the same name in different namespaces. Generally available, GA 2026-10 (Microsoft 365 roadmap). "Generate namespace-aware translation identifiers so identically named AL objects can be translated independently while existing non-namespaced translations remain valid. Business value: Extension developers can translate objects independently when those objects have the same name but belong to different namespaces. This avoids translation identifier collisions and supports broader adoption of namespaces in existing apps."
- 2026-10GA
- 1videos
- 1Learn pages
Microsoft 365 roadmap 573359 · Development · generally available · roadmap status “Launched”, phase General Availability
What Microsoft says
“Generate namespace-aware translation identifiers so identically named AL objects can be translated independently while existing non-namespaced translations remain valid. Business value: Extension developers can translate objects independently when those objects have the same name but belong to different namespaces. This avoids translation identifier collisions and supports broader adoption of namespaces in existing apps.”
Dates
- General availability: October CY2026 (2026 release wave 2)
- Public preview: not given
- On the roadmap since 2026-09-30, last changed 2026-09-30
Covered by
Matched by Haiku among videos and Learn pages in the same galaxy system, checked against the roadmap ids and the evidence text. Every link below was reviewed by Opus.
Videos
- What’s new in AL and Tools (2026 release wave 2): Namespace support in translation IDs at 10:36
Microsoft Learn
Source: Microsoft 365 roadmap. Status words follow the roadmap.