- Feature
- Translate objects with same name in different namespaces
- Availability
- Generally available (October 2026)
- Industry focus
- Multinational manufacturing groups
Manufacturing groups with plants in several countries need their Business Central extensions to speak several languages. A plant manager in Poland, a planner in Germany and a controller in the UK should each see captions and messages in their own language. Business Central 29.0 fixes a problem that has made this harder as extensions grow.
The industry challenge
As group extensions get bigger, developers increasingly use AL namespaces to organize code. Namespaces let different parts of an app, or different apps, use the same object name without clashing. For example, a group might have:
- A "Quality Setup" page in its plant quality module
- A "Quality Setup" page in its supplier quality module
Namespaces make this possible in code. But translations have lagged behind. Translation identifiers were not namespace-aware, so two objects with the same name could collide. Developers either avoided namespaces, used awkward unique names, or accepted wrong translations in some places.
For a multinational group, that means either a less maintainable codebase or users seeing captions that don't match their screen.
What Microsoft delivered in Business Central 29.0
According to Microsoft, Business Central 29.0 generates namespace-aware translation identifiers. Objects with identical names can be translated independently, and existing translations for objects without namespaces stay valid.
Microsoft says this avoids translation identifier collisions and supports wider use of namespaces in existing apps.
Where the value shows up
| Business area | Impact for a multinational manufacturer |
|---|---|
| User experience | Plant staff see correct captions in their own language |
| Code organization | Developers can use namespaces freely in group extensions |
| Maintenance | No need for artificial unique names to avoid translation clashes |
| Rollouts | New countries can be added with translation files, not code changes |
| Backward compatibility | Existing translations keep working |
The benefit is twofold. Users get accurate language support, and developers get to organize large codebases properly. In a group that keeps adding plants and acquisitions, both matter.
A worked scenario
Consider a manufacturer of industrial pumps with plants in the UK, Germany and Poland (an illustrative example). Its group extension has two modules, plant quality and supplier quality, each with a page called "Quality Setup."
Before 29.0, the developers had to rename one page to avoid a translation clash, which confused users who knew both screens by the same name. In one release, the German translation of one page appeared on the other.
With Business Central 29.0, the developers place each module in its own namespace and keep the natural names. Translations are generated separately for each namespace. German and Polish users see the right captions on both pages, and the next acquisition in Czechia only needs a new translation file.
Adoption considerations
- Plan your namespace structure. Decide how modules and apps are organized before refactoring.
- Check existing translations. Non-namespaced translations remain valid, but review them when you introduce namespaces.
- Use your translation workflow. Make sure your tools and translators handle the new identifiers.
- Test with real users. Ask plant staff in each country to check key screens after the change.
- Coordinate with ISVs. If you rely on vertical apps, ask how they're adopting namespaces.
The bottom line
Multinational manufacturing groups need systems that work in every language their people use, and codebases that can grow without becoming tangled. Namespace-aware translations in Business Central 29.0 remove a technical blocker to both. It's a small change that supports better software and better user experience across borders.
If your group is extending Business Central across countries, it's worth reviewing your extension structure and translation approach with an experienced adviser.
Source: Microsoft roadmap 573359