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/fasttab-field-importance.md
Jeremy Vyska f5156c61de 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>
2026-07-01 11:02:48 +02:00

2.2 KiB
Raw Blame History

bc-version domain keywords technologies countries application-area
all
ui
importance
promoted
additional
fasttab
show-more
summary-line
progressive-disclosure
field-visibility
al
w1
all

Set Field Importance To Drive FastTab Progressive Disclosure

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

Description

A FastTab field's Importance property controls whether the field is visible immediately, hidden behind "Show more", or surfaced on the collapsed FastTab header summary line. The three values are Standard (the default, shown in the expanded FastTab), Promoted (also rendered on the FastTab header when the tab is collapsed), and Additional (hidden until the user clicks "Show more"). Misusing these values either clutters the summary line or buries fields users need on every transaction, so reviewers should treat Importance as a deliberate layout decision rather than an afterthought.

Best Practice

Promote only the two to four identifying fields per FastTab that users must read at a glance without expanding — name, status, key amount — so the collapsed header summary line stays scannable. Leave the everyday working fields at Standard, and push rarely-touched fields (legacy compatibility fields, system timestamps, seldom-changed configuration) to Additional. Note that field-level Importance = Promoted is unrelated to action promotion on the page action bar; it governs FastTab field visibility only. Do not rely on initial expand or collapse state, which you cannot set programmatically and which the platform may personalize per user — design assuming any FastTab may be collapsed.

Anti Pattern

Setting Importance = Promoted on most fields of a FastTab so "everything is important" defeats progressive disclosure: the collapsed summary line overflows and conveys nothing at a glance. The opposite failure is marking frequently edited fields Additional, forcing users to click "Show more" on every record. A detectable signal is a FastTab whose fields are nearly all Promoted, or a FastTab containing only Additional fields, which renders as an empty tab until expanded.