This article applies to Microsoft Dynamics 365 Business Central Spring 2019 Update (on-premises deployments) for all countries and all language locales.
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 |
|---|---|
| 364588 | A SQL error displays in Sync-NAVTenant -Mode Sync when you synchronize with a TableSyncSetup Upgrade codeunit that runs with TableSynchSetup.Mode::Force. |
Application hotfixes
| ID | Title | Functional Area | Changed Objects |
|---|---|---|---|
| 366223 | "The Credit Transfer Entry already exists. Identification fields and values: Credit Transfer Register No.='X',Entry No.='Y'" error message displays when you export the electronical payment file. | Cash Management | COD 16 |
| 364192 | When you post a new prepayment invoice after using the VAT Rate Change function, an incorrect VAT amount is registered for the prepayment invoice. | Finance | COD 550 |
| 364423 | After a VAT rate change, a VAT entry from a sales order with prepayments displays the new VAT Product Posting Group table, but the VAT amount is incorrect. | Finance | TAB 37 TAB 39 |
| 365813 | Unreal gain and unreal loss are not posted correctly. | Finance | REP 595 |
| 366228 | The Handled IC Inbox Transactions page and IC Inbox Transactions page have an incorrect PromotedActionCategoriesML Outbox Transactions property. | Finance | PAG 615 PAG 617 |
| 366669 | "The File C:\XXXX*xml does not exist. " error message displays if you try to import a file on the IC Inbox Transactions page. | Finance | COD 435 |
| 366886 | In vendor ledger entries, it is possible to change the value in the Exported to Payment File field from false to true manually. | Finance | PAG 25 PAG 29 |
| 367122 | The customer name should not be updated or replaced when there is no name associated with the VAT Registration No. field. | Finance | COD 249 |
| 368250 | After the VAT Rate Change, a VAT entry from a prepayment credit memo displays the new VAT Product Posting Group table, but the correct VAT amount that is calculated based on the old VAT Product Posting Group table. | Finance | TAB 37 TAB 39 |
| 364720 | When you deal with a service order and transfer by using the order planning and the Reserve option, the Reservation status is set to tracking instead of reservation. | Inventory | COD 926 COD 99000813 COD 99000842 |
| 369205 | The Outbound Transfer is not cost adjusted while the Inbound Transfer, which is split into several entries due to multiple cost relations, is a correctly cost adjusted FIFO item. | Inventory | COD 5895 |
| 365036 | Bin code is not transferred to the sales invoice created from the job planning line. | Jobs | COD 1002 |
| 366064 | Lines with the Type = Text setting in Jobs Planning lines already invoiced can be changed to other type and invoiced again. | Jobs | PAG 1007 |
| 364361 | The Allocated Time field in the Prod. Order Capacity report does need to be consistent with the Needed Time field after you post the negative Run Time field. | Manufacturing | COD 22 |
| 364709 | "Quantity Received must be equal to '0'" error message displays after you post a purchase order where the Blanket Order Line No. field is blank even if the Blanket Order No. field is filled. | Purchase | COD 90 |
| 366706 | The quantity of the item in the purchase quotes cannot be changed if the item is selected from description lookup using mouse. | Purchase | PAG 97 |
| 364554 | The Recipient Bank Account field should be visible and editable on the Customer Ledger Entry page. | Sales | COD 103 COD 113 PAG 25 PAG 29 |
| 365012 | Using Available to Promise (ATP) leads to incorrect earliest shipment date when you deal with sales orders and production orders. | Sales | COD 5790 |
| 366377 | The sales quote is not archived if you convert it into a sales invoice and you set the Archive Quote field to True in the Sales & Receivables Setup. | Sales | COD 1305 |
| 366876 | The Qty. to Receive value entered on a line in a purchase order is not saved in the Web client when you tab out of the field. | Sales | TAB 37 TAB 39 |
| 362536 | When you post a sales document, the sales line record is temporarily stuck. | Sales | PAG 42 |
Local application hotfixes
CZ - Czech
| ID | Title | Functional Area | Changed Objects |
|---|---|---|---|
| 368630 | Incorrect value in the recapitulative declaration export of VAT statement in the Czech version. | Finance | XML 11762 |
DACH
| ID | Title | Functional Area | Changed Objects |
|---|---|---|---|
| 367579 | The first line is not printed in the Finance Charge Memo report in the DACH version. | Finance | REP 118 |
| 367588 | When we have VAT in the Finance Charge Memo report, the system displays several decimal places in the Finance Charge Memo report in the DACH version. | Finance | REP 118 |
ES - Spain
| ID | Title | Functional Area | Changed Objects |
|---|---|---|---|
| 368889 | It is not possible to change the payment method in customer and vender ledger entries even if the document is not linked to the Cartera module in the Spanish version. | Sales | TAB 25 TAB 21 |
IT - Italy
| ID | Title | Functional Area | Changed Objects |
|---|---|---|---|
| 366707 | If you set the VAT period as Quarter, the previous Period Input VAT value is not included in the Periodic VAT Payment Communication report in the Italian version. | Finance | COD 12151 |
| 366839 | On posting a payment for two open vendor ledger entries created from one invoice, incorrect VAT entries are created in the Italian version. | Finance | COD 12 |
| 365067 | If a sales invoice is issued for a customer classified as an individual person, the XML file of the invoice is not correct in the Italian version. | Finance | COD 12179 |
| 364606 | An error message about PrezzoTotale calculation displays when the E-invoicing is not validated in the Italian version. | Sales | COD 12179 |
NA - North American
| ID | Title | Functional Area | Changed Objects |
|---|---|---|---|
| 362536 | When you post a sales document, the sales line record is temporarily stuck in the North American version. | Sales | PAG 42 |
UK - United Kingdom
| ID | Title | Functional Area | Changed Objects |
|---|---|---|---|
| 365265 | The <ContactName> node is exported without data if you export the EC Sales List report in the XML file in the British version. | Finance | REP 130 |
Local regulatory features
NL - Netherlands
| ID | Title | Functional Area | Changed Objects |
|---|---|---|---|
| 367104 | It is possible to see the XML request of the ICP declaration before submission in the Dutch version. | Financial Management | PAG 11411 REP 11405 TAB 11409 |
NO - Norway
| ID | Title | Functional Area | Changed Objects |
|---|---|---|---|
| 361287 | Improve the SAF-T performance in the Norwegian version. | Financial Management | COD 1752 TAB 10629 PAG 10691 TAB 10685 |
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 CU 16 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 16 Dynamics 365 Business Central Spring 2019 AT package |
| AU - Australia | Download the CU 16 Dynamics 365 Business Central Spring 2019 AU package |
| BE - Belgium | Download the CU 16 Dynamics 365 Business Central Spring 2019 BE package |
| CH - Switzerland | Download the CU 16 Dynamics 365 Business Central Spring 2019 CH package |
| CZ- Czech | Download the CU 16 Dynamics 365 Business Central Spring 2019 CZ package |
| DE - Germany | Download the CU 16 Dynamics 365 Business Central Spring 2019 DE package |
| DK - Denmark | Download the CU 16 Dynamics 365 Business Central Spring 2019 DK package |
| ES - Spain | Download the CU 16 Dynamics 365 Business Central Spring 2019 ES package |
| FI - Finland | Download the CU 16 Dynamics 365 Business Central Spring 2019 FI package |
| FR - France | Download the CU 16 Dynamics 365 Business Central Spring 2019 FR package |
| IS - Iceland | Download the CU 16 Dynamics 365 Business Central Spring 2019 IS package |
| IT - Italy | Download the CU 16 Dynamics 365 Business Central Spring 2019 IT package |
| NA - North America | Download the CU 16 Dynamics 365 Business Central Spring 2019 NA package |
| NL - Netherlands | Download the CU 16 Dynamics 365 Business Central Spring 2019 NL package |
| NO - Norway | Download the CU 16 Dynamics 365 Business Central Spring 2019 NO package |
| NZ - New Zealand | Download the CU 16 Dynamics 365 Business Central Spring 2019 NZ package |
| RU - Russia | Download the CU 16 Dynamics 365 Business Central Spring 2019 RU package |
| SE - Sweden | Download the CU 16 Dynamics 365 Business Central Spring 2019 SE package |
| UK - United Kingdom | Download the CU 16 Dynamics 365 Business Central Spring 2019 UK package |
| All other countries | Download the CU 16 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.