Category: Dynamics

This post is part of the In Microsoft Dynamics 365 Business Central (Inventory and Warehouse Management), how do I… series and of the wider In Microsoft Dynamics 365 Business Central, how do I… series which I am posting as I familiarise myself with Microsoft Dynamics 365 Business Central.

With a location enabled for requiring receive, we can now the receipt of goods to the warehouse.

There are two methods for using warehouse receipts:

1. Push, which is where a warehouse receipt is created for a single purchase (or other document bringing stock in, such as a sales return) order from the Create Whse. Receipt action on the Purchase Order card.
2. Pull, which is where a warehouse receipt is created from the Warehouse receipts page. This would typically be used when a shipment from a supplier has come in with goods from multiple orders.

In this post, I will be stepping through the second of the above methods, but you end up in the same window when you use the action mentioned in the first.

To create a warehouse receipt, search for Warehouse Receipts and click the New button.

Tab from the No. field and select the location for which goods are being received. Set the Posting Date and enter the Vendor Posting Number:

Continue reading “In Microsoft Dynamics 365 Business Central (Inventory and Warehouse Management), how do I… Post Receipt From a Warehouse Receipt Document”

This post is part of the New Functionality In Microsoft Dynamics 365 Business Central 2023 Wave 2 series in which I am taking a look at the new functionality introduced in Microsoft Dynamics 365 Business Central 2023 Wave 2.

The eleventh of the new functionality in the Development section is Choose between more sampling intervals for snapshot and in-client profiling.

Some releases ago Microsoft introduced a great new tool to investigate AL performance, namely profiling—either as the AL profiler for developers in a snapshot debug session from within Visual Studio Code, or as part of the in-client performance profiler accessible to customer admins and consultants as well as developers.

In the in-client performance profiler, and optionally in the AL profiler, sampling is used to determine at what intervals the system monitors what is running. At launch Microsoft supported 100ms sampling interval only. Based on feedback Microsoft are now allowing the user to choose between 50, 100 and 150ms. This allows for both finer and coarser granularity of insights, for example, to catch smaller operations and get more accurate durations, or to limit dates being captured and displayed to larger operations only.

Enabled for: Admins, makers, marketers, or analysts, automatically
Public Preview: Aug 2023
General Availability: Oct 2023

Feature Details

With the launch.json snapshot configuration parameter profileSamplingInterval, AL developers can specify the interval at which the sampling will be collected. Current options are {50ms, 100ms, 150ms}. The default value is 100ms.

Continue reading “New Functionality In Microsoft Dynamics 365 Business Central 2023 Wave 2: Choose Between More Sampling Intervals for Snapshot and In-client Profiling”

This post is part of the New Functionality In Microsoft Dynamics 365 Business Central 2023 Wave 2 series in which I am taking a look at the new functionality introduced in Microsoft Dynamics 365 Business Central 2023 Wave 2.

The tenth of the new functionality in the Development section is Set new output folder setting for storing app files at AL project build.

By default, when you build AL projects, the output app file is stored in the project folder. However, if you work on multiple apps that aren’t in the same workspace and depend on each other, outputting to a shared app folder can be a benefit.

Enabled for: Admins, makers, marketers, or analysts, automatically
Public Preview: Aug 2023
General Availability: Oct 2023

Feature Details

In the “al.compilerOptions” settings, you can now use the “outFolder” property to specify which output folder to use when generating an app file as part of building an AL project.

This makes it easier to manage and reuse generated apps in a single location. The AL project in Visual Studio Code will still contain a node for the output file, but the file will then physically be stored outside of the project folder.

Here’s an example of saving built app files in “myappfolder” on the user’s C drive.

This post is part of the New Functionality In Microsoft Dynamics 365 Business Central 2023 Wave 2 series in which I am taking a look at the new functionality introduced in Microsoft Dynamics 365 Business Central 2023 Wave 2.

The ninth of the new functionality in the Development section is Hover over label variable to see text string value.

When label variables are used in AL code, only the label name is shown inline in the source code. To understand what the value of the label is, the developer has had to navigate to the label definition or use Peek Definition. In this release Microsoft add the ability to just hover over the label variable and instantly see the text string value in the tooltip inline, thereby avoiding switching context to see the value.

Enabled for: Admins, makers, marketers, or analysts, automatically
Public Preview: Aug 2023
General Availability: Oct 2023

Feature Details

To easily see the text string value of a label variable, you can now just hover over the variable and the value will be shown in the tooltip. Thus you avoid too much content switching by navigating to the label definition or use Peek Definition (Alt+F12).

Here’s a small example:

This post is part of the New Functionality In Microsoft Dynamics 365 Business Central 2023 Wave 2 series in which I am taking a look at the new functionality introduced in Microsoft Dynamics 365 Business Central 2023 Wave 2.

The eighth of the new functionality in the Development section is Get inlay hints in source editor for AL method parameters and return types.

Visual Studio Code supports an editor concept called inlay hints. These add additional inline information to source code to help you understand what the code does. In this release Microsoft are adding the ability to get inlay hints for AL parameter names and return types.

Enabled for: Admins, makers, marketers, or analysts, automatically
Public Preview: Aug 2023
General Availability: Oct 2023

Feature Details

Visual Studio Code supports inlay hints, which render additional information about the source inline. More information: Inlay Hints

