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

Jesper Schulz-Wedde 8f025ac679 Merge current main into development guidance

Reconcile the read-only guidance output with the machine-readable skill index,
adopt linked sample references required by bounded retrieval, and update the
guidance regression fixture for the retrieval helper dependency. Permit only
the known endpoint-DLP metadata stream during read-only evidence capture.

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

2026-09-18 12:04:06 +02:00

1.5 KiB

Raw 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.5 KiB Raw Blame History

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