Day: April 7, 2025

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

The 14th of the new functionality in the Development section is use new properties on a report layout.

The new properties added to report layouts significantly enhance the flexibility and functionality of your reporting. The ObsoleteState property allows developers to mark layouts as deprecated, ensuring a smoother transition and better management of future updates. Meanwhile, the ExcelLayoutMultipleDataSheets property enables more complex and customized Excel reports without compromising existing layouts. These enhancements streamline your reporting processes, reduce the risk of errors, and ultimately save time and resources for your business.

Enabled for: Users, automatically
Public Preview: –
General Availability: Apr 2025

Feature Details

The following new properties are available for report layouts:

• ObsoleteState
• ExcelLayoutMultipleDataSheets

With the ObsoleteState property, a developer can signal that a layout is deprecated and will be removed in a later release. The property is shown on the Report Layouts page.

With the ExcelLayoutMultipleDataSheets property, a developer can override the global property defined on the report object to the layout context. For reports where the global property ExcelLayoutMultipleDataSheets wasn’t set (and therefore interpreted as False), a developer can add Excel layouts that use the ExcelLayoutMultipleDataSheets feature without adding the risk of breaking existing Excel layouts that users added.

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

The 13th of the new functionality in the Development section is work with multiline strings in AL.

When developing AL, very long strings are sometimes used. Previously these had to be written in one line, making it hard to easily read content. In this release, Microsoft have added support for writing out strings spanning multiple lines, allowing developers to format the string content in a more human readable form. This especially helps when working with more structured string content, like JSON content.

Enabled for: Users, automatically
Public Preview: Apr 2025
General Availability: Apr 2025

Feature Details

You can now write a string in AL that spans multiple lines by prefixing it with @. This allows you to write the string in a more human readable form—for example, when the content is a structured format like JSON content.

When using this option, remember that any added white space (such as trying to indent lines) will become part of the string, and is therefore not recommended.

Below is an example of using this capability when assigning a JSON template structure to a text variable. Notice the use of @ at the beginning of the string to indicate a multiline string.

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

The 12th of the new functionality in the Development section is validate certificates on external web service endpoints called from AL HttpClient.

This new feature enhances the security of HTTP calls in your AL applications by validating all server certificates used for outgoing web service calls. With certificate validation enabled by default, you can ensure a higher level of trust and security in your communications. If needed, you have the flexibility to selectively disable certificate validation for specific calls, and a new telemetry event helps you debug any failures. By providing robust security measures and debugging tools, this feature adds value by protecting your business from potential security threats and ensuring smooth, secure operations.

Enabled for: Users, automatically
Public Preview: –
General Availability: Apr 2025

Feature Details

To enhance security of HTTP calls from AL, the AL runtime now validates all server certificates used when calling a web service endpoint from the HttpClient datatype. Certificate validation is enabled by default. A server certificate is installed on the endpoint side—it’s not the certificate you attach to a request in AL.

If an app or per-tenant extension needs to selectively disable certificate validation, a new property has been added to the HttpClient datatype that allows the AL code to disable server certificate validation for the outgoing web service call.

If the publisher of an app or per-tenant extension needs to debug failing HTTP calls due to server certificates that fail to be validated, a new telemetry event has been added and will be emitted in case of certificate validation failures.

The ability to disable certificate validation is controlled by a feature management key to allow app and per-tenant extension publishers to modify their code. In version 27, certificate validation will be enabled by default without the ability to switch it off.