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.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 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 |
|---|---|
|
271263 |
The Web client can sometimes silently fail to save data that is entered into a matrix field when you use Internet Explorer. |
|
272273 |
The Import-NavData cmdlet generates a huge database when you use SQL Server 2016 compared to an earlier release of SQL Server. |
|
274608 |
Strange behavior in sales lines with indentation when you use the Description field to find records such as items or G/L accounts. |
|
275110 |
Several SOAP Web service Readmultiple calls run in parallel can cause SQL Server to hang if the underlying table has a FlowField. |
|
277577 |
"The length of the string is 30, but it must be less than or equal to 20 characters" error message when you have filtered the Adjust Cost Item Entries batch job for several items by using the "|" as a separator. |
|
278057 |
The Windows client crashes when a subpage contains a control add-in. |
|
280576 |
"Message: (PrincipalOperationException): While trying to retrieve the authorization groups, an error (5) occurred" error message when task schedule does not work. |
Application hotfixes
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
275682 |
It is not able to refresh record after manual selection of CRM records. |
Administration |
PAG 5336 TAB 5332 |
|
275807 |
The Process Service Email Queue function ends in an error message. |
Administration |
COD 5917 |
|
275833 |
When a purchase order is approved, a second approval is required when you try to post the warehouse receipt. |
Administration |
COD 414 COD 415 COD 5760 COD 5763 |
|
277005 |
Attachments cannot be opened when you use Email logging in combination with Exchange Server 2016. |
Administration |
TAB 5065 |
|
277687 |
When you import vendors through RapidStart, a contact number is created for the vendor but no other fields such as the Name field. |
Administration |
COD 5056 COD 5057 COD 5058 TAB 18 TAB 23 TAB 270 |
|
274504 |
The Apply Automatically function does not work consistently. |
Cash Management |
PAG 1252 TAB 1252 |
|
276974 |
"0 orders out of a total of 1 have now been posted" error message when you post a service order through a Batch Post Service Orders batch job with the Replace Posting Date option to an allowed posting date. |
Finance |
COD 5980 |
|
277247 |
If you reorder the general journal lines, there are several scenarios where the test report gets a warning message. |
Finance |
REP 2 TAB 81 |
|
277260 |
Poor performance when you post a general journal after the upgrade. |
Finance |
COD 13 |
|
277569 |
The Payment Disc. Tolerance field is not considered on the Posting Preview page when the Posting Preview page is called from the Apply page. |
Finance |
COD 226 COD 227 |
|
277756 |
"The application was successfully posted" message is displayed incorrectly in an apply process with the Payment Disc. Tolerance option. |
Finance |
COD 226 COD 227 PAG 232 PAG 233 |
|
277850 |
The VAT Registration No. field is missing in VAT entries that are created at issuing reminders. |
Finance |
COD 393 |
|
278197 |
The Payment Discount field is 0 after you delete the document date and re-enter the document date on the Sales Order page. |
Finance |
TAB 36 |
|
278790 |
The External doc no. field is not filled in on the Cash receipt journal page when you select an Apply-to doc. number. |
Finance |
TAB 81 |
|
279067 |
The Job Cost FactBox on the Job Details page is running extremely slowly when the system has many job ledger entries and job planning lines. |
Jobs |
COD 1008 PAG 89 TAB 1003 TAB 167 TAB 169 |
|
277108 |
The Production BOM Version Code and Routing Version Code columns on the Prod. Order Line page are not based on the starting date-time on the Production Order header. |
Manufacturing |
REP 99001025 |
|
274511 |
The Send action that exists on the Purchase Order page and Purchase Order List page does not exist on the Purchase Quote and Purchase Quotes pages. |
Purchase |
PAG 49 PAG 9306 TAB 38 REP 404 |
|
277342 |
The Creditor No. field on the Vendor page does not accept values with characters. |
Purchase |
TAB 122 TAB 23 TAB 25 TAB 372 TAB 38 TAB 81 |
|
277841 |
The shipping method code in a purchase order comes with the pay-to vendor where it should be from the buy-from vendor. |
Purchase |
TAB 38 |
|
278343 |
The Purchase Return Shipment report does not print the ship-to address but the pay-to address. |
Purchase |
COD 130440 REP 6636 |
|
278667 |
When you change the Expected Receipt Date field on a purchase order line backwards a couple of days, the system immediately changes it to +3D ahead of the entered date. |
Purchase |
COD 7600 TAB 39 |
|
276102 |
Some characters are not displayed correctly in the Customer - Labels report. |
Sales |
REP 110 |
|
277196 |
"Another user has modified the record for this Sales Line after you retrieved it from the database" error message if you try to modify a sales order line with extended text. |
Sales |
COD 60 COD 70 |
|
277681 |
Duplicate DEU captions in table fields can cause an unexpected error when you release a sales order if you have a workflow enabled. |
Sales |
COD 1501 |
|
277746 |
The invoice discount is on a posted sales invoice incorrectly after partial invoicing of a sales order. |
Sales |
COD 80 |
|
278112 |
The Allow Document Deletion Before field in the Sales & Receivables Setup table can be blank by mistake. |
Sales |
COD 363 COD 364 |
|
278157 |
"An attempt was made to change an old version of a Customer record" error message when you change a contact name from a customer card. |
Sales |
TAB 18 TAB 23 |
|
278165 |
Item charge line with a negative quantity in credit memo creates value entry with negative sign in the Sales Amount (Actual) and Valued Quantity fields for item using item tracking code. |
Sales |
COD 80 |
|
279173 |
VAT clauses are not printed by using the Word layout for the Standard Sales – Invoice report. |
Sales |
REP 1306 |
|
280248 |
Item charge line with a negative quantity in credit memo creates value entry with negative sign in the Sales Amount (Actual) and Valued Quantity fields for item using item tracking code. |
Sales |
COD 80 |
|
279486 |
Final invoiced sales amount does not match the prepayment invoice when sales taxes are included in the North American version. |
Sales |
COD 398 COD 442 COD 80 TAB 37 |
|
277612 |
Put-Aways are being created for incorrect lot numbers when you create them from a posted warehouse receipt, after two posted warehouse receipt exist for a same item with 2 different lot numbers with inverse quantities that are already put away. |
Warehouse |
COD 6500 |
|
279022 |
"Qty. to Handle (Base) in Tracking Specification for Item No. X, Serial No.: , Lot No.: Y is currently A. It must be B" error message when you post a warehouse shipment with the Item Tracking option. |
Warehouse |
COD 7307 |
Local application hotfixes
BE - Belgium
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
277897 |
The Annual Listing report must disregard the Minimum Amount field in case of a negative sales amount in the Belgian version. |
Finance |
REP 11308 REP 11309 |
CH - Switzerland
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
277560 |
"A call to System.XML.XMLDocumetnLoad failed with this message: Unexpected end tag. Line" error message when you try to import a CAMT054 file including fees in the Swiss version. |
Cash Management |
COD 1240 |
CZ - Czech
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
279921 |
No check to change currency code on the Payment Reconciliation Journal page after applying in the Czech version. |
Cash Management |
TAB 274 |
|
279933 |
Optimizing performance for the Payment Order Management page in the Czech version. |
Cash Management |
COD 11709 PAG 29 PAG 25 |
|
280030 |
EET - extension information processing when an entry is sent for verification in the Czech version. |
Cash Management |
COD 31120 COD 31121 COD 31122 TAB 31123 TAB 31124 |
|
279912 |
"Closed must be equal to 'No' in VAT Period: Starting date=" error message when you post a value which will not generate VAT ledger entries in the Czech version. |
Finance |
COD 11 COD 12 |
|
279961 |
The ExtendedDatatype for the Proxy Password field in the Electronically Govern. Setup table has not value masked in the Czech version. |
Finance |
TAB 11761 |
|
280025 |
The posted sales credit memo is not among suggested lines for the VAT Control report in the Czech version. |
Finance |
COD 31100 |
|
279943 |
The default order address code is not transmitted to the purchase order in the Czech version. |
Purchase |
TAB 38 |
DE - Germany
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
280292 |
An error message related to the Last used options and filters feature when you print the Statement report two times in a non-English language in the German version. |
Sales |
COD 8800 |
|
280927 |
The captions on the request page of the VAT- VIES Declaration Disk report look odd in the German version. |
Finance |
REP 88 |
DK - Denmark
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
277724 |
"Payment Terms Code must have a value in Sales Header: Document Type=Credit Memo, No=XX" error if you try to post a corrective credit memo that is created from the posted sales invoice without payment terms code but with the EAN No. field informed in the Danish version. |
Sales |
COD 13602 |
ES - Spain
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
279796 |
If you use a SII Exemption Code E5 in the VAT Posting Setup/VAT Clause page, the Cuota deducible amount is reported with 0 but it needs to be reported with the actual VAT amount for EU purchase invoices in the Spanish version. |
Finance |
COD 10750 |
|
278070 |
If you post a sales credit memo with reverse charge VAT that corrects an invoice in SII, the ImporteTotal node is getting the total invoice amount incorrectly if both Invoice and credit memo documents share the same document number in the Spanish version. |
VAT/Sales Tax/Intrastat |
COD 10750 |
|
278492 |
The Previous Declared Amount field on the Customer/Vendor Warnings page is incorrect if you try to correct previous period amounts where invoices to Cartera were posted in the Spanish version. |
VAT/Sales Tax/Intrastat |
PAG 10736 REP 10710 TAB 254 |
|
278917 |
The Non Taxable Due To Localization Rules operations are not reflected in the VAT Statements VAT Model nor in the Sales Invoice Book report as they are set up as the NO TAX VAT calculation type for SII in the Spanish version. |
VAT/Sales Tax/Intrastat |
COD 10750 TAB 325 |
FR - France
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
275974 |
The Payment Amount and Total Amount fields in the Payment Practices report layout are incorrect if you apply several invoices to a same payment in the French version. |
Finance |
COD 10880 TAB 10881 |
|
277726 |
The Customer and Vendor Detail Balance report is incorrect if you have entries with the correction of remaining amount entry type in the French version. |
Finance |
REP 10806 REP 10808 |
|
280379 |
Payment period is not working as expected in the Payment Practices Reporting report in the French version. |
Finance |
COD 10880 |
IT - Italy
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
279074 |
If you run the Calc. and post VAT settlement report that reports a previous period input VAT, the test report does not show it as Next Period Input VAT in the Italian version. |
VAT/Sales Tax/Intrastat |
REP 20 |
NA - North America
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
278837 |
"The Hidden expression used in Tablix 'Table1' returned a data type that is not valid" error message when you run the Trial Balance Detail/Summary report with no records returned in the North American version. |
Finance |
REP 10021 |
|
276028 |
Settlement posting does not update the tax ledger entries with the offsetting settlement entries in the Tax Entries table in the North American version. |
VAT/Sales Tax/Intrastat |
COD 12 |
|
279486 |
Final invoiced sales amount does not match the prepayment invoice when sales taxes are included in the North American version. |
Sales |
COD 398 COD 442 COD 80 TAB 37 |
NL - Netherlands
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
273767 |
"Open must be equal to 'Yes'" error message when you import payment history into a Bank/Giro journal in the Dutch version. |
Finance |
COD 11000001 COD 11000002 TAB 11401 |
RU - Russia
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
277337 |
The Source Type filter and the Source No. filter on the G/L Account Turnover page do not work as expected in the G/L Account Card report in the Russian version. |
Finance |
REP 12437 |
|
277948 |
"You must delete the existing item tracking before modifying or deleting the Sales Line" error message in a specific scenario with apply an invoice to prepayment in the Russian version. |
Finance |
COD 6620 COD 80 COD 99000832 |
UK - United Kingdom
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
278517 |
"The operation cannot complete because it uses a feature that is not supported (Automation server.)" error message when you try to export the BACS payment file by using the Web client in the British version. |
Cash Management |
REP 10550 |
Local regulatory features
IT - Italy
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
279147 |
Electronic invoices for private companies in the Italian version. |
Financial Management |
COD12179 COD12180 COD12181 PAG459 PAG5919 TAB18 TAB311 TAB5911 TAB61 COD5980 |
Resolution
How to obtain the Microsoft Dynamics NAV update files
This update is available for manual download and installation from the Microsoft Download Center.
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 22 NAV 2017 AT package |
|
AU - Australia |
Download the CU 22 NAV 2017 AU package |
|
BE - Belgium |
Download the CU 22 NAV 2017 BE package |
|
CH - Switzerland |
Download the CU 22 NAV 2017 CH package |
|
CZ- Czech |
Download the CU 22 NAV 2017 CZ package |
|
DE - Germany |
Download the CU 22 NAV 2017 DE package |
|
DK - Denmark |
Download the CU 22 NAV 2017 DK package |
|
ES - Spain |
Download the CU 22 NAV 2017 ES package |
|
FI - Finland |
Download the CU 22 NAV 2017 FI package |
|
FR - France |
Download the CU 22 NAV 2017 FR package |
|
IS - Iceland |
Download the CU 22 NAV 2017 IS package |
|
IT - Italy |
Download the CU 22 NAV 2017 IT package |
|
NA - North America |
Download the CU 22 NAV 2017 NA package |
|
NL - Netherlands |
Download the CU 22 NAV 2017 NL package |
|
NO - Norway |
Download the CU 22 NAV 2017 NO package |
|
NZ - New Zealand |
Download the CU 22 NAV 2017 NZ package |
|
RU - Russia |
Download the CU 22 NAV 2017 RU package |
|
SE - Sweden |
Download the CU 22 NAV 2017 SE package |
|
UK - United Kingdom |
Download the CU 22 NAV 2017 UK package |
|
All other countries |
Download the CU 22 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.
