Repository navigation
Add BC functional-domain knowledge and a standard application-object reference #35
Description
Context
The README explicitly scopes BC functional domains (Finance, Supply Chain, Manufacturing, Jobs, Warehousing, Service) as in-scope "so agents understand the business context they are working in." None exist today. This is the #1 cause of broken generated extensions.
Why it matters (admission test)
Cheap models hallucinate standard table/field/event names and don't know BC's architectural patterns. Knowing which standard objects to extend (and how) — rather than inventing them — is the difference between a compiling Finance extension and a broken one.
Scope / checklist
Architectural patterns (microsoft/knowledge/<domain>/)
- Posting routines —
Gen. Jnl.-Post Line, Sales/Purchase posting codeunits. - Dimensions & Dimension Set Entries.
- No. Series pattern; setup-singleton tables.
- Document / Document-Line pattern; Ledger Entry pattern; Journal / Registers.
- Currency rounding & precision.
Standard application-object reference (platform method signatures live in #34; this covers application objects/events)
- Curated high-use standard tables (Sales/Purchase Header & Line, Item, Customer, Vendor, G/L Entry, Gen. Journal Line) with key field IDs/names.
- Canonical integration events to subscribe to (e.g.
OnAfterPostSalesDoc, tableOnBeforeInsertEvent) so models extend rather than invent.
Each new knowledge file must pass the README admission test and the CI-validated frontmatter schema.
Activity
JesperSchulz commentedon Jul 1, 2026
Progress update — 2026-07-01
Nothing merged yet, but two open PRs move this:
use-no-series-codeunit-not-noseriesmanagement,master-table-no-from-number-series-in-oninsert,setup-table-is-a-singleton. (Fact check applied: the modern number-series API is codeunit 310"No. Series", not the obsolete-pending 396NoSeriesManagement.)Still open: Dimensions & Dimension Set Entries, the Document / Document-Line + Ledger Entry + Journal / Registers patterns, currency rounding & precision, and the standard application-object reference (high-use standard tables + canonical integration events to subscribe to).