Microsoft/bcquality
1
0
Fork 0
mirror of https://github.com/microsoft/BCQuality.git synced 2026-10-07 15:46:55 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

knowledge(appsource): add AL validation guidance

Browse source
This commit is contained in:
Stefano Demiliani 2026-08-27 17:19:34 +02:00
parent 293f9b13e7
commit e9f870a0f8
22 changed files with 374 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

26
community/knowledge/appsource/place-page-extension-actions-with-addfirst-or-addlast.md Normal file
View file

@ -0,0 +1,26 @@
---
bc-version: [all]
domain: appsource
keywords: [pageextension, actions, addfirst, addlast, addbefore, addafter]
technologies: [al]
countries: [w1]
application-area: [all]
---
# Place page extension actions with addfirst or addlast
## Description
Place new page-extension actions at the beginning or end of an existing action group with `addfirst` or `addlast`. Anchoring a new action relative to a specific base-app action with `addbefore` or `addafter` couples the extension to an implementation detail that can move or disappear between Business Central releases.
## Best Practice
Choose the semantic action area or group and append or prepend the extension's actions. This keeps placement deterministic without depending on the continued existence of one neighboring action.
See sample: `place-page-extension-actions-with-addfirst-or-addlast.good.al`.
## Anti Pattern
Using `addbefore` or `addafter` to place newly added actions next to a specific action from another app. The syntax is valid AL, but the placement anchor is brittle for an AppSource extension.
See sample: `place-page-extension-actions-with-addfirst-or-addlast.bad.al`.