Microsoft/bcquality
1
0
Fork 0
mirror of https://github.com/microsoft/BCQuality.git synced 2026-10-05 14:46:55 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions 4
bcquality/microsoft/knowledge/performance/guiallowed-guard-on-pages-used-as-odata.md
Jesper Schulz-Wedde 42ff075793 Promote knowledge for Microsoft review skills 
Move canonical knowledge for Microsoft-owned review domains into the Microsoft layer and document the skill/knowledge co-location policy.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 2a6ea875-d38e-4f30-aadb-0d606f9be231
2026-09-03 14:59:44 +02:00

1.3 KiB
Raw Blame History

bc-version domain keywords technologies countries application-area
all
performance
guiallowed
clienttype
odata
edit-in-excel
page-trigger
factbox
al
w1
all

Guard page trigger work with GuiAllowed for OData and Excel

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

Description

Pages exposed as OData, including Edit in Excel, still run AL page triggers for every row returned. FactBox updates, defaulting, and extra CalcFields in OnAfterGetRecord therefore run on the web-service path where no UI exists. GuiAllowed is false for those sessions. Agents add page logic as if only the browser client will execute it.

Best Practice

Wrap UI-only work — FactBox refresh, notifications, defaulting that is not part of the web-service contract — in if GuiAllowed then. Keep the OData path to field values the API actually returns.

See sample: guiallowed-guard-on-pages-used-as-odata.good.al.

Anti Pattern

Unconditional FactBox or calculation logic in OnAfterGetRecord / OnAfterGetCurrRecord on a page that is published as a web service or used with Edit in Excel. The signal is trigger work that calls CurrPage parts or extra queries without a GuiAllowed guard.

See sample: guiallowed-guard-on-pages-used-as-odata.bad.al.