When you upgrade on-premises deployments to this update, you and your customers must use a new license that covers more scenarios than the one for the original release in October 2018.
Why this new license?
In cumulative update 1 (CU1), we enabled new licensing scenarios so that Business Central is optimized for licenses that have named users. This was not fully supported in the RTM version that was made available on October 1, 2018. Therefore, CU1 requires a new license. You can pull new licenses when you upgrade customers to CU1.
The new licenses are required for CU1 and later versions of Business Central. They are not backwards compatible with earlier versions of Business Central.
What has changed?
In CU1, Business Central supports the product line IDs 49, 74, 75, and 76 for named users. For more information, see Microsoft Dynamics 365 Business Central Pricing and Licensing.
This cumulative update includes all hotfixes and regulatory features that have been released for Microsoft Dynamics 365 Business Central, including hotfixes and regulatory features that were released in previous cumulative updates.
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, see released cumulative updates for Microsoft Dynamics 365 Business Central. Cumulative updates are intended for new and existing customers who are running Microsoft Dynamics Released Cumulative Updates for Microsoft Dynamics 365 Business Central.
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
|
|
349587
|
The Pending status will not be documented.
|
|
346825
|
The Show as Chart action displays masked fields in plain text.
|
|
348819
|
Web client sessions are in a suspended state when the server is under a heavy load.
|
Application hotfixes
|
ID
|
Title
|
Functional Area
|
Changed Objects
|
|
343159
|
The Suggest Vendor Payments batch job does not increment number series values correctly.
|
Cash Management
|
REP 393 REP 394
|
|
349127
|
When you use the Create Payment function, the payment journal line is created with an incorrect document type.
|
Cash Management
|
PAG 1190
|
|
343788
|
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
|
|
344402
|
The top 10 list is not sorted as expected when the Balance (LCY) field is used for the Show parameter.
|
Finance
|
REP 111
|
|
344606
|
Allocated costs are assigned to a blocked cost center.
|
Finance
|
REP 1131
|
|
345322
|
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
|
|
345489
|
The Currency Code field can be blank when you use the Rapid Start function to import Currency codes.
|
Finance
|
TAB 4
|
|
346505
|
The caption and tooltip of the Allow G/L Acc. Deletion Before field in the General Ledger Setup page do not provide enough information.
|
Finance
|
PAG 118 TAB 98
|
|
349599
|
The Original Pmt. Disc. Possible and the Remaining Pmt. Disc. Possible amounts are incorrect in vendor ledger entries.
|
Finance
|
COD 12
|
|
348571
|
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
|
|
345667
|
The filter for the Company Name field on the Contacts list page does not display the correct result.
|
Marketing
|
TAB 5050
|
|
347310
|
The Sales Cycle Description field is not displayed when you update an opportunity.
|
Marketing
|
PAG 5129
|
|
343173
|
The posting number is used when the check total error is displayed.
|
Purchase
|
COD 74 COD 12104
|
|
347080
|
The Ship-to field on purchase quotes contains the customer address instead of the custom address.
|
Purchase
|
PAG 49
|
|
342790
|
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
|
|
342965
|
The company email address is not printed correctly in the Customer Receipt Payment report.
|
Sales
|
REP 211
|
|
348236
|
The tooltip for the Freight G/L Acc. No. field is not specific.
|
Sales
|
PAG 459 TAB 311
|
|
344611
|
Changing the values in the Lot and Serial No. fields in an inventory pick does not update the item ledger entry and tracking specification when posted.
|
Warehouse
|
COD 7324
|
Local application hotfixes
AT - Austria
|
ID
|
Title
|
Functional Area
|
Changed Objects
|
|
343186
|
An error message displays when you run the VAT Statement report in the Austrian version.
|
Finance
|
REP 11110
|
BE - Belgium
|
ID
|
Title
|
Functional Area
|
Changed Objects
|
|
343110
|
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
|
|
349330
|
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
|
|
344744
|
The Sales Page report does not consider the quote variant in the total amount in the Swiss version.
|
Sales
|
COD 57 COD 11503
|
CZ - Czech
|
ID
|
Title
|
Functional Area
|
Changed Objects
|
|
349532
|
Change FA Subclass code on the Fixed Asset card in fixed assets with more depreciation books in the Czech version.
|
Fixed Assets
|
TAB 5612
|
|
346235
|
"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
|
TAB 36 TAB 38 TAB 83 TAB 210 TAB 5740 REP 202 Sales Document - Test REP 402 REP 502 COD 80 COD 90 COD 5704 COD 5705
|
|
349616
|
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
|
ES - Spain
|
ID
|
Title
|
Functional Area
|
Changed Objects
|
|
347884
|
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
|
|
344739
|
Service Level <SvcLvl> and Service Level Code <Cd> are missing in the SEPA vendor payment file in the French version.
|
Finance
|
XML 1000
|
|
344471
|
"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
|
|
348156
|
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
|
|
347070
|
Withholding tax is not updated after you post the payment because the withholding tax is zero in the Italian version.
|
Finance
|
PAG 12111
|
|
347633
|
The Reason field is not available in the Vendor Bill Withholding Tax table in the Italian version.
|
Purchase
|
PAG 12198 TAB 12185
|
MX - Mexico
|
ID
|
Title
|
Functional Area
|
Changed Objects
|
|
342714
|
"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 has more than 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
|
|
342714
|
"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 has more than 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
|
|
344884
|
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
|
CreateIntrastatDeclDisk.Report
|
|
344651
|
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
|
NO - Norway
|
ID
|
Title
|
Functional Area
|
Changed Objects
|
|
348391
|
Not all G/L accounts export to the SAF-T file in the Norwegian version.
|
Finance
|
COD 10672 COD 10673 COD 10674
|
|
350283
|
The tax information in the SAF-T file is missing for purchase documents in the Norwegian version.
|
Finance
|
COD 10672 COD 10673 COD 10674
|
|
349471
|
Incorrect or missing data in exports to the SAF-T file in the Norwegian version.
|
Finance
|
COD 10672 COD 10673 COD 10674
|
Local regulatory features
BE - Belgium
|
ID
|
Title
|
Functional Area
|
Changed Objects
|
|
349375
|
The PEPPOL implementation is fixed according to partner feedback in the Belgian version.
|
Financial Management
|
COD 1605 COD 1620 COD 2 COD 452 COD 5980 COD 80 PAG 1 PAG 21 TAB 18 TAB 79 COD 1610 COD 1611 COD 1612 COD 1613 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
|
|
345382
|
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
|
|
349375
|
The PEPPOL implementation is fixed according to partner feedback in the Norwegian version.
|
Financial Management
|
COD 1605 COD 1620 COD 2 COD 452 COD 5980 COD 80 PAG 1 PAG 21 TAB 18 TAB 79 COD 1610 COD 1611 COD 1612 COD 1613 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
|
|
349647
|
Make headers update for the Tax Digital FP in the British version.
|
Financial Management
|
N/A
|