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 2024 Release Wave 2, see released updates for Microsoft Dynamics 365 Business Central 2024 Release Wave 2. Updates are intended for new and existing customers who are running Microsoft Dynamics Released Updates for Microsoft Dynamics 365 Business Central 2024 Release Wave 2.
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 |
|---|---|
| 579662 | Unable to add a field using customization when the profile name contains an ampersand (&) character. |
| 580029 | The client uses incorrect custom dimensions when two sessions have the same client session ID. |
| 581161 | Increase the timeout for the upgrade step that repairs system ID and key names. |
| 581313 | Provide better error messages for timeouts. |
Application hotfixes
| ID | Title | Functional Area |
|---|---|---|
| 563299 | The Payment Discount Tolerance Warning occurs when it shouldn't. | Finance |
| 568657 | Error occurs when creating a purchase order on the project planning lines. | Finance |
| 572340 | The price isn't updated correctly based on Price Lists in Service Objects when the Quantity field is changed. | Finance |
| 572623 | Error occurs when editing the Power BI Account Categories page if the G/L Account Category field contains the special character ')'. | Finance |
| 573517 | Incorrect cost is posted in Value Entries of the item charge when using non-deductible VAT with the Prices Including VAT field. | Finance |
| 573611 | The Statistical Account Balance generates a filter error when you choose to exclude closing entries and view the page as Balance at Date. | Finance |
| 574025 | When updating the Item, Resource, or G/L Account codes, it is not correctly reflected in the Project Planning Lines. | Finance |
| 579147 | Incorrect Deferral Schedule Values are incorrectly kept when you refresh the page or close the browser. | Finance |
| 579724 | The non-deductible VAT amount is incorrect in the project ledger entry when the project has a foreign currency. | Finance |
| 572008 | The invoice discount can be modified without restrictions after sending the approval request and the status is Pending Approval in the document. | Integration |
| 575040 | 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 |
| 575484 | Looking up the Item Availability by Event on the Item Card opens the incorrect and last used planning worksheet batch. | Inventory |
| 573751 | 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 |
| 578185 | 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 |
| 565975 | The input quantity and related production time aren't recalculated in a released production order when using the Replan function. | Manufacturing |
| 566055 | "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 |
| 571395 | The VAT rounding is incorrect when using the Get Recurring Purchase Lines functionality on the Purchase Invoice. | Purchase |
| 578825 | When you enter the vendor name in a purchase order, the selection box for possible vendors doesn't display. | Purchase |
| 572934 | Fix an issue where the Assign-to field is disabled when you print the item price list on the report request page. | Sales |
| 578963 | "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 |
| 571432 | Incorrect capacity warnings occur due to the wrong calculation when calculating the Bin Replenishment in a movement worksheet. | Warehouse |
| 575862 | 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
BE - Belgium
| ID | Title | Functional Area |
|---|---|---|
| 571303 | "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 |
| 581693 | Fix the issue when using the Enterprise No. with the multiple VAT in the Belgian version. | Finance |
CA - Canada
| ID | Title | Functional Area |
|---|---|---|
| 576329 | 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 |
CH - Switzerland
| ID | Title | Functional Area |
|---|---|---|
| 579172 | 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 |
|---|---|---|
| 578548 | Fix the issue with additional currency and inventory valuation in the Czech version. | Inventory |
ES - Spain
| ID | Title | Functional Area |
|---|---|---|
| 573478 | 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 |
|---|---|---|
| 575798 | 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 |
IT - Italy
| ID | Title | Functional Area |
|---|---|---|
| 571990 | Issue with Document Occurrence number when using the Vendor Bill Card in the Italian version. | Finance |
MX - Mexico
| ID | Title | Functional Area |
|---|---|---|
| 564932 | Fix the issue where the value is 0 in the CertificadoOrigen field in the Mexican version. | Sales |
NL - Netherlands
| ID | Title | Functional Area |
|---|---|---|
| 568657 | Error occurs when creating a purchase order on the project planning lines in the Dutch version. | Finance |
US - United States
| ID | Title | Functional Area |
|---|---|---|
| 576329 | 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 |
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 2024 database.
How to install a Microsoft Dynamics 365 Business Central on-premises 2024 Release Wave 2 update
See How to install a Microsoft Dynamics 365 Business Central 2024 Release Wave 2 update.
Prerequisites
You must have Microsoft Dynamics 365 Business Central 2024 Release Wave 2 installed to apply this hotfix.
More information
See more information about software update terminology and Microsoft Dynamics 365 Business Central 2024 Release Wave 2.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.