With each update of Dynamics 365 Business Central, Microsoft enhances what is often referred to as the base application and enhances the development environment. Dynamics 365 Business Central 2022 Wave 2 has several exciting Development features for runtime 10.0. One of the exciting features is to Dynamics 365 Business Central 2022 Wave 2 – Enable NoImplicitWith feature by default.

Microsoft Dynamics 365 Business Central 2020 Wave 2 added the Obsolete implicit and explicit use of ‘with’ development feature. The implicit or explicit ‘with’ use introduces possible collisions when referencing only member names instead of the fully qualified name.

From Business Central 2020 Wave 2 forward, the use of implicit and explicit ‘with’ was managed by Compiler Warning AL0606 and AL0604.

Developers could suppress the warning by using the suppressWarnings property in the app.json file, the pragma compiler directive, or a Ruleset rule. The implicit and explicit use of ‘with’ can be switched on or off with the NoImplicitWith option in the features property in the app.json file. Beginning with Business Central 2022 Wave 2, the NoImplicitWith option is enabled by default with the AL:Go! template.

Read more about the feature Enable NoImplicitWith feature by default here.

Note: The code and information discussed in this article is for informational and demonstration purposes only. This content was created referencing Microsoft Dynamics 365 Business Central 2022 Wave 2 online.

With each update of Dynamics 365 Business Central, Microsoft enhances what is often referred to as the base application and enhances the development environment. Dynamics 365 Business Central 2022 Wave 2 has several exciting Development features for runtime 10.0. One of the exciting features is to See the primary key for table fields in IntelliSense.

When developing AL Extensions within VS Code, it is often necessary to work with table fields. In many cases, such as record navigation or creation, knowing the primary keys for a table is important. Before the Microsoft Dynamics 365 Business Central 2022 Wave 2, developers navigated back to the source table to see the primary fields and their sequence. With the release of Microsoft Dynamics 365 Business Central 2022 Wave 2, a table’s primary key fields are identifiable along with their sequence.

Read more about the feature See the primary key for table fields in IntelliSense here.

Note: The code and information discussed in this article is for informational and demonstration purposes only. This content was created referencing Microsoft Dynamics 365 Business Central Public Preview 2022 Wave 2 online.

With each update of Dynamics 365 Business Central, Microsoft enhances what is often referred to as the base application and enhances the development environment. Dynamics 365 Business Central 2022 Wave 2 has several exciting Development features for runtime 10.0. One of the exciting features is to Use option access syntax in formulas.

[EventSubscriber(ObjectType: ObjectType, ObjectId: Integer, EventName: Text, ElementName: Text, SkipOnMissingLicense: Boolean, SkipOnMissingPermission: Boolean)]

[EventSubscriber(ObjectType::Codeunit, 12, 'OnAfterInitVendLedgEntry', '', true, true)]

[EventSubscriber(ObjectType::Codeunit, Codeunit::"Gen. Jnl.-Post Line", 'OnAfterInitVendLedgEntry', '', true, true)]

It is much easier on the eyes.

Read more about the feature Use option access syntax in formulas here.

Note: The code and information discussed in this article is for informational and demonstration purposes only. This content was created referencing Microsoft Dynamics 365 Business Central Public Preview 2022 Wave 2 online.

With each update of Dynamics 365 Business Central, Microsoft enhances what is often referred to as the base application and enhances the development environment. Dynamics 365 Business Central 2022 Wave 2 has several exciting Development features. One of the exciting features is to Exclude temporary records when debugging record writes.

While debugging in Microsoft Dynamics 365 Business Central, it is often desirable to break on record writes. The BreakOnRecordWrite setting in the Launch configuration determines if the debugger will break on record writes. Setting the BreakOnRecordWrite to true would trigger a break on record writes while debugging.

With the release of Dynamics 365 Business Central Wave 2, a new option – ExcludeTemporary, was added to the BreakOnRecordWrite setting. The BreakOnRecordWrite setting options are:

None (false): Do not break on any record writes.
All (true): Break on all record writes.
ExcludeTemporary: Breaks on record writes for non-temporary tables

Note: the true and false options are available for backward compatibility and may become obsolete. True/False values should be changed to the appropriate new option value.

Read more about the feature Exclude temporary records when debugging record writes here.

Note: The code and information discussed in this article is for informational and demonstration purposes only. This content was created referencing Microsoft Dynamics 365 Business Central Public Preview 2022 Wave 2 online.