mirror of https://github.com/microsoft/BCQuality.git synced 2026-10-05 14:46:55 +01:00

Jesper Schulz-Wedde 56b80e6dcf Add knowledge-backed AL development

Add read-only planning and repository-changing development skills so BCQuality
knowledge can guide features, bug fixes, refactors, upgrades, and maintenance
before the existing AL review gate runs. Track Microsoft Learn ingestion and
add development and BCApps-shaped guidance evaluation fixtures.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 638b66d2-9f06-4f60-8781-808709e1485c

2026-09-04 12:53:54 +02:00

1.3 KiB

Raw Permalink Blame History

bc-version

domain

keywords

technologies

countries

application-area

all

fieldgroup

dropdown

addlast

lookup-page

visible

tableextension

pageextension

all

A `DropDown` field remains hidden when its lookup-page control is hidden

Description

A tableextension can append a field to the DropDown field group with addlast, but the client still omits that field when its control on the underlying lookup page has Visible = false. Changing only the table field group therefore compiles while producing no visible UI change. The field-group name is case-sensitive and must be written as DropDown.

Best Practice

When adding a hidden field to a DropDown field group, also extend the page used for the lookup and make that field control visible. Verify the actual lookup page rather than assuming the table definition alone controls the drop-down.

See sample: dropdown-fieldgroup-respects-lookup-page-visibility.good.al.

Anti Pattern

Adding the field with addlast(DropDown; ...) while leaving its lookup-page control hidden, then expecting the field to appear in the drop-down.

See sample: dropdown-fieldgroup-respects-lookup-page-visibility.bad.al.

Reference

Add a new FieldGroup to an existing table

1.3 KiB Raw Permalink Blame History

A DropDown field remains hidden when its lookup-page control is hidden