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:
Platform hotfixes
|
ID |
Title |
|
310286 |
A warning is not displayed in the development environment if you do not run as an administrator when you convert a database. |
|
346819 |
Canceling customer creations and adding customer numbers incorrectly update the shipping and billing tab with custom addresses. |
|
358481 |
An IndexOutOfRangeException error is sometimes raised. |
|
361729 |
Long event signatures are not displaying correctly in C/SIDE and cannot be copied and pasted correctly. |
Application hotfixes
|
ID |
Title |
Functional Area |
Changed Objects |
|
362192 |
"Manual Invoice Discount Amount is not allowed" error message displays when you try to change the Allow invoice Disc. flag on a sales order line. |
Finance |
COD 56 COD 66 TAB 37 TAB 39 |
|
360059 |
A receipt for a purchase order can be posted for a fixed asset which is already disposed. |
Fixed Assets |
COD 5606 COD 90 |
|
361064 |
The Prices Including VAT field for G/L accounts are not converted by the VAT Rate Change tool. |
VAT/Sales Tax/Intrastat |
COD 550 PAG 550 TAB 37 TAB 39 TAB 550 TAB 5902 |
|
361081 |
Item templates are not updated when you run the VAT Rate Change tool. |
VAT/Sales Tax/Intrastat |
COD 550 PAG 550 TAB 37 TAB 39 TAB 550 TAB 5902 |
Local application hotfixes
CH - Switzerland
|
ID |
Title |
Functional Area |
Changed Objects |
|
360271 |
Error message displays when you try to post a purchase order that contains an item with No Stockkeeping flag in the Swiss version. |
Inventory |
TAB 27 |
|
359579 |
Error message displays when you try to post a purchase order that contains an item with No Stockkeeping flag in the Swiss version. |
Inventory |
TAB 27 |
DE - Germany
|
ID |
Title |
Functional Area |
Changed Objects |
|
359430 |
The Registration No. field for German State of Hessen should be 11 in the German version. |
Finance |
TAB 11011 |
ES - Spain
|
ID |
Title |
Functional Area |
Changed Objects |
|
360646 |
The export of the module needs to be changed in the Spanish version. |
Finance |
REP 10710 |
NO - Norway
|
ID |
Title |
Functional Area |
Changed Objects |
|
360656 |
The last modified date is not updated correctly in the SAF-T file in the Norwegian version. |
Finance |
COD 10673 |
|
359776 |
Using multiple VAT posting groups in an invoice exports incorrect values in SAF-T in the Norwegian version. |
Finance |
COD 10673 |
|
361598 |
If you do not select all Dimensions code to export to the SAF-T file, the source file contains the selected dimensions, but all dimensions are exported in the general ledger in the Norwegian version. |
Finance |
COD 10673 |
Local regulatory features
|
ID |
Title |
Functional Area |
Changed Objects |
|
347527 |
Add processing order to Data Exchange Definition Mapping. |
Financial Management |
COD 1201 PAG 1217 PAG 1218 TAB 1225 |
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 44 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 44 NAV 2017 AT package |
|
AU - Australia |
Download the CU 44 NAV 2017 AU package |
|
BE - Belgium |
Download the CU 44 NAV 2017 BE package |
|
CH - Switzerland |
Download the CU 44 NAV 2017 CH package |
|
CZ- Czech |
Download the CU 44 NAV 2017 CZ package |
|
DE - Germany |
Download the CU 44 NAV 2017 DE package |
|
DK - Denmark |
Download the CU 44 NAV 2017 DK package |
|
ES - Spain |
Download the CU 44 NAV 2017 ES package |
|
FI - Finland |
Download the CU 44 NAV 2017 FI package |
|
FR - France |
Download the CU 44 NAV 2017 FR package |
|
IS - Iceland |
Download the CU 44 NAV 2017 IS package |
|
IT - Italy |
Download the CU 44 NAV 2017 IT package |
|
NA - North America |
Download the CU 44 NAV 2017 NA package |
|
NL - Netherlands |
Download the CU 44 NAV 2017 NL package |
|
NO - Norway |
Download the CU 44 NAV 2017 NO package |
|
NZ - New Zealand |
Download the CU 44 NAV 2017 NZ package |
|
RU - Russia |
Download the CU 44 NAV 2017 RU package |
|
SE - Sweden |
Download the CU 44 NAV 2017 SE package |
|
UK - United Kingdom |
Download the CU 44 NAV 2017 UK package |
|
All other countries |
Download the CU 44 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.
