Add data-modeling and appsource knowledge articles (MICROSOFT layer)

Author 7 remedial BCQuality knowledge articles plus good/bad AL samples
(21 files) covering AL master-table and data-model design:

- data-modeling: master No. from number series in OnInsert; use codeunit
  "No. Series" not obsolete NoSeriesManagement; setup table is a singleton;
  set Last Date Modified in OnModify and OnRename; enforce Blocked in
  referencing code not in the master.
- style: ApplicationArea required on page controls (AS0062).
- appsource: object affixes prevent collisions (AS0011).

Clean-room authored from own BC knowledge; specifics verified against public
sources only (learn.microsoft.com, microsoft/BCApps). Introduces two new
domains (data-modeling, appsource).

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

microsoft/knowledge/appsource/object-affixes-prevent-collisions.bad.al

@@ -0,0 +1,43 @@
+// Anti-pattern: an own object with no affix. Another app that also defines a
+// "Loyalty Tier" table cannot be installed alongside this one.
+table 50379 "Loyalty Tier"
+{
+    Caption = 'Loyalty Tier';
+    DataClassification = CustomerContent;
+
+    fields
+    {
+        field(1; "Code"; Code[20])
+        {
+            Caption = 'Code';
+        }
+        field(10; Description; Text[100])
+        {
+            Caption = 'Description';
+        }
+    }
+
+    keys
+    {
+        key(PK; "Code")
+        {
+            Clustered = true;
+        }
+    }
+}
+
+// Anti-pattern (the common half-measure): the extension object carries the
+// affix, but the field it adds to the standard Customer table does not. That
+// unaffixed field still collides with any other app that adds "Loyalty Points"
+// to Customer, and AS0011 flags it.
+tableextension 50378 "ABC Customer Ext" extends Customer
+{
+    fields
+    {
+        field(50378; "Loyalty Points"; Integer)
+        {
+            Caption = 'Loyalty Points';
+            DataClassification = CustomerContent;
+        }
+    }
+}

microsoft/knowledge/appsource/object-affixes-prevent-collisions.good.al

@@ -0,0 +1,40 @@
+// Own object: the affix "ABC" is carried at object-name level.
+table 50377 "ABC Loyalty Tier"
+{
+    Caption = 'Loyalty Tier';
+    DataClassification = CustomerContent;
+
+    fields
+    {
+        field(1; "Code"; Code[20])
+        {
+            Caption = 'Code';
+        }
+        field(10; Description; Text[100])
+        {
+            Caption = 'Description';
+        }
+    }
+
+    keys
+    {
+        key(PK; "Code")
+        {
+            Clustered = true;
+        }
+    }
+}
+
+// Extension of a standard object: the added field is individually affixed,
+// because the object name (Customer) belongs to the base application.
+tableextension 50376 "ABC Customer Ext" extends Customer
+{
+    fields
+    {
+        field(50376; "Loyalty Points ABC"; Integer)
+        {
+            Caption = 'Loyalty Points';
+            DataClassification = CustomerContent;
+        }
+    }
+}

microsoft/knowledge/appsource/object-affixes-prevent-collisions.md

@@ -0,0 +1,28 @@
+---
+bc-version: [all]
+domain: appsource
+keywords: [object-affix, prefix, suffix, as0011, appsourcecop, collision, tableextension]
+technologies: [al]
+countries: [w1]
+application-area: [all]
+---
+
+# Apply a reserved affix to objects and to members added to base objects
+
+## Description
+
+An AppSource extension must carry a reserved affix — a prefix or a suffix of at least three characters — on the names of the objects it owns **and** on any field, key, control, or action it adds to a base-application object. The affix is registered with Microsoft; when two coexisting extensions would otherwise collide, the registrant of the affix wins. Without it, two apps that both add a `Loyalty Points` field to `Customer`, or both define a `Loyalty Tier` table, cannot be installed side by side.
+
+AppSourceCop enforces this. The primary rule is AS0011 ("An affix is required"); the affixes are configured through `mandatoryAffixes` (and `mandatoryPrefix`) in `AppSourceCop.json`. Two placements matter and are easy to get half-right: an object you define carries the affix at **object-name** level, while a member you add to a **standard** object carries the affix on that **member's** name. Adding an affixed object is not enough — an unaffixed field bolted onto `Customer` still collides and still fails validation.
+
+## Best Practice
+
+Own objects are named with the affix (e.g. a table `ABC Loyalty Tier`), and every field or action added to a standard object is individually affixed (e.g. `Loyalty Points ABC` on a `Customer` tableextension).
+
+See sample: `object-affixes-prevent-collisions.good.al`.
+
+## Anti Pattern
+
+Unaffixed object or member names, or the common half-measure: the extension object carries the affix but a field it adds to a standard table does not. AS0011 flags the missing affix and the field can still collide with another app.
+
+See sample: `object-affixes-prevent-collisions.bad.al`.