mirror of
https://github.com/microsoft/BCQuality.git
synced 2026-10-05 14:46:55 +01:00
2f3e5afac1
Two articles covering retention policies for extension-owned tables, the gap that lets high-volume log tables grow unbounded: - register-owned-log-tables-for-retention-policies: an extension's own log tables must be added to the allowed-tables list from install AND upgrade code, guarded by IsAllowedTable plus an upgrade tag, with a mandatory minimum retention where audit needs one. - ship-a-default-retention-policy-setup: registration only makes a table selectable; nothing is deleted until a Retention Policy Setup record exists, so ship one (disabled by default) as the platform's own Retention Policy Installer does. Each ships good/bad AL samples. Claims verified against the BC admin docs and the Retention Policy module in microsoft/BCApps. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011gvTjm746MtJEVWeRTbG46 |
||
|---|---|---|
| .. | ||
| appsource | ||
| breaking-changes | ||
| data-modeling | ||
| error-handling | ||
| events | ||
| interfaces | ||
| performance | ||
| privacy | ||
| query | ||
| security | ||
| style | ||
| telemetry | ||
| testing | ||
| ui | ||
| upgrade | ||
| web-services | ||
| .gitkeep | ||