code change · featureAL Developmentofficial - Microsoftreviewed - checked by Opus

#142 Add AL-focused AppSource validation guidance

Six community AppSource knowledge articles with paired good and bad AL samples now cover profile objects, invariant date literals, page extension action placement, UI calls in web-service paths, UsageCategory on searchable entry points, and time-zone offsets. The AppSource review skill routes AL signals to them.

Pull request · merged into main on 2026-09-14 by demiliani · 19 files (+322 -4), 19 AL · feature · tier official · reviewed (checked by Opus)

What changed

  • Adds six AppSource articles, each with good and bad AL examples
  • Covers profiles as AL objects, invariant date literals, addfirst/addlast action placement, web-service UI calls, UsageCategory, and time-zone offsets
  • Updates the AppSource review skill to point concrete AL signals at the new guidance
  • Avoids duplicating privacy, style, security, and upgrade domain rules

AL objects touched

  • community/knowledge/appsource/define-profiles-as-al-objects.bad.al: added, not in the BC? snapshot yet
  • community/knowledge/appsource/define-profiles-as-al-objects.good.al: added, not in the BC? snapshot yet
  • community/knowledge/appsource/define-profiles-as-al-objects.md: added, not in the BC? snapshot yet
  • community/knowledge/appsource/do-not-hard-code-time-zone-offsets.bad.al: added, not in the BC? snapshot yet
  • community/knowledge/appsource/do-not-hard-code-time-zone-offsets.good.al: added, not in the BC? snapshot yet
  • community/knowledge/appsource/do-not-hard-code-time-zone-offsets.md: added, not in the BC? snapshot yet
  • community/knowledge/appsource/keep-web-service-paths-free-of-ui-calls.bad.al: added, not in the BC? snapshot yet
  • community/knowledge/appsource/keep-web-service-paths-free-of-ui-calls.good.al: added, not in the BC? snapshot yet
  • community/knowledge/appsource/keep-web-service-paths-free-of-ui-calls.md: added, not in the BC? snapshot yet
  • community/knowledge/appsource/place-page-extension-actions-with-addfirst-or-addlast.bad.al: added, not in the BC? snapshot yet
  • community/knowledge/appsource/place-page-extension-actions-with-addfirst-or-addlast.good.al: added, not in the BC? snapshot yet
  • community/knowledge/appsource/place-page-extension-actions-with-addfirst-or-addlast.md: added, not in the BC? snapshot yet
  • community/knowledge/appsource/set-usagecategory-on-searchable-entry-points.bad.al: added, not in the BC? snapshot yet
  • community/knowledge/appsource/set-usagecategory-on-searchable-entry-points.good.al: added, not in the BC? snapshot yet
  • community/knowledge/appsource/set-usagecategory-on-searchable-entry-points.md: added, not in the BC? snapshot yet
  • community/knowledge/appsource/use-invariant-date-literals.bad.al: added, not in the BC? snapshot yet
  • community/knowledge/appsource/use-invariant-date-literals.good.al: added, not in the BC? snapshot yet
  • community/knowledge/appsource/use-invariant-date-literals.md: added, not in the BC? snapshot yet
  • microsoft/skills/review/al-appsource-review.md: modified, not in the BC? snapshot

Context

  • Systems: development
  • From the description: “add seven community AppSource knowledge articles with paired good and bad AL samples”

Source: metadata of a merged pull request in microsoft/BCQuality (bcquality): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).