Exclude temporary records when debugging record writes

  • Article

Important

This content is archived and is not being updated. For the latest documentation, go to What's new and planned for Dynamics 365 Business Central. For the latest release plans, go to Dynamics 365 and Microsoft Power Platform release plans.

Enabled for Public preview General availability
Admins, makers, marketers, or analysts, automatically Sep 1, 2022 Oct 1, 2022

Business value

When debugging, it has been possible to control whether to break on record writes. However, until now, any writes to temporary records have also triggered a break. To allow ignoring these for a more efficient debugging of database writes, a new option has been added to omit any writes to temporary records.

Feature details

We have added new options to control when the debugger should break on record writes. Instead of the old Boolean BreakOnRecordWrite setting in a launch.json file connection setup, this now takes one of the following values: true, false, None, All, ExcludeTemporary.

The behavior for each option is:

  • false/None: Does not break on any record writes.
  • true/All: Breaks on all record writes.
  • ExcludeTemporary: Breaks on record writes only if they are not on a temporary table.

True and false are retained for now for backward compatibility. They map to All and None. We recommend using the latter going forward. True and false might become obsolete in a future version.

Tell us what you think

Help us improve Dynamics 365 Business Central by discussing ideas, providing suggestions, and giving feedback. Use the forum at https://aka.ms/bcideas.

Thank you for your idea

Thank you for submitting this idea. We listened to your idea, along with comments and votes, to help us decide what to add to our product roadmap.

See also

JSON Files (docs)