Add a new FieldGroup to an existing table
Important
This content is archived and is not being updated. For the latest documentation, go to What's new or changed in Business Central. For the latest release plans, go to Dynamics 365, Power Platform, and Cloud for Industry release plans.
| Enabled for | Public preview | General availability |
|---|---|---|
| Admins, makers, marketers, or analysts, automatically | 
Sep 12, 2023 |
Oct 2, 2023 |
Business value
One of the highest-voted extensibility gaps in AL is the ability to add field groups to tables through table extensions, when the table doesn't have one. Apart from a functional gap, this also impacts moving existing on-premise customizations to extensions, be it on-premises still or to cloud.
Feature details
While it's currently possible to add a FieldGroup (a dropdown list, for example) in an extension in a new table or to add fields to an existing FieldGroup for a core table, it isn't possible to add a FieldGroup to a core table that doesn't have one already defined. With this new feature, table extensions will be able to add a FieldGroup to existing tables.
The way this works is that a table extension can add fields by using the "addlast" keyword in the Dropdown or Brick field groups, just as today. However, if the field group doesn't exist on the table, which is being extended, it will be created. If multiple table extensions each add fields, the field group will contain the merged result, in the order that the extensions are loaded (first AppSource apps, then PTEs).
Tell us what you think
Help us improve Dynamics 365 Business Central by discussing ideas, providing suggestions, and giving feedback. Use the forum at https://aka.ms/bcideas.
Thank you for your idea
Thank you for submitting this idea:
We listened to your idea, along with comments and votes, to help us decide what to add to our product roadmap.
See also
Adding new field groups (docs)