Skip to content
BC 2026 release wave 2unofficial launch event map, by waldo

Features › Developer tools

Namespaces in translation IDs

GA · 7 min in 1 video · dev relevance high · documented as Translate objects with the same name in different namespaces high match

Namespaces in translation IDs

XLIFF files can use fully qualified names including the namespace as ids instead of hash keys. This avoids collisions between same-named objects in different namespaces and makes ids readable.

Area: Developer tools. Status: GA. Developer relevance: high. Airtime: 7 min across 1 video, demoed.

Status evidence

  • Nothing said about status; launch event convention: generally available unless stated otherwise.

Where they talk about it

Quotes

  • 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.
  • 13:53 "So we made it possible for you to switch to big integer by changing the type." - States the design decision to allow changing a field to big integer for large customers whose entries run out of numbers.
  • 14:32 "Just changing the type itself does not change all the places where you use this value." - Warns that a big integer change needs follow-up edits in code that uses the field.
  • 15:19 "but it's still allowed and it will still pass through and you can actually do this change without having to copy data" - Shows the type change passes the breaking-change check and needs no data copy or parallel implementation.
  • 17:25 "This will now generate XL files with a fully qualified name as the ids." - Describes the namespace-aware translation ids that avoid collisions between same-named objects.

Caveats mentioned

  • Old hash-key ids could collide when names exist more than once in the global space

Prerequisites mentioned

  • Namespaced objects
  • Translation file setting in app.json for translations with namespaces

Documented features match

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. The wider product documentation on learn.microsoft.com was searched for this feature on the same date; the feature's data lists an article when one was found.

Tags: al, translations, xliff, namespaces, translation, localization

Generated by pipeline step 06. Source: YouTube auto-captions of the launch event videos, see the deep links. Not official.