- Feature
- Let agents allocate free AL object IDs
- Availability
- Generally available (October 2026)
- Industry focus
- Industrial equipment and engineer-to-order manufacturing
Industrial equipment manufacturers often have the most heavily customized Business Central systems. Configure-to-order rules, engineering BOM interfaces, service contracts for installed machines and project costing all rely on extensions. Many of these firms now use AI coding agents to speed up development. Business Central 29.0 removes one of the small, irritating reasons that agent-generated code fails.
The industry challenge
Every AL object, such as a table, page, report or codeunit, needs a unique ID within the range assigned to the extension. In a large customization project, those ranges fill up over time. Developers working in parallel can easily pick the same number.
AI coding agents make this harder, not easier. When an agent scaffolds a new page or table, it has to choose an ID. Without a reliable way to check which IDs are free, it may:
- Pick an ID outside the project's range
- Reuse an ID already taken in the project
- Choose one that clashes with an object already installed in the environment
Each mistake means a failed build and a human fixing the agent's output. That erodes the productivity gain that made AI attractive.
What Microsoft delivered in Business Central 29.0
According to Microsoft, coding agents can now find available IDs for AL objects and extension objects within the project's ranges. This cuts manual range checks and collisions with objects already in the project.
Microsoft adds one important limit: only IDs in the connected environment are considered.
The stated business value is that agents can scaffold AL objects without manually reading ID ranges or risking collisions, so generated code is more reliable and needs fewer corrections before it compiles.
Where the value shows up
| Business area | Impact for an equipment manufacturer |
|---|---|
| Development speed | Agents scaffold objects without manual ID checks |
| Build reliability | Fewer failures caused by ID clashes |
| Developer focus | Less time correcting routine agent mistakes |
| Parallel work | Fewer conflicts between developers and agents in the same project |
| Confidence in AI | Agent output that compiles builds trust in the tooling |
The value is cumulative. One ID clash costs only a few minutes. But across a busy development team using agents every day, avoidable failures add up and push people back to doing everything by hand.
A worked scenario
Consider a manufacturer of packaging machinery that builds each line to customer specification (an illustrative example). Its two in-house developers maintain a large extension for product configuration, installed-base tracking and field service contracts.
The team asks an AI coding agent to create a new table and page to track retrofit kits for installed machines. Before 29.0, the agent picked IDs that were already used by objects in the project. The build failed, and a developer spent time finding free numbers and correcting the code.
With Business Central 29.0, the agent asks for free IDs within the extension's range and gets valid numbers. The new table and page compile first time. The developers spend their time reviewing the logic instead of fixing numbering.
Adoption considerations
- Connect to a representative environment. Only IDs in the connected environment are considered, so use one that matches production.
- Keep ranges well defined. Make sure each extension's ID ranges in the manifest are correct and don't overlap with other apps.
- Coordinate parallel work. Branches that haven't been deployed aren't visible to the environment, so merge often and keep communicating.
- Review generated code anyway. Correct IDs don't mean correct logic.
- Combine with other agent tools. Object discovery and clearer compiler diagnostics make agent output more reliable together.
The bottom line
Industrial equipment manufacturers depend on custom Business Central functionality to handle complex products and long equipment lifecycles. Automatic object ID allocation in Business Central 29.0 makes AI-assisted development of that functionality smoother. Fewer failed builds mean more time spent on what matters: logic that reflects how the business actually works.
If your team is starting to use AI coding agents on Business Central, it's worth agreeing standards for ID ranges, environments and code review with an experienced adviser.
Source: Microsoft roadmap 573346