Microsoft/bcquality
1
0
Fork 0
mirror of https://github.com/microsoft/BCQuality.git synced 2026-08-06 17:36:53 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
bcquality/community/knowledge/ui/prefer-actionref-syntax-for-promoted-actions.md
Jeremy Vyska 4119417ce4
Some checks failed
Validate knowledge index / validate-index (push) Has been cancelled
Details
Validate frontmatter and structure / validate (push) Has been cancelled
Details
Add 15 community knowledge articles from BC Code Intel ingest (#66) 
* Add 15 community knowledge articles from BC Code Intel ingest

Ingests net-new /community knowledge from BC Code Intelligence, surviving
the admission test, gray-zone salvage, and dedup against the full corpus.

Domains: ui (6), error-handling (3), performance (2), upgrade (1),
appsource (1), security (1), telemetry (1). The two BC24 No. Series
migration drafts are merged into one article.

Adds good/bad AL samples for the clean-fit articles (error-handling,
performance, security, telemetry). UI and appsource remain knowledge-only.

Validator and knowledge-index checks pass (207 articles).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* Correct SetLoadFields JIT-load article to match MS docs

The draft claimed accessing an unlisted field "reloads the entire row"
per record. Microsoft's partial-records docs say otherwise: the platform
does an implicit Get that loads the missing field(s), and in a direct var
loop the first JIT updates the enumerator so later iterations do not
re-load. The genuine per-row penalty is the pass-by-value case, where the
copy's enumerator is not updated.

Rewrite the article around JIT loading and the by-value footgun, rename
the slug from ...full-reload to ...jit-load, and fix the good/bad samples
to demonstrate the by-value repetition accurately.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Jeremy Vyska <jeremy@sparebrained.com>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-01 14:31:50 +02:00

2.1 KiB
Raw Blame History

bc-version domain keywords technologies countries application-area
21..
ui
actionref
promoted-actions
area-promoted
promotedcategory
promotedonly
action-bar
legacy-syntax
al
w1
all

Promote Actions With The Modern actionref Syntax, Never The Legacy Promoted Properties

Contributions welcome — open a PR to refine or extend this article.

Description

Business Central 2022 release wave 2 (v21) introduced the area(Promoted) block with actionref as the way to promote page actions, separating an action's definition from its promotion. The older approach set Promoted, PromotedCategory, PromotedOnly, and PromotedIsBig directly on each action. The two syntaxes cannot be mixed within a single page or page extension, and choosing the legacy one entangles definition with presentation, making the action bar harder to maintain and to extend.

Best Practice

For new pages and page extensions, define actions in their normal area, then promote selected ones with actionref inside area(Promoted), grouping them under explicit categories such as Category_Process and entity-named groups. This keeps each action defined once and referenced where it should appear, supports split buttons via ShowAs, and lets an extension promote a base action without redefining it. When extending a page, you may use modern syntax even if the base page used legacy properties (and vice versa) — the no-mixing rule is per-object, not per-dependency-tree.

Anti Pattern

Setting Promoted = true (with PromotedCategory, PromotedOnly, or PromotedIsBig) on actions in new code, or attempting to combine those properties with an area(Promoted) block in the same object — the latter fails to compile. The reviewer signal is any Promoted-prefixed property on an action in a newly authored page or page extension; flag it and convert to actionref (VS Code offers an automated conversion). Note separately that once an action is promoted in a published app, removing the promotion is a breaking change (AS0031/AW0013), so promote conservatively rather than walking it back later.