DropDown and Brick fieldgroups must be defined
When a table does not define a DropDown fieldgroup, the platform falls back to the first fields in the table definition. Lookups then show whatever fields happen to come first — often a primary key code on its own, without a description or any other identifying information. The same applies to the Brick fieldgroup: without it, tile views and Teams cards fall back to the DropDown definition, or to the primary key fields if neither fieldgroup exists.
Both fieldgroups should carry the fields that help users spot the right record at a glance — typically a number, a description, and one or two key attributes.
Example
The following table defines no fieldgroups — lookups and tile views fall back to showing whatever fields the platform picks:
table 27 Item // DropDown and Brick fieldgroups must be defined [AC0013]
{
fields
{
field(1; "No."; Code[20]) { }
}
}Define both fieldgroups with the fields that best summarize the record. The DropDown controls which fields appear in lookups; the Brick controls tile views and Teams cards — they typically carry different field sets:
table 27 Item
{
fields
{
field(1; "No."; Code[20]) { }
field(3; Description; Text[100]) { }
field(8; "Base Unit of Measure"; Code[10]) { }
field(18; "Unit Price"; Decimal) { }
field(20; Inventory; Decimal) { }
field(21; "Description 2"; Text[50]) { }
field(93; Picture; MediaSet) { }
}
fieldgroups
{
fieldgroup(DropDown; "No.", Description, "Base Unit of Measure", "Unit Price") { }
fieldgroup(Brick; "No.", Description, Inventory, "Unit Price", "Base Unit of Measure", "Description 2", Picture) { }
}
}When the diagnostic is reported
- Temporary tables are checked only when they are used as the source table of a page.
- Setup tables are excluded — tables whose only primary key field is a
Codefield named “Primary Key”.
See also
- Field groups (DropDown controls) on Microsoft Learn
- Displaying Data as Tiles on Microsoft Learn
- How to Customize Drop-Down List (Field Groups) by Yun Zhu