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 |
|---|---|
| 562348 | Improved performance when generating AL callstack. |
| 562647 | Support plus sign in field names when editing in Excel. |
| 563006 | $batch requests to a custom API $batch endpoint do not perform rollbacks. |
| 563602 | Reenable full text indexes after a cloud migration. |
| 564145 | Avoid locking when retrieving translatable texts. |
| 563612 | Avoid unnecessary generation of media thumbnails. |
| 563572 | Duplicate table names break RecordId evaluation. |
| 563600 | Full text index task does not run when tenant is misconfigured. |
| 563575 | Only allow modern search but not only extension fields when base table is optimized. |
| 563045 | Running Analysis mode of a query does not respect the SetRange filter. |
| 563898 | Improve resilience of container startup and ensure shared fonts folders are not removed. |
| 560428 | Improve the TenantApplicationStorageRepo query to fix the "Could not continue scan with NOLOCK due to data movement" error. |
| 563337 | Customer license cannot be used because of missing non-universal codes. |
Application hotfixes
| ID | Title | Functional Area |
|---|---|---|
| 560355 | "The transaction cannot be completed because it will cause inconsistencies in the G/L Entry table" error message when trying to post a purchase document with Currencies, Non-Deductible VAT and the VAT Amount modified in the Statistics. | Finance |
| 561635 | "Journal Source Code BANKREC is not same as default Source Code set for Gen. Journal Template with type General..." error message when performing a transfer to the General Journal due to a default deferral on the selected G/L account. | Finance |
| 562108 | Discrepancies on the G/L Currency Revaluation and the Exchange Rate Adjustments reports. | Finance |
| 562688 | Filters stop saving in the Create Reminders Setup table on the Reminder Automation page. | Finance |
| 563058 | Alternative Customer VAT Registration issue when using the Bill to customer and Ship-to-code. | Finance |
| 563607 | Issues with Gen. Jnl.-Post Line procedure (PostDtldCVLedgEntry). | Finance |
| 560778 | The Line Separator field is excluded during the export of the Data Exchange Definition, but it is included during the import process. | Integration |
| 561854 | The VAT posting group in the General Journal should follow the batch setup when created by the API. | Integration |
| 560785 | When converting the Planned Production Order with specified Lot Tracking and the Prospect Reservation Entry into a Released Production Order, the Prospect Reservation Entry isn't changed to the Surplus Entry. As a result, when running the Planning, it suggests a new Production Order on the Planning line. | Inventory |
| 561210 | "The Reservation Entry does not exist. Identification fields and value Entry No=xx, Positive='Yes'" error message when the Order Tracking Policy of the Drop Ship Item is set as Tracking Only, and the planning is run to break the reservation records for this item. | Inventory |
| 561585 | The calculation of Gross Requirement is incorrect in the Show Availability when a non-base Unit of Measure is used on the Assembly Component. | Inventory |
| 547582 | If the reservation line of a Sales Order is linked to a direct Transfer Order (before posting), even if the Transfer Order is posted, it will not be linked back to the line in item ledger entries. | Inventory |
| 555810 | Incorrect reservation entries when using an Older Tracking Policy and Item Tracking. | Inventory |
| 561174 | Cannot post a purchase invoice with item charge when the receipt lines are assigned to a location that has dimension of code mandatory. | Inventory |
| 561866 | The Item Dimensions - Detail report shows incorrect cost amounts for Transferred items. | Inventory |
| 562986 | The Reserved From Stock value has Partial status on the Statistics page of a sales order when there is non-inventory item in sales lines. | Inventory |
| 562548 | "The record in table G/L Entry already exists. Identification fields and values: Entry No.=XXX" error when trying to post a pick with an assembly item for a project. | Jobs |
| 556710 | The Ending Date/Time in the Production Order Line is incorrect when there's a remaining quantity lower than the Quantity field value. | Manufacturing |
| 560520 | After calculating a planning worksheet, the Expiration Date value of an item tracking line of a released production order has been cleared. | Manufacturing |
| 551593 | The purchase order quantity can't be changed to zero when the item does not have a direct unit cost. | Purchase |
| 560682 | Issues with the Payment Discount validation of a created purchase invoice via an API endpoint. | Purchase |
| 562691 | Status must be equal to Open in the purchase header when posting a purchase invoice that was released and having an allocation account in one of its lines. | Purchase |
| 557866 | Invoice discounts are validated automatically to the sales order when the posting date is changed. | Sales |
| 561021 | Global dimensions 1 and 2 are not copied to the Sales and Purchase Documents lines when using the Copy Document function, even if the global dimensions are visible under linked dimensions. | Sales |
| 557299 | Sales return order throws unit of measure error when copying a document from a posted sales invoice with an automatically added G/L rounding line. | Sales |
| 562007 | Blanket sales order cannot be selected in a sales order return. | Sales |
| 561140 | Permission error when trying to change the VAT date in VAT entries. | VAT/Sales Tax/Intrastat |
| 561297 | Issue when registering the pick after using the split lines functionality in Warehouse Pick. | Warehouse |
| 561597 | "Item Tracking Serial Number SNxxx Lot No for the Item No. xxx Variant cannot be fully applied" error message when trying to post the Warehouse Shipment after registering a pick for a different Serial Number reserved from a different Sales Order. | Warehouse |
| 561744 | Unable to create a purchase order for items configured for directed put-away and pick locations. | Warehouse |
| 562672 | Item Tracking is not populated by the Get Bin Content function in an item reclassification journal or a Transfer Order. | Warehouse |
Local application hotfixes
AT - Austria
| ID | Title | Functional Area |
|---|---|---|
| 561413 | Issues with the Standard Cost calculation when it includes a non-inventory item in the Austrian version. | Manufacturing |
CH - Switzerland
| ID | Title | Functional Area |
|---|---|---|
| 562965 | Amount (FCY) has a value which causes imbalance when posting a purchase invoice with payables account that has currency code in the Swiss version. | Finance |
CZ- Czechia
| ID | Title | Functional Area |
|---|---|---|
| 560750 | Excluding vendor ledger entries that are on hold from compensation in the Czech version. | Finance |
| 563560 | New format DPHDP3 v. 3.0.1 when exporting the VAT Statement and VAT report in the Czech version. | VAT/Sales Tax/Intrastat |
DE - Germany
| ID | Title | Functional Area |
|---|---|---|
| 561413 | Issues with the Standard Cost calculation when it includes a non-inventory item in the German version. | Finance |
| 561778 | Incorrect details when creating an Intrastat xml file in the German version. | Manufacturing |
ES - Spain
| ID | Title | Functional Area |
|---|---|---|
| 561864 | The total number of documents and the total amount are missing in the Receivables and Payable Docs FactBox in the Spanish version. | Cash Management |
| 561824 | The 349 Declaration incorrectly exports information if Credit Memos are included, while some of the Credit Memos has the Corrected Invoice No. filled, and the others haven't in the Spanish version. | Finance |
| 561052 | Purchase documents do not bring the Special Scheme Code 07. Special Cash automatically for the VAT Prod Posting Groups marked with the VAT cash regime in the Spanish version. | Finance |
| 563402 | Credit Memo applied to Posted Invoice with bills uses an incorrect G/L account and the entries do not balance in case the first Detailed Ledger Entry value in the system has a payment method that creates bills in the Spanish version. | Finance |
| 561939 | Dispute Status is not visible in the Update Document option for the Posted Sales Invoice in the Spanish version. | Sales |
| 561437 | The 349 Declaration does not work as expected with Non. Deductible VAT when not all locations are within the EU in the Spanish version. | VAT/Sales Tax/Intrastat |
FI - Finland
| ID | Title | Functional Area |
|---|---|---|
| 560856 | The Currency filter is not taken into account when trying to send a page using the Suggest Vendor Payments functionality from the Bank Payment in the Finnish version. | Cash Management |
FR - France
| ID | Title | Functional Area |
|---|---|---|
| 561149 | The No. Series does not increment when Payment Slip lines are entered manually in the French version. | Finance |
GB - United Kingdom
| ID | Title | Functional Area |
|---|---|---|
| 561295 | "The Reservation Entry does not exist. Identification fields and values: Entry No.='7'Positive='Yes'" error message when trying to ship a Sales Order if the Order Tracking Policy is set for an item with a Reorder Policy of Lot-for-Lot and the Special Order is involved in the British version. | Inventory |
| 561935 | The Non-deductible VAT does not display as non-deductible when performing full VAT in the British version. | VAT/Sales Tax/Intrastat |
IT - Italy
| ID | Title | Functional Area |
|---|---|---|
| 560063 | The Update on Posting feature does not function as expected in the Italian version. | Finance |
| 560915 | The Total Weight field value is incorrect in the Intrastat report in the Italian version. | Inventory |
US - United States
| ID | Title | Functional Area |
|---|---|---|
| 561458 | Cannot apply partial credit on a payment and it shows difference in the balance amount in the United States version. | Cash Management |
| 562313 | When creating a new 1099 reporting year and copying from an existing year, the Adjustment Amounts value is also copied, which should not be automatically copied in the United States version. | Finance |
| 562184 | "The operation cannot be performed on a closing date value" error message when trying to print an accurate year-end trial balance. Specifically, the Trial Balance with Spread Global Dimension doesn't not include entries with a closing date in the United States version. | Finance |
| 562320 | The full 4-digit year must be printed instead of the 2-digit year for the 2022 and 2023 in the 1099 form if the 1099 report printed for 2024 in the United States version. | Finance |
| 561585 | The calculation of Gross Requirement is incorrect in the Show Availability when a non-base Unit of Measure is used on the Assembly Component in the United States version. | Inventory |
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.