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 Application features. One of the exciting features is to Find posted and non-posted document lines in search.

With the release of Microsoft Dynamics 365 Business Centra 2022 Wave 2, it is possible to search for posted and non-posted document lines. In the in-product search field, you can search for the following pages, grouped here by document type.

Posted documents:

• Posted Purchase Invoice Lines 
• Posted Purchase Receipt Lines
• Posted Purchase Cr. Memo Lines
• Posted Sales Invoice Lines
• Posted Sales Shipment Lines
• Posted Sales Credit Memo Lines

Open documents:

• Purchase Lines
• Sales Lines
• Prod. Order Comp. Lines

Read more about the feature Find posted and non-posted document lines in search 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 View size of text, code fields in page inspection.

The page inspector is a helpful tool allowing users and developers to see page properties, table fields, and data for the selected page. Before the Microsoft Dynamics 365 Business Central 2022 Wave 2, developers needed to review the table structure to find the length of table fields. With the release of Microsoft Dynamics 365 Business Central Wave 2, users and developers can now see the length of text and code fields in the page inspector. The information is displayed as Text[x] or Code[x], where x is the field’s length.

Read more about the feature View size of text, code fields in page inspection 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 Combine multiple UI actions with a split button.

With the release of Microsoft Dynamics 365 Business Central 2022 Wave 2, there is a new button, or, uh, menu, or, uh, menu button in town – the Split Button. A Split Button is a menu group with a drop-down list for the actions and executes the first action as the button action.

 

As part of the new model for promoting menu actions, the ShowAs property of an action group indicates an action group as a Split Button. The order of the actions is defined in code or as rearranged by extensibility or page design.

 

The following code example of an action group display as a Split Button

Demonstrates how the first action is the Split Button action and can also expand to select the additional actions.

Read more about the feature Combine multiple UI actions with a split button 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 Access database row version from AL code.

Dynamics 365 Business Central 2020 Wave 2 introduced data audit system fields to every table. The audit fields, SystemLastModifiedOn, SystemLastModifiedBy, SystemCreatedBy, and SystemCreatedOn are populated by the platform when a record is created or modified.

With the release of Dynamics 365 Business Central 2022 Wave 2, a global row version number was added to all tables. The platform updates the SystemRowVersion value each time a record is updated. Developers can access this value to query for updated data.

In this example, the SystemRowVersion is displayed on the Customer List Page. When viewing the Customer List Page we can see the values of the audit fields and the version value for the records.

When the Customer is modified, the SystemRowVersion is updated:

Read more about the feature Access database row version from AL code 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 Exclude Try functions when debugging errors.

Before Microsoft Dynamics 365 Business Central 2022 Wave 2, when debugging code, developers could determine if the debugger would break on errors by setting the key, BreakOnError, in the launch.json file value to true or false. When debugging code that uses Try functions, this often leads to many unnecessary breaks because, usually, Try functions are designed to cause errors. With the release of Microsoft Dynamics 365 Business Central, developers have new options for the value of the BreakOnError key.

Then options are:
None (false): do not break on errors
All (true): break on all errors
ExcludeTry: break on all errors if they occur outside of the context of a try function

When debugging the following code with the BreakOnError key value set to All, the debugger will break on the error generated within the Try function. If the BreakOnError key is set to ExcludeTry, the debugger will not break on the error within the Try function.

Note: the true and false options are used for backwards compatibility and may become obsolete in the future. It is recommended to use the All and None option values.

Read more about the feature Exclude Try functions when debugging errors 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.