
Announcements
In Business Central AL development, object IDs are required for all object types such as tables, pages, codeunits, reports, page extensions, table extensions, interfaces, enums, and so on.
Currently, object IDs must be manually assigned at design time, typically within a predefined idRanges block in app.json. While this works, managing IDs becomes challenging in larger projects or team-based development, especially when working across multiple object types.
My questions are:
Is there any built-in or recommended way in Business Central / AL to automatically generate or assign object IDs for new objects?
Are there best practices or tooling approaches (VS Code extensions, workflows, conventions) that teams commonly use to avoid ID conflicts and manual tracking?
How do teams usually handle this across multiple object types, not just tables?
I understand that runtime generation is not possible, but I’m looking for practical, near-automatic approaches that are commonly adopted in real-world AL development.
Any guidance or shared experiences would be appreciated.