e570d6113f
Adds 55 articles (plus 76 code samples) spanning four new domains and two existing domains, extracted from the internal Business Central review-agent prompt. Content was filtered against BCQuality's remedial-knowledge premise: each article encodes BC-specific behaviour, a CodeCop rule, a platform API semantic, or an anti-false-positive guideline that a capable LLM would otherwise get wrong. New domains: - privacy (11 articles): DataClassification inheritance semantics, the StrSubstNo-defeats-Error-telemetry-classification pitfall, Privacy Notice consent for outgoing requests, anti-false-positives for pages and in-memory data. - upgrade (11 articles): upgrade-codeunit structure, upgrade-tag lifecycle and registration, protected DB reads, DataTransfer for large datasets, InitValue semantics, enum-ordinal preservation, obsolete-workflow, first-install detection. - ui (9 articles): caption capitalization by phrase type, tooltip voice, teaching-tip vs tooltip, tour-tip conventions, character limits, banned terms, ampersand handling, title punctuation. - style (11 articles): label-suffix convention, API page naming, temporary-variable prefix, label properties (Comment/Locked), named invocations, FieldCaption in user messages, OptionCaption pairing, Error-parameter passing, `this` keyword, required parentheses, file naming. Gaps in existing domains: - performance (11 articles): production-scale table catalog (no row counts, per internal-data concern), anti-false-positive for bounded tables, guard-before-Get ordering, redundant-Get-in-OnAfterGetRecord, LockTable in read-only helpers, combined ModifyAll passes, writes in OnAfterGetRecord, SetLoadFields heuristics, temporary-table regressions, FlowField source-table widening, MaintainSQLIndex disabling SIFT. - security (2 articles): environment-specific hardcoded GUIDs, ValidateTableRelation=false on user input. Intentionally excluded: specific production P95 row-count numbers (aggregated internal telemetry); rewritten as categorical guidance on which tables to treat as production-scale without publishing sizes. All articles use `bc-version: [all]` (applies to every BC version, per the new schema sentinel). Validator passes with 0 errors / 0 warnings.
1.7 KiB
| bc-version | domain | keywords | technologies | countries | application-area | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
style |
|
|
|
|
API pages follow strict naming and property rules that differ from regular pages
Description
Pages declared PageType = API are exposed through the OData API surface. The platform enforces a set of conventions that regular pages do not share: APIPublisher, APIGroup, EntityName, and EntitySetName must be camelCase alphanumeric only — no spaces, hyphens, or underscores. APIVersion must match the pattern vX.Y (for example v2.0) or the literal beta. EntityName is the singular form (customer); EntitySetName is the plural (customers). DelayedInsert = true is effectively required for the OData insert workflow to behave correctly on composite keys. These rules are platform-enforced and tooling-enforced; violations produce runtime errors or consumer-visible inconsistencies rather than soft warnings.
Best Practice
For every API page: camelCase alphanumeric API properties; APIVersion as vX.Y or beta; singular EntityName and plural EntitySetName; DelayedInsert = true. Keep these properties together near the top of the page definition so reviewers can check the set at a glance.
See sample: follow-api-page-naming-rules.good.al.
Anti Pattern
APIPublisher = 'Contoso-App' (hyphen rejected), EntityName = 'customers' and EntitySetName = 'customer' (swapped), APIVersion = 'v2' (missing minor version), DelayedInsert omitted. Each violation surfaces only when a consumer exercises the endpoint.
See sample: follow-api-page-naming-rules.bad.al.