This article applies to Microsoft Dynamics 365 Business Central 2019 Release Wave 2 for all countries and all language locales.
This update also addresses a vulnerability related to the NAVRecordState state. To learn more about the vulnerability, go to CVE-2020-1022.
Overview
This update replaces previously released updates. You should always install the latest update.
It may be necessary to update your license after you install this hotfix to gain access to new objects that are included in this or a previous update. (This only applies to customer licenses.) For a list of updates that were released for Microsoft Dynamics 365 Business Central 2019 Release Wave 2, see released updates for Microsoft Dynamics 365 Business Central 2019 Release Wave 2. Updates are intended for new and existing customers who are running Microsoft Dynamics Released Updates for Microsoft Dynamics 365 Business Central 2019 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 |
|
342848 |
Activity Cues are not displayed correctly if they span more than one line in the Web client. |
|
347523 |
The client stops working when you open the Item Quantities page. |
|
347149 |
The browser stops working when you use the extension. |
|
349589 |
The Pending status will not to be documented. |
|
346773 |
Installation fails if the Dynamics NAV Server cannot start. |
|
340227 |
"The following SQL error was unexpected: Invalid object name '<DB Name>.dbo.CRONUS France S_A_$Activities Cue'" error message displays when you export to a data file. |
|
347830 |
Some values are stored with both uppercase and lowercase characters in the System tables of the server instance and active session. |
|
343641 |
You cannot open list pages if you change the Item SQL Data Type property of the No. field to Variant in the Item table. |
|
347447 |
"Filter is not valid - Did not expect " error message displays when you try to filter on Payment Terms Code 1M(8D). |
Application hotfixes
|
ID |
Title |
Functional Area |
|
343390 |
If you export data classifications to Excel, Business Central will export all lines without sorting data classification lines by company. |
Administration |
|
343395 |
If you use the local language to export Data Sensitivity lines, the content of the Data Sensitivity column is always exported in English. |
Administration |
|
346540 |
The Windows User Name field does not persist on the Users list page. |
Administration |
|
343161 |
The Suggest Vendor Payments batch job does not increment number series values correctly. |
Cash Management |
|
342941 |
Cannot remove a match when you use the Suggest Lines action and the auto match function is enabled for bank reconciliations. |
Cash Management |
|
349502 |
When you use the Create Payment function, the payment journal line is created with an incorrect document type. |
Cash Management |
|
341562 |
Journal lines have incorrect dates in general journals. |
Finance |
|
343954 |
"G/L accounts for discounts are missing on one or more lines on the General Posting Setup page" error message displays if G/L accounts related to discounts are missing. |
Finance |
|
344476 |
The top 10 list is not sorted as expected when the Balance (LCY) field is used for the Show parameter. |
Finance |
|
344608 |
Allocated costs are assigned to a blocked cost center. |
Finance |
|
343318 |
Blocked and non-standard dimension values can be added to the G/L Budget Entries page. |
Finance |
|
345324 |
You can post unbalanced G/L entries by using a reversing recurring journal although the Force Doc. Balance check box is chosen. |
Finance |
|
346478 |
The incorrect table has relation in the Statement No. field in the Posted Payment Recon. Line table. |
Finance |
|
346507 |
The caption and tooltip of the Allow G/L Acc. Deletion Before field in the General Ledger Setup table/page do not provide enough information. |
Finance |
|
347930 |
If you search for the Dimension – Detail report you get two results. |
Finance |
|
349601 |
The Original Pmt. Disc. Possible and the Remaining Pmt. Disc. Possible amounts are incorrect in vendor ledger entries. |
Finance |
|
348186 |
The Document Type field is blank on purchase journals. |
Finance |
|
344021 |
Dimensions are not displayed correctly on archived sales orders. |
Finance |
|
342232 |
The Payment Terms code is blank when the Copy Document function is used. |
Finance |
|
342936 |
Cannot create tariff numbers by choosing the New button in the on-premises version of Business Central. |
Inventory |
|
341354 |
A performance issue occurs when you use the Item Category Code field on the Item card. |
Inventory |
|
345339 |
The filter on the assembly does not work. |
Inventory |
|
349623 |
The inbound transfer of an average cost item is revalued and indirectly contributes to its own cost. |
Inventory |
|
344748 |
Updating an item category does not also update item attributes. |
Inventory |
|
343319 |
On the Item Tracking card, the Require Expiration Dates field is renamed. |
Inventory |
|
345148 |
Section titles Price(LCY), Cost(LCY), Profit(LCY), Price, Cost, Profit) are missing in job statistics. |
Jobs |
|
343277 |
A rescheduled production order is updated with different due dates on the header and lines when the Safety Lead Time field is blank. |
Manufacturing |
|
348573 |
You cannot sort on the Start Date and End Date fields in production orders after upgrading to cumulative update 24. |
Manufacturing |
|
346058 |
"The field Segment No. of table Segment Line contains a value (SM00021) that cannot be found in the related table (Segment Header)." error message displays after you log a segment. |
Marketing |
|
345669 |
The filter for the Company Name field on the Contacts list page does not display the correct result. |
Marketing |
|
347312 |
The Sales Cycle Description field is not displayed when you update an opportunity. |
Marketing |
|
346225 |
When the Reorder Policy field is set to Maximum Qty. Value and a Lead Time Calculation field is added, the requisition worksheet is suggests a value that greater than the maximum quantity. |
Purchase |
|
343962 |
The Ship-to field on purchase quotes contains the customer address instead of the custom address. |
Purchase |
|
342518 |
The Apply from Item Ledger Entry field is blank for a tracked item on a sales order when you make a reservation on a sales return. |
Sales |
|
342792 |
In a prepayment scenario, sales line comments are not displayed for the prepayment invoice if the Compress Prepayment field is set to true. |
Sales |
|
343131 |
The Item Sales by Customer query does not reconcile to the Customer/Item Sales report. |
Sales |
|
345197 |
Sales orders with the same bill-to customer and sell-to customer (where the sell-to customer and bill-to customer are not the same in a document) are not combined into the same invoice that is running the Combine Shipment batch job. |
Sales |
|
345708 |
The address does not change when you choose Another Customer in the Bill-to field on the Sales Invoice page. |
Sales |
|
348238 |
The tooltip for the Freight G/L Acc. No. field is not specific. |
Sales |
|
345942 |
"The length of the string is *, but it must be less than or equal to 250" error message displays in all Power BI embedded scenarios. |
Sales |
|
343716 |
"Cannot match item tracking" error message displays when you perform an inventory pick. |
Warehouse |
|
344614 |
Changing the values in the Lot and Serial No. fields in the inventory pick does not update the item ledger entry and tracking specification when posted. |
Warehouse |
Local application hotfixes
A U - Australia
|
ID |
Title |
Functional Area |
|
347139 |
The printed posted purchase receipt is truncated, and a blank page is printed in the Australian version. |
Purchase |
BE - Belgium
|
ID |
Title |
Functional Area |
|
347949 |
The tooltip for the Minimal Amount field in the VAT Annual Listing report and the VAT Annual Listing - Disk report is incorrect in the Belgian version. |
Finance |
|
343208 |
If you create a vendor payment by using the EB Payment Journal, the Message to Recipient and Exported to Payment File fields are blank in the created vendor ledger entry in the Belgian version. |
Finance |
|
349332 |
The dimension filter for the Suggest Vendor Payments action in the EB Payment Journal does not work in the Belgian version. |
Purchase |
CH - Switzerland
|
ID |
Title |
Functional Area |
|
344746 |
The Sales Page report does not consider the quote variant in the total amount in the Swiss version. |
Sales |
CZ - Czech
|
ID |
Title |
Functional Area |
|
346763 |
Change FA Subclass code on the Fixed Asset card in fixed assets with more depreciation books in the Czech version. |
Fixed Assets |
|
345114 |
"Transaction type must have a value" error message displays when you post a sales shipment for an item of type Service in the Czech version. |
Sales |
DK - Denmark
|
ID |
Title |
Functional Area |
|
349140 |
You cannot export an OIOUBL file to a folder. However, fields to specify the folders are available on the Sales & Receivables Setup page in the Danish version. |
Sales |
ES - Spain
|
ID |
Title |
Functional Area |
|
347886 |
Posting VAT entries from the G/L journal does not check whether there is a customer or a vendor in the transaction in the Spanish version. |
Finance |
FR - France
|
ID |
Title |
Functional Area |
|
344741 |
Service Level <SvcLvl> and Service Level Code <Cd> are missing in the SEPA vendor payment file in the French version. |
Finance |
IT - Italy
|
ID |
Title |
Functional Area |
|
348158 |
The advanced amount in the Periodic VAT Settlement table is not inserted correctly in the Calc. and Post VAT Settlement report in the Italian version. |
Finance |
|
347072 |
Withholding tax is not updated after you post the payment because the withholding tax is zero in the Italian version. |
Finance |
|
343175 |
The posting number is used when the check total error is displayed in the Italian version. |
Purchase |
|
347635 |
The Reason field is not available in the Vendor Bill Withholding Tax table in the Italian version. |
Purchase |
|
346509 |
The withholding tax is not calculated correctly in the vendor bill if you manually change the WHT amount in the Italian version. |
Purchase |
|
345496 |
If you create a split payment VAT line for a service invoice, the Dimensions values of the document header are not reported in the Italian version. |
Sales |
|
345525 |
The Fiscal VAT Register reports the Product Post. description instead of the VAT identifier in the Italian version. |
VAT/Sales Tax/Intrastat |
NA - North America
|
ID |
Title |
Functional Area |
|
343316 |
There is no image or icon for the Change Batch feature in deposits in the North American version. |
Cash Management |
|
345641 |
The Purchase Order Status Related reports are not available in menus in the online version of Business Central. They are available only in the Selections List report in the North American version. |
Purchase |
NL - Netherlands
|
ID |
Title |
Functional Area |
|
345160 |
There is a check for the Entry/Exit Point table when creating an Intrastat file, although this information is not mandatory in the Dutch version. |
Finance |
|
344654 |
The audit file for the tax authority in the report allows only 15 characters in the Document No. field, although Business Central can handle more characters and the file format allows up to 999 characters in the Dutch version. |
Finance |
NO - Norway
|
ID |
Title |
Functional Area |
|
350285 |
The tax information in the SAF-T file is missing for purchase documents in the Norwegian version. |
Finance |
|
349473 |
Incorrect or missing data in exports to the SAF-T file in the Norwegian version. |
Finance |
|
348393 |
Not all G/L accounts export to the SAF-T file in the Norwegian version. |
Finance |
NZ - New Zealand
|
ID |
Title |
Functional Area |
|
347139 |
The printed posted purchase receipt is truncated, and a blank page is printed in the New Zealand version. |
Purchase |
Local regulatory features
BE - Belgium
|
ID |
Title |
Functional Area |
|
349377 |
The PEPPOL implementation is fixed according to partner feedback in the Belgian version. |
Financial Management |
IT - Italy
|
ID |
Title |
Functional Area |
|
345389 |
A new value of Non-Taxable Income Type is added to the withholding tax in the Italian version. |
Financial Management |
NO - Norway
|
ID |
Title |
Functional Area |
|
349377 |
The PEPPOL implementation is fixed according to partner feedback in the Norwegian version. |
Financial Management |
UK - United Kingdom
|
ID |
Title |
Functional Area |
|
349641 |
Make headers update for the Tax Digital FP in the British version. |
Financial Management |
Resolution
How to obtain the Microsoft Dynamics 365 Business Central 2019 Release Wave 2 files
This update is available for manual download and installation from the Microsoft Download Center.
Update 15.5 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2
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 2019 database:
|
Country |
Hotfix package |
|
AT - Austria |
Download update 15.5 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 AT package |
|
AU - Australia |
Download update 15.5 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 AU package |
|
BE - Belgium |
Download update 15.5 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 BE package |
|
CH - Switzerland |
Download update 15.5 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 CH package |
|
CZ- Czech |
Download update 15.5 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 CZ package |
|
DE - Germany |
Download update 15.5 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 DE package |
|
DK - Denmark |
Download update 15.5 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 DK package |
|
ES - Spain |
Download update 15.5 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 ES package |
|
FI - Finland |
Download update 15.5 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 FI package |
|
FR - France |
Download update 15.5 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 FR package |
|
IS - Iceland |
Download update 15.5 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 IS package |
|
IT - Italy |
Download update 15.5 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 IT package |
|
NA - North America |
Download update 15.5 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 NA package |
|
NL - Netherlands |
Download update 15.5 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 NL package |
|
NO - Norway |
Download update 15.5 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 NO package |
|
NZ - New Zealand |
Download update 15.5 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 NZ package |
|
RU - Russia |
Download update 15.5 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 RU package |
|
SE - Sweden |
Download update 15.5 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 SE package |
|
UK - United Kingdom |
Download update 15.5 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 UK package |
|
All other countries |
Download update 15.5 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 W1 package |
How to install a Microsoft Dynamics 365 Business Central 2019 Release Wave 2 update
See How to install a Microsoft Dynamics 365 Business Central 2019 Release Wave 2 update.
Prerequisites
You must have Microsoft Dynamics 365 Business Central 2019 Release Wave 2 installed to apply this hotfix.
More information
See more information about software update terminology and Microsoft Dynamics 365 Business Central 2019 Release Wave 2.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
