This article applies to Microsoft Dynamics NAV 2017 for all countries and all language locales.
Overview
This cumulative update includes all hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2017, 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 implementing this hotfix to gain access to new objects included in this or a previous cumulative update (this only applies to customer licenses).For a list of cumulative updates released for Microsoft Dynamics NAV 2017, see released cumulative updates for Microsoft Dynamics NAV 2017. Cumulative updates are intended for new and existing customers who are running Microsoft Dynamics NAV 2017.ImportantWe 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 being installed. A hotfix or update may cause interoperability issues with customizations and third-party products that work with your Microsoft Dynamics NAV solution.
Problems that are resolved in this cumulative update
The following problems are resolved in this cumulative update:
Application hotfixes
|
ID |
Title |
Functional Area |
Changed Objects |
|
364190 |
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 |
|
364421 |
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 |
|
368248 |
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 |
|
364718 |
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 |
|
369069 |
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 |
|
364707 |
"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 |
Local application hotfixes
CZ - Czech
|
ID |
Title |
Functional Area |
Changed Objects |
|
368254 |
Incorrect value in the recapitulative declaration export of VAT statement in the Czech version. |
Finance |
XML 11762 |
DACH
|
ID |
Title |
Functional Area |
Changed Objects |
|
363812 |
The index.xml file created from the Business Data Export cannot be validated if German special characters are included in Export Table Name, Export File Name and/or Export Field Name in the DACH version. |
Finance |
COD 11000 |
IT - Italy
|
ID |
Title |
Functional Area |
Changed Objects |
|
365065 |
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 |
|
364604 |
An error message about PrezzoTotale calculation displays when the E-invoicing is not validated in the Italian version. |
Sales |
COD 12179 |
Local regulatory features
NL - Netherlands
|
ID |
Title |
Functional Area |
Changed Objects |
|
367119 |
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 |
|
361296 |
Improve the SAF-T performance in the Norwegian version. |
Financial Management |
COD 10673 COD 10675 COD 10678 PAG 10687 PAG 10691 TAB 10629 TAB 10632 |
Resolution
How to obtain the Microsoft Dynamics NAV update files
This update is available for manual download and installation from the Microsoft Download Center.
Cumulative update CU 46 for Microsoft Dynamics NAV 2017
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 NAV 2017 database:
|
Country |
Hotfix package |
|
AT - Austria |
Download the CU 46 NAV 2017 AT package |
|
AU - Australia |
Download the CU 46 NAV 2017 AU package |
|
BE - Belgium |
Download the CU 46 NAV 2017 BE package |
|
CH - Switzerland |
Download the CU 46 NAV 2017 CH package |
|
CZ- Czech |
Download the CU 46 NAV 2017 CZ package |
|
DE - Germany |
Download the CU 46 NAV 2017 DE package |
|
DK - Denmark |
Download the CU 46 NAV 2017 DK package |
|
ES - Spain |
Download the CU 46 NAV 2017 ES package |
|
FI - Finland |
Download the CU 46 NAV 2017 FI package |
|
FR - France |
Download the CU 46 NAV 2017 FR package |
|
IS - Iceland |
Download the CU 46 NAV 2017 IS package |
|
IT - Italy |
Download the CU 46 NAV 2017 IT package |
|
NA - North America |
Download the CU 46 NAV 2017 NA package |
|
NL - Netherlands |
Download the CU 46 NAV 2017 NL package |
|
NO - Norway |
Download the CU 46 NAV 2017 NO package |
|
NZ - New Zealand |
Download the CU 46 NAV 2017 NZ package |
|
RU - Russia |
Download the CU 46 NAV 2017 RU package |
|
SE - Sweden |
Download the CU 46 NAV 2017 SE package |
|
UK - United Kingdom |
Download the CU 46 NAV 2017 UK package |
|
All other countries |
Download the CU 46 NAV 2017 W1 package |
How to install a Microsoft Dynamics NAV 2017 cumulative update
See How to install a Microsoft Dynamics NAV 2017 cumulative update.
Prerequisites
You must have Microsoft Dynamics NAV 2017 installed to apply this hotfix.
More information
See more information about software update terminology and Microsoft Dynamics NAV 2017.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
