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 |
|---|---|
| 574992 | The OrderBy filter isn't respected when the SourceTableView page is defined. |
| 575093 | Removing an obsoleted field and reintroducing it with a new name should cause a drop and recreate operation instead of renaming it. |
| 575602 | Fix language translation inconsistencies in Business Central. |
| 578184 | "Could not open the company" error occurs when you use the "Do not link to a specific company" option of the Copy Link functionality in Analysis View mode and try to run it. |
| 578496 | The upgrade might fail with a lock timeout when the Sync-NAVTenant cmdlet is executed with the CommitPerTable parameter set to true. |
| 578560 | Fixes an issue that causes chat to fail to retrieve relevant records. |
| 579260 | The session might crash when reports are sent to Excel using the Microsoft Excel Document (data only) option. |
Application hotfixes
| ID | Title | Functional Area |
|---|---|---|
| 572709 | "A reminder attachment text cannot be created without an ID" error occurs when adding text for language in Reminder Level Communication. | Finance |
| 574340 | Fix the issue where all reminders for all customers are sent to a specific customer. | Finance |
| 574606 | "An error occured and the transaction is stopped" error occurs when adding text for language in Reminder Level Communication. | Finance |
| 574746 | The Use for Job Cost field should be renamed to Use for Project Cost in VAT Setup. | Finance |
| 575100 | The Source Currency Amount is calculated incorrectly when the VAT calculation type is Reverse Charge in the VAT posting setup and the posting is done via the journal. | Finance |
| 575653 | The security filter applied to the G/L Account table causes an error on the General Ledger Entries page. | Finance |
| 575756 | The Unit Cost field in Project Ledger Entries is incorrect when partially invoicing after receiving the full quantity with the non-deductible VAT setting. | Finance |
| 575775 | Unable to correct a posted invoice with an item that has Dimension Code Mandatory. | Finance |
| 575777 | "The value '0,X' can't be evaluated into type Decimal." error occurs when you try to evaluate the selected model on the Late Payment Prediction Setup page with the Dutch (Belgium) region. | Finance |
| 576358 | The Closed at Date field doesn't reflect correctly when applying entries on the Vendor Ledger Entries page and the Customer Ledger Entries page. | Finance |
| 579148 | Incorrect deferred schedule values are incorrectly kept when you refresh the page or close the browser. | Finance |
| 579186 | The Import from Allocation Accounts action in recurring general journals doesn't import dimensions. | Finance |
| 579320 | The Source Currency Amount carries the Vat Amount in the General Ledger Entries. | Finance |
| 575624 | The Item No. field can't be changed if it's too long when the Variant Code field is set up in version 26.x. | Integration |
| 578818 | After running the synchronization for products to pull Shopify products into Business Central, the products in Shopify are archived. | Integration |
| 571565 | The same serial number can be in stock twice. | Inventory |
| 572185 | The Auto Reserve function doesn't reserve the full quantity for the Sales Lines. | Inventory |
| 574250 | After posting and generating value entries with variant codes and a blank variant code for the item, an error occurs when trying to change (renumber) the Item No. field. | Inventory |
| 574691 | "Bin Code must be equal to '' in Requisition Line: Worksheet Template Name=BESTVOR" error occurs when using the Carry Out Action Message function in the requisition worksheet for a drop shipment with a Transfer SKU and Bin Contents. | Inventory |
| 575231 | Using the order tracking policy of Tracking & Action Message and Lot Specific Tracking can result in damaged Reservation Entries with Inventory Picking. | Inventory |
| 578435 | After undoing an assembly order with item tracking, the item is undefined and the quantity base is incorrect. | Inventory |
| 569523 | The Prospect Reservation Entry is orphaned and not updated to Surplus for Item Tracking when moving a project from "status = quote" to "status = open". | Jobs |
| 574938 | Creating a purchase order from the project doesn't work as expected if you add Project Planning Lines before the previous ones. | Jobs |
| 575563 | The Job Planning Lines are slow due to checking if the variant code is mandatory. | Jobs |
| 574344 | The routing of the MTO Finished Good item in a production order is incorrect when it is part of a family. | Manufacturing |
| 574595 | The Invt. Picks to Production list doesn't display correctly when using the Manufacturing Manager role. | Manufacturing |
| 578476 | The Routing No. field can be deleted after changing the routing status to Finished. | Manufacturing |
| 571560 | The Default Remit-to-Code doesn't default to a new Purchase Invoice document when it's created from Vendor Card and the associated No. Series has both Default and Manual options marked. | Purchase |
| 572197 | The Line Discount % field disappears after adding the Project No. field and then the Project Task No. field to a purchase order line. | Purchase |
| 573781 | The tooltip for the Check Doc. Total Amounts field on the Purchases & Payables page is incorrect. | Purchase |
| 574639 | "The length of the string is XX but it must be less than or equal to 20 characters" error occurs when working with opportunities. | Purchase |
| 575811 | The Capable to Promise Date is calculated incorrectly when a Vendor Item Catalog relation is created and both the Safety Lead Time (Manufacturing Setup) and the Order Promising Off time are set. | Purchase |
| 573330 | The sales invoice can post lines for a location with directed put-away and pick without a warehouse shipment. | Sales |
| 573758 | Blocking the "Attempted to divide by zero" error when unticking Allow Invoice Discount on a sales invoice where calculated invoice discounts are redistributed to certain lines. The sales invoice can't be reopened anymore. | Sales |
| 575507 | The inventory receipt posts with zero cost when the VAT Setup is set to use non-deductible VAT. | Sales |
| 575847 | When creating a credit memo for a sales invoice with a drop shipment using the Correct action, the purchase order isn't corrected, and you can't post the sales order. | Sales |
| 579221 | The security filters on the price list line cause an inability to open the item card. | Sales |
| 575353 | The alternative posting group in Service Management doesn't use the correct G/L accounts for posting. | Service Management |
| 577995 | The calculated amounts of the source amount in the VAT entries are incorrect when using the G/L currency revaluation with non-deductible VAT. | VAT/Sales Tax/Intrastat |
| 568065 | The warehouse shipment line in a transfer order disappears after the Preview Posting action. | Warehouse |
| 568444 | "Qty. to Handle (Base) in the item tracking assigned to the document line for item 70061 is currently 4. It must be 8." error occurs when trying to post a warehouse shipment with several registered picks. | Warehouse |
| 572913 | "Nothing to Handle" error occurs where a Movement and a blank expiration date exist when creating a warehouse pick for an item with serial tracking that has Strict Expiration Date enabled. | Warehouse |
| 574142 | "Nothing to Handle" error occurs when creating the put-away from the posted warehouse receipt. | Warehouse |
| 574591 | The purchase order line can be deleted when a warehouse receipt exists. | Warehouse |
| 576019 | "Item tracking defined for source line xx of Prod. Consumption xx amounts to more than the quantity you have entered. You must adjust the existing item tracking specification..." error occurs when using the Allow Whse. Overpick setting with the item tracking and registering the Pick. | Warehouse |
| 578466 | Fix the regression in the extensibility after fixing the warehouse pick when using alternative units of measure. | Warehouse |
| 579219 | Improve the extensibility of Whse. Get Bin Content.GetItemTracking(). | Warehouse |
Local application hotfixes
APAC
| ID | Title | Functional Area |
|---|---|---|
| 578915 | Fix an issue on the GST Entries page in the APAC version. | Finance |
AU - Australia
| ID | Title | Functional Area |
|---|---|---|
| 578915 | Fix an issue on the GST Entries page in the Australian version. | Finance |
BE - Belgium
| ID | Title | Functional Area |
|---|---|---|
| 571558 | CODA statement lines for customers and vendors with currency are incorrectly transferred to the Financial Journal if the currency of the bank is the local currency (blank) in the Belgian version. | Finance |
CA - Canada
| ID | Title | Functional Area |
|---|---|---|
| 576020 | When a remittance is voided, for a payment that's manually created, the vendor documents are unapplied to the payment in the Canadian version. | Cash Management |
| 574564 | Fix the sales tax difference in the Canadian version. | Finance |
| 574639 | "The length of the string is XX but it must be less than or equal to 20 characters" error occurs when working with opportunities in the Canadian version. | Purchase |
CZ - Czechia
| ID | Title | Functional Area |
|---|---|---|
| 575023 | Extend the column width in the Cash Flow Date List report in the Czech version. | Finance |
| 579248 | The caption of category_new is missing on the unreliable payer entries page in the Czech version. | Finance |
| 578547 | Fix the issue with additional currency and inventory valuation in the Czech version. | Inventory |
| 579244 | "Attempted to divide by zero" error occurs in the Phys. Inventory Document CZL report (Report 31073) in the Czech version. | Inventory |
| 573307 | The VAT currency factor isn't posted correctly with non-deductible VAT in the Czech version. | VAT/Sales Tax/Intrastat |
DE - Germany
| ID | Title | Functional Area |
|---|---|---|
| 575416 576028 |
The CSV file format for the VAT Vies Declaration report (Report 88) is outdated in the German version. | Finance |
| 575756 | The Unit Cost field in Project Ledger Entries is incorrect when partially invoicing after receiving the full quantity with the non-deductible VAT setting in the German version. | Finance |
| 571565 | The same serial number can be in stock twice in the German version. | Inventory |
ES - Spain
| ID | Title | Functional Area |
|---|---|---|
| 574350 | Unbalanced entries occur if you settle more than one bill through Payment Order with Multiple Posting Groups in the Spanish version. | Finance |
| 575521 | The Total field in the Purchase Invoice Book report is incorrect when you use non-deductible VAT in the Spanish version. | Finance |
| 575779 | The Remaining Amount (LCY) stats. field is incorrect after unapplying a credit memo and a bill in the Spanish version. | Finance |
| 578360 | The CONSISTENT error occurs when trying to run the Close Income Statement in the Spanish version. | Finance |
| 574907 | The Get Posted Document Lines to Reverse action from the Posted Sales Shipment doesn't bring the Equivalence Charge correctly in the Spanish version. | Inventory |
FR - France
| ID | Title | Functional Area |
|---|---|---|
| 575576 | The voided check in the vendor ledger entries is generated with the wrong vendor posting group when the Allow Multiple Posting Groups setting is enabled in the French version. | Finance |
| 575796 | The Allow Deferral Posting From and Allow Deferral Posting To fields are incorrectly translated in the French version. | Finance |
GB - United Kingdom
| ID | Title | Functional Area |
|---|---|---|
| 575529 | Posting a purchase invoice with a non-deductible VAT amount incorrectly posts to the depreciation expense account instead of the fixed asset cost account in the British version. | Finance |
| 579647 | Fix the postcode lookup when using the GetAddress.io extension in the British version. | Finance |
| 574250 | After posting and generating value entries with variant codes and a blank variant code for the item, an error occurs when trying to change (renumber) the Item No. field in the British version. | Inventory |
MX - Mexico
| ID | Title | Functional Area |
|---|---|---|
| 576415 | Fix the issue where the value is 0 in the CertificadoOrigen field in the Mexican version. | Sales |
NA - North America
| ID | Title | Functional Area |
|---|---|---|
| 574564 | Fix the sales tax difference in the North American version. | Finance |
| 575653 | The security filter applied to the G/L Account table causes an error on the General Ledger Entries page in the North American version. | Finance |
| 579112 | When running the Inventory Movement report as RDLC (report ID 7301), it doesn't populate the variant code in the report layout in the North American version. | Inventory |
NL - Netherlands
| ID | Title | Functional Area |
|---|---|---|
| 576358 | The Closed at Date field doesn't reflect correctly when applying entries on the Vendor Ledger Entries page and the Customer Ledger Entries page in the Dutch version. | Finance |
SE - Sweden
| ID | Title | Functional Area |
|---|---|---|
| 576243 | The Automatic Account Groups aren't populated to the general journal line when using the Copy G/L Register to Journal Line function in the Swedish version. | Finance |
US - United States
| ID | Title | Functional Area |
|---|---|---|
| 576020 | When a remittance is voided, for a payment that's manually created, the vendor documents are unapplied to the payment in the United States version. | Cash Management |
| 574564 | Fix the sales tax difference in the United States version. | Finance |
| 575713 | Posting a sales invoice after posting a prepayment invoice for 70% with a currency code of EUR in a USD company generates an inconsistency error, which is due to rounding in the G/L entries in the US localized database in the United States version. | Finance |
| 571565 | The same serial number can be in stock twice in the United States version. | Inventory |
| 579112 | When running the Inventory Movement report as RDLC (report ID 7301), it doesn't populate the variant code in the report layout in the United States version. | Inventory |
| 571560 | The Default Remit-to-Code doesn't default to a new Purchase Invoice document when it's created from Vendor Card and the associated No. Series has both Default and Manual options marked in the United States version. | Purchase |
| 571832 | When creating a new sandbox or tenant in the United States, the CRONUS USA, Inc. isn't created with the completed 1099 Form Boxes, which should be added by default for any company in a US tenant in the United States version. | Purchase |
| 574870 | The Aging Band Totals don't show a value in the latest band period in the Customer Statement report 1316 in the United States version. | Sales |
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.