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).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.
For a list of cumulative updates released for Microsoft Dynamics NAV 2017, seeProblems that are resolved in this cumulative update
The following problems are resolved in this cumulative update:
Platform hotfixes
ID |
Title |
---|---|
206872 |
"Cannot access a disposed object" error message when integrating with Dynamics 365 for Sales (CRM). |
233874 |
Problems with auto-scrolling up in the Web client when you enter lines in document orders, purchase order lines, or sales order lines. |
251532 |
FIELDCAPTION with Date Virtual Table fields are not translated within AL. |
251614 |
Task scheduler causes deadlocks in a multiple service scenario that causes phantom running job queue entries. |
251695 |
Menu items are lost when you add them to a user with specific permissions. |
252833 |
It is not possible to remove an added element from the navigation pane. |
253239 |
The client crashes if you change a copied permission set. |
254438 |
The HideValue property can be cheated to reveal its value. |
254588 |
Dynamics 365 (CRM) SDK in the cmdlets requires TLS 1.2 to be set. |
254648 |
"Cannot assign a scope id. The maximum number of methods for 8" error message is displayed. |
254976 |
Object reference is not set to an instance of an object when you try to run scheduled tasks if Dynamics NAV is running in Azure. |
255086 |
You can set language and company by using the Set-NAVServerUser and New-NAVServerUser cmdlets. |
255145 |
The Windows client crashes when there is a CurrPage.EDITABLE(FALSE) in the OnOpenPage trigger. |
255464 |
The DISPLAYBARCODE field does not work as expected with Word documents. |
255520 |
NAV APP for Android-based tablet and phone blanks out all fields when you edit a record. |
256107 |
Upgrade does not set permissions on System Tables, which blocks synchronization. |
256142 |
Performance issues after you deploy Dynamics NAV 2017 CU 12 because of a huge scan of object metadata and object metadata snapshot tables. |
Application hotfixes
ID |
Title |
Functional area |
Changed objects |
---|---|---|---|
251191 |
Logging time does not work with the Web client. |
Administration |
COD 40 |
251670 |
Errors in the import from the Excel Data Migration tool result in mostly blank records being created. |
Administration |
COD 1806 COD 8611 |
253058 |
"The length of the string is Value, but it must be less than or equal to 250 characters" error message when you enter a VAT registration number on the Customer, Vendor or Contact page. |
Administration |
TAB 381 |
256551 |
Recurring job queue entries are not rescheduled after the first run. |
Administration |
COD 453 |
252237 |
If you change the Description field on the Reverse Transaction Entries page, the change is ignored when you use the Reverse and Post function. |
Finance |
COD 17 COD 5600 |
252849 |
Several fields on the Customer Statistic FactBox page are not calculated when a date filter is set. |
Finance |
PAG 9082 PAG 9094 |
253353 |
"The date is not valid" error message on the Customer Card page after you close an invoice with an empty due date. |
Finance |
COD 763 |
254101 |
If you post a sale order that comes from an IC purchase order posting, when you check the IC outbox entry details, the system does not show the IC partner reference of the G/l account that is used to post the sale invoice. |
Finance |
COD 427 |
254324 |
If you use the Adjust Exchange Rate function for subsequent years, an incorrect G/L account is used. |
Finance |
REP 595 |
255470 |
The Additional Fee and Interest Amount fields are displayed oddly in a printed Reminder report. |
Finance |
REP 117 |
255530 |
"The Item does not exist. Identification fields and values: No.='6120'" error message when you post an invoice with G/L account lines and Shipping Advise = TRUE. |
Finance |
TAB 36 |
255567 |
The G/L Register report does not print the journal numbers correctly if they are longer than 4 digits. |
Finance |
REP 3 |
252765 |
Insert or modify the attribute value on the Item Category Card page causes performance issues. |
Inventory |
COD 7500 TAB 7505 |
253621 |
"The field Variant Code of table Item Journal Line contains a value that cannot be found in the related table (Item Variant)" error message when you run the Calculate Inventory report from the Phys. Inventory Journal page. |
Inventory |
REP 790 |
255800 |
"The Config. Template Line already exists. Identification fields and values: Data Template Code='',Line No.='100000'" error message when you run the Save As Template action from the Item Card page. |
Inventory |
COD 8612 |
252104 |
When you post inventory cost to a G/L batch job per a posting group, consolidated G/L entries representing several Jobs contains a Job No field which should be blank. |
Jobs |
COD 5802 |
253648 |
"The Job Task cannot be modified because the job has associated job WIP entries" error message when you modify the description in a job task. |
Jobs |
COD 1000 TAB 1001 |
254113 |
Items of type service may be purchased for jobs but then the update job item cost will update the actual invoiced cost amount to zero because the service item cost resides in the cost amount (Non-Inventoriable) instead of cost amount (Actual). |
Jobs |
COD 90 REP 1095 |
253201 |
The To-Production Bin Code field from the Work Center is not recognized when you create the production order from the Planning Worksheet page. |
Manufacturing |
COD 99000809 TAB 99000829 |
254341 |
Pick document does not contain all components when a production order is created through planning and this is a make-to-order production. |
Manufacturing |
COD 5431 |
253938 |
"The length of the string is Value1, but it must be less than or equal to Value2 characters" error message when a salesperson code has more than 7 characters. |
Marketing |
TAB 5065 |
252892 |
Unexpected lines are suggested when you use the GetReceipt Lines function. |
Purchase |
TAB 121 |
253613 |
"You cannot change Variant Code because the order line is associated with sales order 1001" error message when you assign a blanket purchase order to a purchase line that is related to drop shipment. |
Purchase |
TAB 37 TAB 39 |
253750 |
When you post a purchase receipt and purchase invoice in same posting process, a line with negative quantity will be recorded with a positive quantity that is invoiced in a posted purchase receipt document. |
Purchase |
COD 80 COD 90 |
254399 |
The Total Excl. VAT field in the purchase order contains an amount even though the Line Amount Excl. VAT field is zero. |
Purchase |
COD 57 PAG 54 |
256045 |
The Sell-to Customer No. field should be validated in the Invoice Details FastTab from the purchase header when you create this purchase with a special order option. |
Purchase |
COD 333 TAB 38 |
257861 |
When you post a purchase return receipt and a purchase credit in the same posting process, a line with negative quantity will be recorded with a positive quantity invoiced in the posted purchase return receipt document. |
Purchase |
COD 80 COD 90 |
257883 |
When you post a purchase return receipt and a purchase credit in a same posting process, a line with negative quantity will be recorded with a positive quantity invoiced in the posted purchase return receipt document. |
Purchase |
COD 80 COD 90 |
251570 |
Dynamics NAV and Dynamics 365 allows a customer to be deleted even if it's on a saved document like a sales invoice. |
Sales |
TAB 18 TAB 23 |
253101 |
An unnecessary entry is created in the Reservation Entry table when you change the quantity in the sales invoice for an item with Item tracking and post it. |
Sales |
COD 99000832 COD 99000834 |
253682 |
It is not possible to add an item number to the Sales Prices page. |
Sales |
PAG 7002 |
253711 |
You notice that NAV Assembly to Order products are not handled properly by Dynamics 365 for Sales (CRM) integration when they are included in a sales order that is created in Dynamics 365 for Sales (CRM ). |
Sales |
COD 5343 |
254317 |
"An attempt was made to change an old version of a Sales Header record" error message when you create a sales invoice with a copy document. |
Sales |
19506030 |
254437 |
The words “for Sales” are missing in several places. |
Sales |
MEN 1010 TAB 5330 |
254851 |
The Allow Line Discount and Allow Invoice Discount fields always appear as TRUE on the Sales Price and Line Discounts page. |
Sales |
TAB 1304 |
255881 |
"The Warehouse Entry already exists. Identification fields and values: Entry No.=EntryNumber" error message when you undo a shipment from a posted sales shipment that contains two assembly items. |
Sales |
COD 5815 COD 7320 COD 900 |
252196 |
Variant code is undefined when you post inventory put-away for a production output. |
Warehouse |
COD 7324 COD 99000854 TAB 37 TAB 83 |
253649 |
Put-away creation does not consider maximum quantity that is defined in the bin content when the quantity in the bin content is already above its maximum capacity. |
Warehouse |
COD 7313 |
254427 |
Quantity outstanding is calculated before quantity base when the quantity is validated in a warehouse receipt. |
Warehouse |
TAB 7317 TAB 7321 |
254516 |
Warehouse pick generated from the pick worksheet does not properly flag the pick lines for components with Assemble To Order = True for components on an assemble to order (ATO) assembly BOMs, which results in an incorrect presentation on bin contents. |
Warehouse |
TAB 5767 |
256463 |
Improvement on the warehouse register when using warehouse management with item tracking. |
Warehouse |
COD 7307 |
256472 |
Consumption posting loops through the existing assigned item tracking when these are not posted. |
Warehouse |
COD 99000838 |
Local application hotfixes
APAC
ID |
Title |
Functional area |
Changed objects |
---|---|---|---|
252241 |
The Sales Line Description field is not posted to G/L entries in the APAC version. |
Finance |
COD 5987 COD 80 TAB 49 |
CH - Switzerland
ID |
Title |
Functional area |
Changed objects |
---|---|---|---|
254296 |
The Reference No. field is not used for matching when you import the CAMT 054 file in the Swiss version. |
Cash Management |
COD 11503 COD 1255 |
254502 |
Vendor payment file of Payment Type = 5 cannot be created because of a missing SWIFT code even though the SWIFT code seems not needed for the file creation and validation in the Swiss version. |
Cash Management |
COD 1223 |
254631 |
Incorrect caption in the Suggested Swiss SEPA payment export type field on the Vendor Bank Account Card page in the Swiss version. |
Cash Management |
PAG 425 |
254675 |
Vendor Payment file of Payment Type = 1 cannot be validated correctly if, instead of the ESR Account No. field, only the IBAN without the BIC is used in the Swiss version. |
Cash Management |
TAB 288 |
255830 |
Only one of the SWIFT Code or BIC (Bank Identifier Code) fields should appear on the Vendor Bank Account page in the Swiss version. |
Cash Management |
PAG 425 |
CZ- Czech
ID |
Title |
Functional area |
Changed objects |
---|---|---|---|
256336 |
Differences in the application behavior in a general journal and in the cash documents in the Czech version. |
Finance |
TAB 81 TAB 11731 |
256344 |
You cannot set enough stockkeeping unit templates in the Czech version. |
Inventory |
REP 5706 |
254314 |
Incorrect rounding on a sales document caused by a line with blank type in the Czech version. |
Sales |
COD 80 |
DE - Germany
ID |
Title |
Functional area |
Changed objects |
---|---|---|---|
254449 |
Translation issue in the tooltip of the Blanket Order No. and Blanket Order Line No. fields are incorrect in several pages in the German version. |
Administration |
N/A |
ES - Spain
ID |
Title |
Functional area |
Changed objects |
---|---|---|---|
251157 |
If you post a purchase document with a Buy-from Vendor no. field that is different than the Pay-to Vendor field, the document is rejected by the SII interface in the Spanish version. |
Finance |
COD 10750 |
253772 |
Sales documents do not have the correct values on the initial upload in the Spanish version. |
Finance |
COD 10750 COD 10752 COD 10756 PAG 10751 PAG 10752 REP 10707 TAB 10750 TAB 10751 TAB 10752 |
254615 |
"Codigo[4102].El XML no cumple el esquema. Falta informar campo obligatorio.: DesgloseTipoOperacion" error message if you post an international sales document in the Spanish version. |
Finance |
COD 10750 |
254973 |
"You do not have the following permissions on TableData Closed Payment Order: Modify" error message if you try to delete a new bank account without any entry associated, but posted payment orders in Cartera in the Spanish version. |
Finance |
COD 7000004 |
255491 |
The FechaRegContable field is incorrect for purchase documents if the posting date is different than the system date in the Spanish version. |
Finance |
COD 10750 |
FR - France
ID |
Title |
Functional area |
Changed objects |
---|---|---|---|
254017 |
If you apply and unapply G/L entries multiple times, the Letter field only shows ZZZ in the French version. |
Finance |
COD 10842 REP 10842 TAB 17 |
IT - Italy
ID |
Title |
Functional area |
Changed objects |
---|---|---|---|
253610 |
If you insert a new purchase invoice for a withholding tax vendor from a purchase invoices list, the system does not insert the withholding tax code or the Soc.sec. code in the Italian version. |
Finance |
TAB 12137 TAB 38 |
256187 |
The foreign vendor purchase invoices must be linked to the related custom invoices even if the country is not set a black listed country in the Italian version. |
Purchase |
COD 12 |
252594 |
If the vendor card reports the fiscal code and the VAT Registration No. field, the DatiFAttura file always reports the Fiscal code field content instead of the VAT Registration No. field content in the <IDCodice> field in the Italian version. |
VAT/Sales Tax/Intrastat |
COD 12182 |
253535 |
The un-deductible part of purchase invoices and credit memo base amount should be included in the <TotaleOperazioniPAssive> of the period VAT settlement communication in the Italian version. |
VAT/Sales Tax/Intrastat |
COD 12151 |
253604 |
If you add the Tax Representative No. field in the sales or purchase invoice document, the VAT fiscal register does not report the VAT Registration No. field of the Tax Representative No. field that is inserted in the Italian version. |
VAT/Sales Tax/Intrastat |
REP 12120 |
NA - North America
ID |
Title |
Functional area |
Changed objects |
---|---|---|---|
254007 |
"The length of the string is Value, but it must be less than or equal to 20 characters" error message for the Bank Account Reconciliation report in the North American version. |
Cash Management |
TAB 1284 |
UK - United Kingdom
ID |
Title |
Functional area |
Changed objects |
---|---|---|---|
253948 |
Partial payments lead to incorrect calculations on the Payment Practice report in the British version. |
Purchase |
COD 10525 |
RU - Russia
ID |
Title |
Functional area |
Changed objects |
---|---|---|---|
254542 |
Incorrect print form is used for the FA Phys. Inventory INV-1 report in the Russian version. |
Finance |
REP 12486 |
255105 |
The G/L Account page is turned over after re-opening and the lines are not filtered by the Source Type Filter and Source No. Filter fields in the Russian version. |
Finance |
PAG 12405 |
255458 |
The detailed by account area is not filtered by the Source Type Filter and Source No. Filter fields in the G/L Account Entries Analysis report in the Russian version. |
Finance |
COD 12403 PAG 12405 TAB 12400 |
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 15 NAV 2017 AT package |
AU - Australia |
Download the CU 15 NAV 2017 AU package |
BE - Belgium |
Download the CU 15 NAV 2017 BE package |
CH - Switzerland |
Download the CU 15 NAV 2017 CH package |
CZ- Czech |
Download the CU 15 NAV 2017 CZ package |
DE - Germany |
Download the CU 15 NAV 2017 DE package |
DK - Denmark |
Download the CU 15 NAV 2017 DK package |
ES - Spain |
Download the CU 15 NAV 2017 ES package |
FI - Finland |
Download the CU 15 NAV 2017 FI package |
FR - France |
Download the CU 15 NAV 2017 FR package |
IS - Iceland |
Download the CU 15 NAV 2017 IS package |
IT - Italy |
Download the CU 15 NAV 2017 IT package |
NA - North America |
Download the CU 15 NAV 2017 NA package |
NL - Netherlands |
Download the CU 15 NAV 2017 NL package |
NO - Norway |
Download the CU 15 NAV 2017 NO package |
NZ - New Zealand |
Download the CU 15 NAV 2017 NZ package |
RU - Russia |
Download the CU 15 NAV 2017 RU package |
SE - Sweden |
Download the CU 15 NAV 2017 SE package |
UK - United Kingdom |
Download the CU 15 NAV 2017 UK package |
All other countries |
Download the CU 15 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.