Dynamics 365 Business Central: Development - Check records for uncommitted changes Beta
Data as of 2 hours ago (26 October 2026)
Description
"Use the Record API IsDirty property to determine whether a record instance contains unsaved changes before deciding to validate, save, or otherwise process it. Business value: AL developers can determine whether a record instance has been changed before deciding to save it, validate it, or prompt the user. This can simplify conditional persistence and reduce unnecessary database operations."
Change history
Added to the roadmap 30 September 2026. Tracked here since 1 October 2026. Earliest target we recorded: October 2026 (since tracked — Microsoft may have moved it before we started watching).
Nothing has changed on this item since tracking began on 1 October 2026. Changes appear here as Microsoft updates the feed.