Day: February 23, 2024

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

The 1st of the new functionality in the Development section is handle multiple file uploads and file drop zones.

The ability for AL developers to handle multiple file uploads and designate different page parts as file drop zones in Business Central provides greater flexibility and usability. This enhancement benefits developers working on applications or customizations that require multifile upload functionality and adds value to organizations by improving productivity and the user experience.

Enabled for: Users, automatically
Public Preview: Mar 2024
General Availability: Apr 2024

Feature Details

Developers can handle multiple file uploads and designate different page parts as file drop zones.

This improvement empowers AL developers to create more flexible and user-friendly interfaces within Business Central. Designating specific page parts as file drop zones lets people upload multiple files at the same time, which improves efficiency.

This feature is particularly valuable for developers working on applications or customizations that require users to upload multiple files simultaneously. By allowing users to drag and drop files onto designated page parts, developers can streamline the file upload process and simplify data entry.

Continue reading “New Functionality In Microsoft Dynamics 365 Business Central 2024 Wave 1: Handle Multiple File Uploads and File Drop Zones”

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

The 3rd of the new functionality in the Country and regional section is install UK localization as an app.

The new and upgraded localized version for the United Kingdom is delivered as an extension.

By removing country-based customizations in the base app, delocalization can help organizations save time and money during implementation. This can be especially beneficial for organizations that operate in multiple countries or regions with different regulatory requirements because they can easily build PTEs and connect those environments. Delocalization can also help organizations get ISV solutions without limitations.

Enabled for: Users, automatically
Public Preview: –
General Availability: Aug 2024

Feature Details

The localized version for the UK is now delivered as a set of extensions on top of the W1 base app. The solution offers a data upgrade, making it easy to move from the previous localization to the new extension. This release is a step toward full delocalization so that ISVs can release their apps to a broader market.

My Opinion

This sounds, on the surface, like it might be a positive, but also that there could be a lot of extra overhead and complexity. I worry about the phrase “set of extensions”.

I had a moment during a client training session recently where I was showing them through the payment journal for doing a purchase ledger payment run and ran into a problem with the process whereby all of the lines were getting the same document number assigned. Obviously this is bad, as each vendor payment requires a unique document number.

It took me a couple of minutes to realise that when I’d talked them through the Suggest Vendor Payments function, I had missed the last field. This field is New Doc. No.per Line and needs to be toggled on for each payment line to receive a unique document number:

I don’t know why this is an option is off by default on a new system, as you will always want every line to have a unique number, but at least it will be remembered for future payments runs which are processed. Once the option was toggled on and the suggest function complete, all of the payment lines had a unique number and the payment run could be completed.