Microsoft/bcquality
1
0
Fork 0
mirror of https://github.com/microsoft/BCQuality.git synced 2026-10-05 06:36:55 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
bcquality/community/knowledge/appsource/place-page-extension-actions-with-addfirst-or-addlast.md
Stefano Demiliani 45ac371e7a
Add AL-focused AppSource validation guidance (#142) 
* knowledge(appsource): add AL validation guidance

* Address Marketplace review feedback

* Address remaining Marketplace review feedback

* Align AppSource review applicability outcome
2026-09-14 12:42:45 +02:00

1.3 KiB
Raw Blame History

bc-version domain keywords technologies countries application-area
all
appsource
pageextension
actions
addfirst
addlast
addbefore
addafter
al
w1
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 a Marketplace extension.

See sample: place-page-extension-actions-with-addfirst-or-addlast.bad.al.