With this release Microsoft are adding inlay hints for AL parameter names and method return types.
Here’s an example of inlay hints enabled for both return type and parameters (these are the grey names):

Continue reading “New Functionality In Microsoft Dynamics 365 Business Central 2023 Wave 2: Get Inlay Hints in Source Editor for AL Method Parameters and Return Types”

This post is part of the New Functionality In Microsoft Dynamics 365 Business Central 2023 Wave 2 series in which I am taking a look at the new functionality introduced in Microsoft Dynamics 365 Business Central 2023 Wave 2.

The seventh of the new functionality in the Development section is Find all references now works on triggers, system methods, and trigger events.

The CodeLens for Where used reference counts and the Find all References tool in Visual Studio Code has not supported triggers, system methods, or trigger events, making it much harder for users to understand and navigate. With Business Central 2023 release wave 2 we are adding support for this, making developers more productive.

Enabled for: Admins, makers, marketers, or analysts, automatically
Public Preview: Aug 2023
General Availability: Oct 2023

Feature Details

We are now finding only relevant references to built-in methods. As an example, Shift+F12 on the Customer.Insert method will now only give you Insert references on the customer record, whereas before you would get any Insert on any record.
We also support finding references to triggers/events/built-in methods that are relevant. For instance, we are finding:

• References to triggers in event subscribers and vice versa (ex: Table.OnInsert <-> OnAfterInsertEvent)
• References to triggers in other triggers and vice versa (ex: Table.OnInsert <-> TableExt.OnBeforeInsert)
• References to triggers in procedures and vice versa (ex: Table.OnInsert <-> Rec.Insert)
• References to procedures or events in event subscribers and vice versa (ex: Table.OnInsert <-> OnAfterInsertEvent)

In this release, the above is enabled on page fields, table fields, page actions, and table methods/triggers/events.
This illustration shows an example of the CodeLens count (the grey "17 references" at the top) and Find all References used on the Customer table trigger OnInsert:

This post is part of the New Functionality In Microsoft Dynamics 365 Business Central 2023 Wave 2 series in which I am taking a look at the new functionality introduced in Microsoft Dynamics 365 Business Central 2023 Wave 2.

The sixth of the new functionality in the Development section is Get the AL Language extension in prerelease versions on Visual Studio Code Marketplace.

Prerelease versions of the AL Language extension for Dynamics 365 Business Central are currently only available as part of Business Central Insider builds. This requires partners to regularly download Insider builds to get the latest prerelease AL Language extension. This situation can cause compatibility issues when Business Central launches a preview close to general release because it’s not clear to partners that they need to download the latest AL Language extension version from the Insider build. However, Visual Studio Code already supports the ability to notify users about and install prerelease versions of extensions. Using this mechanism will make it easier for developers to be aware of and opt in to prerelease AL Language extensions.

Enabled for: Admins, makers, marketers, or analysts, automatically
Public Preview: Jul 2023
General Availability: Oct 2023

Feature Details

The AL Language extension prerelease versions are now available through the existing Visual Studio Code mechanism for getting notified about and installing prerelease versions. To learn more about this mechanism, visit Prerelease Extensions in the Visual Studio Code documentation.

To install the prerelease version, use the drop-down list to select Install Pre-Release Version, or if already installed, use the Switch to Pre-Release Version option in the Visual Studio Code extension management page for the AL Language extension.

When you have switched to the prerelease version, the Visual Studio Code extension management page for the AL Language extension will display that the prerelease is used, and offer the option to switch back to the release version.

This post is part of the In Microsoft Dynamics 365 Business Central (Inventory and Warehouse Management), how do I… series and of the wider In Microsoft Dynamics 365 Business Central, how do I… series which I am posting as I familiarise myself with Microsoft Dynamics 365 Business Central.

In the last article, I covered receiving items on a PO without a specific receipt requirement; this would generally be used by organisations with smaller warehouses or stockrooms and does not need any configuration on a location.

The next level up in the basic warehousing functionality, is to require a warehouse receipt. There is one toggle which needs to be enabled for a location to require warehouse receipts. When you create a location, on the Warehouse fasttab, you need to toggle the Require Receive option to the on position:

Receiving goods in this way, allows you to receive multiple orders at the same time, instead of one-by-one. In the next article of this series, I’ll step through the process of receiving items into the new PURPLE location shown above.

This post is part of the New Functionality In Microsoft Dynamics 365 Business Central 2023 Wave 2 series in which I am taking a look at the new functionality introduced in Microsoft Dynamics 365 Business Central 2023 Wave 2.

The fifth of the new functionality in the Development section is Easier management of System Application permissions.

A streamlined and organized permissions management system can save time and effort for IT administrators. Having fewer permissions that an IT administrator needs to grant to users can improve security, simplify administration, increase productivity, enhance compliance, and lead to cost savings for businesses.

Enabled for: Users, automatically
Public Preview: –
General Availability: Oct 2023

Feature Details

Reducing the number of permissions that you need to control in the System Application makes it easier to manage permissions because you need to consider fewer objects. Managing fewer permissions also reduces the risk of permission errors, such as if you or a partner accidentally leave out certain objects in custom permission sets.

Inherent permissions are applied across System Application modules.

For example, Microsoft have reduced the number of objects that require permissions to be set in System Application – Basic by 60 percent. In the remaining objects, you no longer have to manage some individual permissions. For example, you no longer need to manage Read permission for the Language table because everyone needs access to that table.