5
There is an option for the debugger, breakOnRecordWrite, that will break on any record write - database or temporary.
When trying to pinpoint a problem related to a database write, breaking on all writes to temporary tables clouds the picture.

Suggestion: add an option breakOnDatabaseRecordWrite. This should break only on records that are database backed, i.e. not temporary.
Category: Development
STATUS DETAILS
Planned
2022 Release Wave 2
Ideas Administrator

Thank you for this suggestion! This has been added to 2022 release wave 2 and can already now be tested with the insider VSIX builds.

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 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.

As can be seen, "true" and "false" are retained for now for backwards compatibility. They map to "All" and "None", we recommend using latter going forward, and might obsolete true and false in a future version.

Best regards,
Business Central Team