---
id: feature/573359
type: feature
title: Translate objects with the same name in different namespaces
summary: '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."'
tier: official
language: en
system: development
tags:
  - development
review:
  state: derived
  by: null
  at: null
  flags: []
generated:
  at: "2026-10-07T23:41:05.192Z"
  pipeline: 0.2.0
  prompts: {}
  input_hash: 13d47c993d7d69fd118075f520215d3f834848ac64d2796b9e523db178a5e907
evidence:
  - kind: roadmap
    url: https://www.microsoft.com/microsoft-365/roadmap?id=573359
    title: Microsoft 365 roadmap 573359
    date: "2026-09-30"
    commit: null
    t: null
    quote: null
  - kind: video
    url: https://www.youtube.com/watch?v=D_Lur52IrIg&t=636s
    title: "What's new in AL and Tools (2026 release wave 2): Namespace support in translation IDs"
    date: null
    commit: null
    t: 636
    quote: null
  - kind: learn
    url: https://learn.microsoft.com/dynamics365/business-central/dev-itpro/developer/devenv-work-with-translation-files
    title: Work with XLIFF Translation Files
    date: null
    commit: null
    t: null
    quote: null
links:
  learn:
    - https://learn.microsoft.com/dynamics365/business-central/dev-itpro/developer/devenv-work-with-translation-files
  objects: []
  features: []
  topics: []
  localizations: []
  videos:
    - video/D_Lur52IrIg
  posts: []
  guidelines: []
roadmap_id: "573359"
wave: 2026 release wave 2
status: ga
roadmap_status: Launched
release_phase: General Availability
ga_date: 2026-10
preview_date: null
area: Development
whatsnew_url: null
localizations: []
objects_touched: []
---

# 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."

[Microsoft 365 roadmap 573359](https://www.microsoft.com/microsoft-365/roadmap?id=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)](../videos/D_Lur52IrIg.md): Namespace support in translation IDs at [10:36](https://www.youtube.com/watch?v=D_Lur52IrIg&t=636s)

### Microsoft Learn

- [Work with XLIFF Translation Files](https://learn.microsoft.com/dynamics365/business-central/dev-itpro/developer/devenv-work-with-translation-files)

Source: Microsoft 365 roadmap. Status words follow the roadmap.