This article applies to Microsoft Dynamics 365 Business Central Spring 2019 Update (on-premises deployments) for all countries and all language locales.
An information disclosure vulnerability exists if Microsoft Dynamics Business Central/NAV on-premises does not correctly hide the value of a masked field when it displays the records as a chart page. To learn more about the vulnerability, go to CVE-2020-1018.
This update also addresses a vulnerability that is related to the NAVRecordState state. To learn more about the vulnerability, go to CVE-2020-1022.
Overview
This cumulative update replaces previously released cumulative updates. You should always install the latest cumulative 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 cumulative update. (This applies only to customer licenses.)
For a list of cumulative updates that were released for Microsoft Dynamics 365 Business Central Spring 2019, see released cumulative updates for Microsoft Dynamics 365 Business Central Spring 2019. Cumulative updates are intended for new and existing customers who are running Microsoft Dynamics Released Cumulative Updates for Microsoft Dynamics 365 Business Central Spring 2019.
Note
When you upgrade to Business Central 2019 release wave 2 (version 15), refer to Dynamics 365 Business Central Upgrade Compatibility Matrix to see which Business Central 15 versions are compatible with this cumulative update.
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 cumulative update
The following problems are resolved in this cumulative update.
Platform hotfixes
|
ID |
Title |
|
342802 |
Activity cues are not displayed correctly if they span more than one line in the web client. |
|
343626 |
An issue with the vendor item number in the FactBox. |
|
341121 |
NAV Service Tier stops responding. |
|
349588 |
The Pending status will not be documented. |
|
346926 |
The Show as Chart action displays masked fields in plain text. |
|
347321 |
"Exception of type 'Microsoft.Dynamics.Nav.Types.Exceptions.NavNotSupportedException' was thrown" error message displays when you use the BigInteger Data Type with the Customer No. field. |
|
346699 |
"Filter is not valid - Did not expect " error message displays when you try to filter on Payment Terms Code 1M(8D). |
|
345763 |
When you use the Select Item actions in the sales order, the focus is moved in the line above right after selecting the item. |
|
347120 |
Extension locks up the browser while it works fine in the RTC client. |
Application hotfixes
|
ID |
Title |
Functional Area |
Changed Objects |
|
345066 |
The menu in the workflow is not displayed correctly in the departments. |
Administration |
MEN 1010 |
|
343160 |
The Suggest Vendor Payments batch job does not increment number series values correctly. |
Cash Management |
REP 393 REP 394 |
|
349501 |
When you use the Create Payment function, the payment journal line is created with an incorrect document type. |
Cash Management |
PAG 1190 |
|
342231 |
The Payment Terms code is blank when you use the Copy Document function. |
Finance |
COD 6620 |
|
343789 |
When running the Cal. and Post VAT Settlement report, the Gen. Posting Type field is not set to Settlement for general ledger entries for reverse charge VAT. |
Finance |
REP 20 |
|
344011 |
Dimensions are not displayed correctly on archived sales orders. |
Finance |
PAG 5160 PAG 5163 PAG 5165 PAG 5168 PAG 6628 PAG 6645 PAG 6621 PAG 6624 |
|
344475 |
The top 10 list is not sorted as expected when the Balance (LCY) field is used for the Show parameter. |
Finance |
REP 111 |
|
344607 |
Allocated costs are assigned to a blocked cost center. |
Finance |
REP 1131 |
|
345323 |
You can post unbalanced G/L entries by using a reversing recurring journal although the Force Doc. Balance check box is chosen. |
Finance |
COD 13 |
|
346283 |
The incorrect table has a relation in the Statement No. field in the Posted Payment Recon. Line table. |
Finance |
TAB 1296 |
|
346506 |
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 |
PAG 118 TAB 98 |
|
346835 |
The Document Type field is blank on purchase journals. |
Finance |
PAG 254 |
|
345490 |
The Currency Code field can be blank when you use the Rapid Start function to import Currency codes. |
Finance |
TAB 4 |
|
349600 |
The Original Pmt. Disc. Possible and the Remaining Pmt. Disc. Possible amounts are incorrect in vendor ledger entries. |
Finance |
COD 12 |
|
341347 |
A performance issue occurs when you use the Item Category Code field on the Item card. |
Inventory |
COD 5722 PAG 5730 PAG 5733 TAB 5722 |
|
344524 |
Updating an item category does not also update item attributes. |
Inventory |
COD 7500 |
|
348609 |
The filter is missing at the item by location subpage level in the Windows client. |
Inventory |
PAG 491 |
|
348572 |
You cannot sort on the Start Date and End Date fields in production orders after upgrading to cumulative update 24. |
Manufacturing |
PAG 5406 PAG 9323 PAG 9324 PAG 9325 PAG 9326 PAG 9327 PAG 99000759 PAG 99000813 PAG 99000814 PAG 99000815 PAG 99000817 PAG 99000820 PAG 99000829 PAG 99000830 PAG 99000831 PAG 99000832 PAG 99000867 PAG 99000868 PAG 99000912 PAG 99000913 |
|
345668 |
The filter for the Company Name field on the Contacts list page does not display the correct result. |
Marketing |
TAB 5050 |
|
347311 |
The Sales Cycle Description field is not displayed when you update an opportunity. |
Marketing |
PAG 5129 |
|
343547 |
When the Reorder Policy field is set to Maximum Qty. Value and a Lead Time Calculation field is added, the requisition worksheet is suggesting a value that greater than the maximum quantity. |
Purchase |
COD 99000854 |
|
343899 |
The Ship-to field on purchase quotes contains the customer address instead of the custom address. |
Purchase |
PAG 49 |
|
342791 |
In a prepayment scenario, sales line comments are not displayed for the prepayment invoice if the Compress Prepayment field is set to true. |
Sales |
COD 442 COD 444 TAB 43 TAB 44 |
|
343183 |
The company email address is not printed correctly in the Customer Receipt Payment report. |
Sales |
REP 211 |
|
343785 |
The RDLC layout for the Sales Invoice report always prints two pages. |
Sales |
REP 1306 |
|
346197 |
You cannot search for the Delete Invoiced Sales Orders report in the online version of Business Central. |
Sales |
MEN 1010 |
|
348237 |
The tooltip for the Freight G/L Acc. No. field is not specific. |
Sales |
PAG 459 TAB 311 |
|
344613 |
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 |
COD 7324 COD 80 |
Local application hotfixes
APAC
|
ID |
Title |
Functional Area |
Changed Objects |
|
350042 |
The printed posted purchase receipt is truncated, and a blank page is printed in the APAC version. |
Purchase |
REP 408 |
AT – Austria
|
ID |
Title |
Functional Area |
Changed Objects |
|
343187 |
Error message is displayed when you run the VAT Statement report in the Austrian version. |
Finance |
REP 11110 |
BE - Belgium
|
ID |
Title |
Functional Area |
Changed Objects |
|
343207 |
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 vendor ledger entry in the Belgian version. |
Finance |
REP 2000004 |
|
349331 |
The dimension filter for the Suggest Vendor Payments action in the EB Payment Journal does not work in the Belgian version. |
Purchase |
REP 2000019 |
CH - Switzerland
|
ID |
Title |
Functional Area |
Changed Objects |
|
344745 |
The Sales Page report does not consider the quote variant in the total amount in the Swiss version. |
Sales |
COD 11503 |
CZ - Czech
|
ID |
Title |
Functional Area |
Changed Objects |
|
349572 |
The message that displays when you create a new payment reconciliation journal is corrected in the Czech version. |
Cash Management |
TAB 273 |
|
347938 |
Change FA Subclass code on the Fixed Asset card in fixed assets with more depreciation books in the Czech version. |
Fixed Assets |
FADepreciationBook.Table |
|
349614 |
Call of stock in the VIES report in the Czech version. |
VAT/Sales Tax/Intrastat |
PAG 31067 REP 31060 REP 31068 TAB 31067 XML 31060 |
DK - Denmark
|
ID |
Title |
Functional Area |
Extensions |
|
345034 |
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 |
OIOUBL |
ES - Spain
|
ID |
Title |
Functional Area |
Changed Objects |
|
347885 |
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 |
COD 12 COD 13 |
FR - France
|
ID |
Title |
Functional Area |
Changed Objects |
|
344740 |
Service Level <SvcLvl> and Service Level Code <Cd> are missing in the SEPA vendor payment file in the French version. |
Finance |
XML 1000 |
|
344472 |
"The value can't be evaluated into type Integer" error message displays when you run the Export G/L Entries - Tax Audit report and the Registration No. field is blank in the company information in the French version. |
Finance |
REP 10885 |
IT - Italy
|
ID |
Title |
Functional Area |
Changed Objects |
|
347071 |
Withholding tax is not updated after you post the payment because the withholding tax is zero in the Italian version. |
Finance |
PAG 12111 |
|
348157 |
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 |
REP 20 |
|
343174 |
The posting number is used when the check total error is displayed in the Italian version. |
Purchase |
COD 12104 |
|
347634 |
The Reason field is not available in the Vendor Bill Withholding Tax table in the Italian version. |
Purchase |
PAG 12198 TAB 12185 |
|
345618 |
Withholding tax is not calculated correctly in the vendor bill if you manually change the WHT amount in the Italian version. |
Purchase |
TAB 12182 |
|
345273 |
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 |
TAB 5900 |
|
345455 |
The Fiscal VAT Register reports the VAT Product Post. Group code description instead of the VAT identifier code description in the Italian version. |
VAT/Sales Tax/Intrastat |
VATRegisterPrint.Report |
MX - Mexico
|
ID |
Title |
Functional Area |
Changed Objects |
|
343369 |
"Error: The length of the string is ## but it must be less than or equal to 30. " error message displays in the sales order statistics when a Tax Area code description is entered for over 30 characters in the Mexican version. |
Sales |
PAG 10038 PAG 10039 PAG 10041 PAG 10042 PAG 10043 PAG 10044 PAG 10045 PAG 10046 PAG 10052 PAG 10053 PAG 10056 PAG 10057 |
NA - North America
|
ID |
Title |
Functional Area |
Changed Objects |
|
343369 |
"Error: The length of the string is ## but it must be less than or equal to 30. " error message displays in the sales order statistics when a Tax Area code description is entered for over 30 characters in the North American version. |
Sales |
PAG 10038 PAG 10039 PAG 10041 PAG 10042 PAG 10043 PAG 10044 PAG 10045 PAG 10046 PAG 10052 PAG 10053 PAG 10056 PAG 10057 |
NL - Netherlands
|
ID |
Title |
Functional Area |
Changed Objects |
|
344653 |
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 |
REP 11412 TAB 11404 |
|
345159 |
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 |
REP 11413 |
NO - Norway
|
ID |
Title |
Functional Area |
Extensions |
|
348392 |
Not all G/L accounts export to the SAF-T file in the Norwegian version. |
Finance |
NorwegianSAFT |
|
349472 |
Incorrect or missing data in exports to the SAF-T file in the Norwegian version. |
Finance |
NorwegianSAFT |
|
350284 |
The tax information in the SAF-T file is missing for purchase documents in the Norwegian version. |
Finance |
NorwegianSAFT |
Local regulatory features
BE - Belgium
|
ID |
Title |
Functional Area |
Changed Objects |
|
349378 |
The PEPPOL implementation is fixed according to partner feedback in the Belgian version. |
Financial Management |
COD 1605 COD 1610 COD 1611 COD 1612 COD 1613 COD 1620 COD 2 COD 452 COD 5980 COD 80 PAG 1 PAG 21 TAB 18 TAB 79 XML 1610 XML 1611 PAG 132 PAG 134 PAG 143 PAG 144 PAG 459 PAG 5971 PAG 5972 PAG 5977 PAG 5978 |
IT - Italy
|
ID |
Title |
Functional Area |
Changed Objects |
|
345392 |
A new value of Non-Taxable Income Type is added to the withholding tax in the Italian version. |
Financial Management |
PAG 12112 TAB 12116 |
NO - Norway
|
ID |
Title |
Functional Area |
Changed Objects |
|
349378 |
The PEPPOL implementation is fixed according to partner feedback in the Norwegian version. |
Financial Management |
COD 1605 COD 1610 COD 1611 COD 1612 COD 1613 COD 1620 COD 2 COD 452 COD 5980 COD 80 PAG 1 PAG 21 TAB 18 TAB 79 XML 1610 XML 1611 PAG 132 PAG 134 PAG 143 PAG 144 PAG 459 PAG 5971 PAG 5972 PAG 5977 PAG 5978 |
UK - United Kingdom
|
ID |
Title |
Functional Area |
Changed Objects |
|
349644 |
Make headers update for the Tax Digital FP in the British version. |
Financial Management |
N/A |
Resolution
How to obtain the Microsoft Dynamics 365 Business Central Spring 2019 files
This update is available for manual download and installation from the Microsoft Download Center.
Cumulative Update 11 for Microsoft Dynamics 365 Business Central Spring 2019 Update on-premises
Which hotfix package to download
This cumulative 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 Spring 2019 database:
|
Country |
Hotfix package |
|
AT - Austria |
Download the CU 11 Dynamics 365 Business Central Spring 2019 AT package |
|
AU - Australia |
Download the CU 11 Dynamics 365 Business Central Spring 2019 AU package |
|
BE - Belgium |
Download the CU 11 Dynamics 365 Business Central Spring 2019 BE package |
|
CH - Switzerland |
Download the CU 11 Dynamics 365 Business Central Spring 2019 CH package |
|
CZ- Czech |
Download the CU 11 Dynamics 365 Business Central Spring 2019 CZ package |
|
DE - Germany |
Download the CU 11 Dynamics 365 Business Central Spring 2019 DE package |
|
DK - Denmark |
Download the CU 11 Dynamics 365 Business Central Spring 2019 DK package |
|
ES - Spain |
Download the CU 11 Dynamics 365 Business Central Spring 2019 ES package |
|
FI - Finland |
Download the CU 11 Dynamics 365 Business Central Spring 2019 FI package |
|
FR - France |
Download the CU 11 Dynamics 365 Business Central Spring 2019 FR package |
|
IS - Iceland |
Download the CU 11 Dynamics 365 Business Central Spring 2019 IS package |
|
IT - Italy |
Download the CU 11 Dynamics 365 Business Central Spring 2019 IT package |
|
NA - North America |
Download the CU 11 Dynamics 365 Business Central Spring 2019 NA package |
|
NL - Netherlands |
Download the CU 11 Dynamics 365 Business Central Spring 2019 NL package |
|
NO - Norway |
Download the CU 11 Dynamics 365 Business Central Spring 2019 NO package |
|
NZ - New Zealand |
Download the CU 11 Dynamics 365 Business Central Spring 2019 NZ package |
|
RU - Russia |
Download the CU 11 Dynamics 365 Business Central Spring 2019 RU package |
|
SE - Sweden |
Download the CU 11 Dynamics 365 Business Central Spring 2019 SE package |
|
UK - United Kingdom |
Download the CU 11 Dynamics 365 Business Central Spring 2019 UK package |
|
All other countries |
Download the CU 11 Dynamics 365 Business Central Spring 2019 W1 package |
How to install a Microsoft Dynamics 365 Business Central Spring 2019 cumulative update
See How to install a Microsoft Dynamics 365 Business Central Spring 2019 cumulative update.
Prerequisites
You must have Microsoft Dynamics 365 Business Central Spring 2019 installed to apply this hotfix.
More information
See more information about software update terminology and Microsoft Dynamics 365 Business Central Spring 2019.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
