Overview
This update replaces previously released updates. You should always install the latest update.
After you install this hotfix, you might have to update your license to gain access to new objects that are included in this or a previous update. (This applies only to customer licenses.)
For a list of updates that were released for Microsoft Dynamics 365 Business Central 2025 Release Wave 1, see released updates for Microsoft Dynamics 365 Business Central 2025 Release Wave 1. Updates are intended for new and existing customers who are running Microsoft Dynamics Released Updates for Microsoft Dynamics 365 Business Central 2025 Release Wave 1.
Important
We recommend that you contact your Microsoft Dynamics Partner before you install hotfixes or updates. It is important to verify that your environment is compatible with the hotfixes or updates that will be installed. A hotfix or update may cause interoperability issues with customizations and third-party products that work together with your Microsoft Dynamics 365 Business Central solution.
Problems that are resolved in this update
The following problems are resolved in this update.
Platform hotfixes
| ID | Title |
|---|---|
| 573394 | The PDF files that are printed from Business Central miss accessibility properties. |
| 579644 | Fix an issue where retrieving PTE fails during the upgrade. |
| 579849 | The OnPreRendering trigger isn't triggered in print or preview when using RDLC report layouts. |
| 580061 | The web client stops responding when adding values in a dropdown list that's dynamically set to visible. |
| 580154 | SQL Server indexes added directly in SQL Server might block schema synchronization when shortening a column length. |
| 581183 | Increase the timeout for the upgrade step that repairs system ID and key names. |
| 581312 | Provide better error messages for timeouts. |
| 581332 | Publishing extensions occasionally fails. |
| 582049 | Ensure all tables are created with the dbo schema. |
| 582115 | Support PDF/UA for PDF files generated from Word layouts using bulk rendering of multiple documents. |
Application hotfixes
| ID | Title | Functional Area |
|---|---|---|
| 578186 | The ledger entries with the Usage, Purchase, and Sale Entry Types can be posted for a resource without specifying a document number in the Resource Journal. | Administration |
| 571561 | Issue with non-deductible VAT rounding when using reverse charge VAT. | Finance |
| 572705 | Error occurs when creating a purchase order on the project planning lines. | Finance |
| 574067 | "The length of the string is XXXX, but it must be less than or equal to 1024 characters" error occurs when importing a CSV file through the bank reconciliation journal. | Finance |
| 574648 | Fix an issue where the Sales Order Amount and Sales Invoice Amount are tripled in Customer Card Statistics. | Finance |
| 576217 | The Payment Discount Tolerance Warning occurs when it shouldn't. | Finance |
| 579311 | Fix the Allocation Account rounding issue. | Finance |
| 579394 | The Sales This Month activity on the Business Manager role isn't refreshed as expected. | Finance |
| 579735 | Incorrect cost is posted in Value Entries of the item charge when using non-deductible VAT with the Prices Including VAT field. | Finance |
| 579826 | The dimensions aren't considered when adjusting G/L accounts for Add.-Reporting Currency with the Dimension Posting option set to Source Entry Dimension. | Finance |
| 579918 | The price isn't updated correctly based on Price Lists in Service Objects when the Quantity field is changed. | Finance |
| 581111 | When updating the Item, Resource, or G/L Account codes, it is not correctly reflected in the Project Planning Lines. | Finance |
| 581458 | Fix the incorrect behavior of the Apply to Oldest method in Customer Card Setup. | Finance |
| 581483 | The Statistical Account Balance generates a filter error when you choose to exclude closing entries and view the page as Balance at Date. | Finance |
| 574390 | The Name field is blank in the Vendor - Top List Excel (Report ID: 4404) report when Vendor No. contains an ampersand (&) character. | Integration |
| 578450 | The invoice discount can be modified without restrictions after sending the approval request and the status is Pending Approval in the document. | Integration |
| 574240 | Fix the issue with the Item Availability by BOM Level page in Released Production Orders, where selecting Item Components only closes the page instead of presenting the Item to be selected for further review. | Inventory |
| 575511 | "The Location Code field must be blank for items of type Non-Inventory" error occurs in a planning worksheet in the Planning Components when you change the Quantity field. | Inventory |
| 575725 | Looking up the Item Availability by Event on the Item Card opens the incorrect and last used planning worksheet batch. | Inventory |
| 578318 | The reservation of an item can be on a transfer order even if the item is set to "Reserve = Never". | Inventory |
| 579001 | Recalculating an item in a requisition or planning worksheet that has no planning results causes incorrect surplus entries in the reservation table that are added to the Item Tracking page. | Inventory |
| 580053 | Fix the issue where the Shelf No. value is taken from the item card instead of the Stockkeeping Unit when creating an inventory pick. | Inventory |
| 580738 | Enabling the SN Assembly Tracking in version 26.x doesn't block you from posting without assigning a SN. | Inventory |
| 581025 | Fix the slow performance of the average cost calculation in the specific scenario. | Inventory |
| 575091 | The Recurring Project Journal is inconvenient to use because the posted lines need to be revalidated to get the unit amounts again for the next posting. | Jobs |
| 580089 | When setting the Task Billing Method to Multiple Customers, the Send Project Task Quote in Project Task Card doesn't provide the same file name structure as the Send Project Quote in Project Card. | Jobs |
| 578063 | The input quantity and related production time aren't recalculated in a released production order when using the Replan function. | Manufacturing |
| 580074 | "Lot No. XXX is not available on inventory, or it has been reserved for another document" error occurs when the reservation binding (order-to-order) doesn't allow a partial shipment to be posted on a particular LOT if the inventory pick is used. | Manufacturing |
| 581071 | Fix the device license permission issues caused by missing permissions for TableData 5405 Production Order in Business Central version 26.0. | Manufacturing |
| 579288 | When you enter the vendor name in a purchase order, the selection box for possible vendors doesn't display. | Purchase |
| 580422 | The VAT rounding is incorrect when using the Get Recurring Purchase Lines functionality on the Purchase Invoice. | Purchase |
| 574903 | The sales invoice can be created with a line of Type Item for an Item No. which has a default Purchasing Code of Drop Shipment, but can't be processed due to errors related to a missing linked purchase order. | Sales |
| 575809 | Printing a sales invoice is voided if you post and send a Sales Order with the Ship and Invoice option. | Sales |
| 578424 | When using the Cancel action on a partial sales or purchase invoice related to an existing order, a message is needed to inform that the order quantities are changed. | Sales |
| 578445 | Incorrect quantities and inconsistent results occur in the existing sales order when creating a credit memo with the Create Corrective Credit Memo action. | Sales |
| 578460 | When using the Create Corrective Credit Memo action on a partial sales or purchase invoice related to an existing order, a message is needed to inform that the order quantities are changed. | Sales |
| 579476 | Fix an issue where the Assign-to field is disabled when you print the item price list on the report request page. | Sales |
| 580152 | The tooltip for the Correct field in the posted sales invoice is incorrect. | Sales |
| 580263 | "There is nothing to post because the document does not contain a quantity or amount" error occurs when you try to batch post Released Sales Orders with Currency and replace the Posting Date, and the status of the order changes to Open. | Sales |
| 581596 | The expiration date disappears from the item tracking lines after adding or modifying the Promised Delivery Date field. | Sales |
| 575244 | Incorrect capacity warnings occur due to the wrong calculation when calculating the Bin Replenishment in a movement worksheet. | Warehouse |
| 575737 | When manually adding a Bin Content line, the Qty. per Unit of Measure field on the Bin Content Page defaults to 1 for an item with a different UOM and a quantity greater than 1 in this field. | Warehouse |
| 581463 | The availability error occurs when creating a pick from the pick worksheet when the location setup has Bin Mandatory and the item is reserved on the related production order. | Warehouse |
Local application hotfixes
AU - Australia
| ID | Title | Functional Area |
|---|---|---|
| 581871 | Posting dates and months are incorrectly categorized with Column Labels in Pivot Mode of Analysis View in the Australian version. | Finance |
BE - Belgium
| ID | Title | Functional Area |
|---|---|---|
| 579709 | "It is not possible to display in a field with a length of 12" error occurs when suggesting a domiciliation in the domiciliation journal in the Belgian version. | Finance |
CA - Canada
| ID | Title | Functional Area |
|---|---|---|
| 578826 | The remittance advice generated from the Payment Journals page isn't accurate when the invoices being paid are in a foreign currency in the Canadian version. | Cash Management |
| 574067 | "The length of the string is XXXX, but it must be less than or equal to 1024 characters" error occurs when importing a CSV file through the bank reconciliation journal in the Canadian version. | Finance |
CH - Switzerland
| ID | Title | Functional Area |
|---|---|---|
| 579173 | The information isn't fully displayed in the report when using QR invoices to print posted sales invoices in the Swiss version. | Finance |
CZ - Czechia
| ID | Title | Functional Area |
|---|---|---|
| 579269 | The Import Tariff Numbers XMLport doesn't match the current XML Schema in the Czech version. | Finance |
DE - Germany
| ID | Title | Functional Area |
|---|---|---|
| 574648 | Fix an issue where the Sales Order Amount and Sales Invoice Amount are tripled in Customer Card Statistics in the German version. | Finance |
| 580032 | The PEPPOL invoice with a zero amount isn't generated correctly and fails validation in the German version. | Finance |
DK - Denmark
| ID | Title | Functional Area |
|---|---|---|
| 574200 | The discrepancy in the handling of the IBAN code and G/L account code for domestic transfers in the Danish version. | Cash Management |
ES - Spain
| ID | Title | Functional Area |
|---|---|---|
| 571556 | Unbalanced entries occur if you settle invoices to Cartera through Payment Order with Multiple Posting Groups in the Spanish version. | Finance |
| 575499 | The Exported to Payment File field is set to True in all bills with the same document number when only one bill entry is exported in the payment journal in the Spanish version. | Finance |
| 576379 | The txt file generated from the VAT statement file is filtered by Posting Date instead of VAT Date in the Spanish version. | Finance |
| 580846 | The Adjust Exchange Rate doesn't work as expected when posting or settling a payment order in Currencies in the Spanish version. | Finance |
FR - France
| ID | Title | Functional Area |
|---|---|---|
| 579514 | The CompAuxNum field and the CompAuxLib field aren't informed in the Audit File Export when using Multiple Posting Groups in the French version. | Finance |
| 580072 | The G/L Trial Balance report shows incorrect opening balances in the French version. | Finance |
| 580424 | The Last No. Used field in the No. Series line doesn't increment when the Payment Slip lines are entered manually. It only increments when using the Suggest function in the Payment Slip in the French version. | Finance |
GB - United Kingdom
| ID | Title | Functional Area |
|---|---|---|
| 574390 | The Name field is blank in the Vendor - Top List Excel (Report ID: 4404) report when Vendor No. contains an ampersand (&) character in the British version. | Integration |
IT - Italy
| ID | Title | Functional Area |
|---|---|---|
| 580569 | Issue with Document Occurrence number when using the Vendor Bill Card in the Italian version. | Finance |
NA - North America
| ID | Title | Functional Area |
|---|---|---|
| 580990 | Issue with the Bank Reconciliation Test report in the North American version. | Finance |
NL - Netherlands
| ID | Title | Functional Area |
|---|---|---|
| 572705 | Error occurs when creating a purchase order on the project planning lines in the Dutch version. | Finance |
NO - Norway
| ID | Title | Functional Area |
|---|---|---|
| 579823 | Issue with VAT Calculation from Reverse Charge and Partial Deduction in Mixed-Invoice scenarios in the Norwegian version. | VAT/Sales Tax/Intrastat |
NZ - New Zealand
| ID | Title | Functional Area |
|---|---|---|
| 575123 | Unable to enter the 13-digit NZBN on the Company Information page in the New Zealand version. | Finance |
SE - Sweden
| ID | Title | Functional Area |
|---|---|---|
| 575346 | The rounding issue causes the "Inconsistency" error when trying to post with different currency and automatic accounting in the Swedish version. | Finance |
US - United States
| ID | Title | Functional Area |
|---|---|---|
| 578826 | The remittance advice generated from the Payment Journals page isn't accurate when the invoices being paid are in a foreign currency in the United States version. | Cash Management |
| 574067 | "The length of the string is XXXX, but it must be less than or equal to 1024 characters" error occurs when importing a CSV file through the bank reconciliation journal in the United States version. | Finance |
| 574648 | Fix an issue where the Sales Order Amount and Sales Invoice Amount are tripled in Customer Card Statistics in the United States version. | Finance |
Resolution
Which hotfix package to download
This update has multiple hotfix packages. Select and download one of the following packages depending on the country version of your Microsoft Dynamics 365 Business Central 2025 database.
How to install a Microsoft Dynamics 365 Business Central on-premises 2025 Release Wave 1 update
See How to install a Microsoft Dynamics 365 Business Central 2025 Release Wave 1 update.
Prerequisites
You must have Microsoft Dynamics 365 Business Central 2025 Release Wave 1 installed to apply this hotfix.
More information
See more information about software update terminology and Microsoft Dynamics 365 Business Central 2025 Release Wave 1.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.