Cumulative Update 1 for Microsoft Dynamics NAV 2017 (Build 14199)

Applies to: Dynamics NAV 2017

This article applies to Microsoft Dynamics NAV 2017 for all countries and all language locales.


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.


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.

Known issue

You will receive the following compilation warning during the compile time:
Compilation warning
The warning does not influence the metadata generation.  If you change the CRM Connection SETUP table and save it without compilation, you can't run it anymore from the Dev environment. After you compile it, you can run the table. To work around the warning is to copy the Microsoft.IdentityModel.Client.ActiveDirectory.dll to the add-in folder of the RTC client installation folder. Microsoft.IdentityModel.Client.ActiveDirectory.dll can be found in the root folder of the RTC client.
C:\Program Files (x86)\Microsoft Dynamics NAV\100\RoleTailored Client
Copying it to
C:\Program Files (x86)\Microsoft Dynamics NAV\100\RoleTailored Client\Add-ins

Problems that are resolved in this cumulative update

The following problems are resolved in this cumulative update:

Platform hotfixes

381465When you use the report builder to save and compile reports, extra pages are displayed.
381481When you use the Import-NAVData cmdlet, the cmdlet may fail with large navdata files on Azure SQL.
381487You cannot run reports by using the Protocol Handler without Object Designer permissions tools.
381488Hash key is replaced by compiler.
381491The Export-NAVAppPermissionSet cmdlet exports similar permissions incorrectly.
381497Some card pages flicker when you open them.
381502Double characters are inserted when you enter data in the Korean language.
381507You cannot change the work date in PaaS localized versions.
381508When you use ReadMultiple with a SOAP, the web service returns an unfiltered record set if you specify a filter with a field name that does not exist.
381509Quick Entry does not work on a subpage in a certain scenario.
381510Profile groups cannot be readded.
381512"Invalid data encountered in stream, unable to read text" error message and the Debugger crashes when you try to debug a large codeunit.
381516Multiple script tags reference the same add-in on an HTML page for iFrame.
381517The client crashes when you edit a page type part that is placed in a group.
381580The CurrPage-Update method is not executed in Add-Trigger.
381582The NAV server with SaaS tenants mounted throws a timeout when it is being stopped.
381598Support for setting ManagementServicesPort through Powershell in the Set-NAVWebServerInstanceConfiguration cmdlet.
381599SQL transaction history causes CPU spike in production.
381615Connection problem with Dynamics 365 (CRM 2016 SP2 or later versions).
381622New GitHub-based CAB files are missing from the DVD.
381642Queries in extensions that use static values in filters can prevent the extensions from being installed.
381643Extensions calling COMMIT in upgrade code can cause the schema to become unsynchronized.
381644Extensions do not run upgrade code unless there is at least one table object or delta in the package.
381645Extensions requiring Json.Net cannot publish because of missing binding redirects.
381647The NAV service tier crashes when it handles an invalid SOAP web service call.
381657Queries must be processed when you reinitialize repaired or republished extensions.
381748The client crashes when you change the media data type with a RecordRef.
381791Support for the .NET Framework interoperability in combination with the Web client.
381924ETAG properties are added to OData V4 for all page web services.
381925The first specified sort field does not work.
381926When you install a combination of different random extensions, this can result in an error not allowing some new extensions to be installed and some installed extensions to be uninstalled.

Application hotfixes

IDTitleFunctional areaChanged objects
381725The Std. Password Dialog page returns a blank password.AdministrationPAG 9815
381367When you export a Positive Pay file that is a variable text comma-separated file type, no commas appear between columns in the exported file.Cash ManagementTAB 1222 XML 1231
381398The entries suggested under the Within Amount Tolerance field on the Payment-to-Entry Match FactBox on the Payment Application page are not accurate if you use Percentage as the match tolerance type.Cash ManagementTAB 274
381399The Payment Discount Tolerance Warning page does not appear in the payment reconciliation journal even if you apply entries where the Remaining Pmt. Discount Possible field has a value.Cash ManagementCOD 1255 COD 426 TAB 1293 TAB 1294 TAB 274
381400Payment discount tolerance entries are not created for certain periods if you post from the payment reconciliation journal and the Remaining Pmt. Discount Possible field has a value. Cash ManagementCOD 1255 COD 426 TAB 1293 TAB 1294 TAB 274
381416Repeated prompts to save the file are shown when you modify a budget in Excel.Cash ManagementREP 29
381593"Amount to Apply must not be larger than Remaining Amount in Cust. Ledger Entry Entry No.='XXX"' error message if you apply a payment in local currency to an invoice that is posted in a foreign currency from the reconciliation journal.Cash ManagementCOD 370 TAB 1294
381594When you export a Positive Pay file that includes a large check amount, the amount populates the file with commas.Cash ManagementCOD 1711 COD 47
381671Formatting issue in the Business Units report.Cash ManagementREP 17
381764The Remove Applications action in the payment reconciliation journal does not clear the Applies-to ID field on the customer and vendor ledger entries.Cash ManagementTAB 1294
381825"The Source Code does not exist. Identification fields and values: Code='' error message if you post a direct debit collection and do not have any journal lines.Cash ManagementREP 1201
381358The CRM table has the same captions as in the NAV tables.ClientTAB 5330 TAB 5340 TAB 5341 TAB 5342 TAB 5343 TAB 5344 TAB 5345 TAB 5346 TAB 5347 TAB 5348 TAB 5349 TAB 5350 TAB 5351 TAB 5352 TAB 5353 TAB 5354 TAB 5355 TAB 5356 TAB 5357 TAB 5359 TAB 5360 TAB 5361 TAB 5362 TAB 5363 TAB 5364 TAB 5365 TAB 5366 TAB 5367 TAB 5368 TAB 5370
381409"The length of the string is XY, but it must be less than or equal to 20 characters" error message because ADCS only supports 20 characters.ClientCOD 7701
381577Email / SMTP information with Cyrillic characters is translated to "???".ClientTAB 9500
381383When you implement standard cost changes in the standard cost worksheet, a revaluation journal line is generated now rounded to 3 decimals, which provides incorrect value in the Inventory Value (Revalued) field.CostingREP 5855
381567The Item Tracking Comments feature triggers false change log.CostingPAG 6504 PAG 6505 PAG 6508 PAG 6509 PAG 12418 PAG 12469
381394Debit/credit differs between G/L and the customer/vendor sub ledger.FinanceCOD 12
381404"The field Parent Code of table Data Exch. Line Def contains a value (XXX) that cannot be found in the related table (Data Exch. Line Def)." error message if you try to import a Data Exch. Definition file with the Parent Code field filled.FinanceTAB 1227 XML 1225
381595The G/L Dimension Overview page is not filtered accordingly when you use drill-down from the Analysis by Dimension page.FinancePAG 20
381823Limitations in the Web client makes it hard to get the G/L balance.FinancePAG 414
381374"The length of the string is X, but it must be less than or equal to 30 characters" error message when you choose the Show Matrix action in the Inventory Analysis report.InventoryCOD 7110
381376"You must assign a serial number for item X" error message when you post a transfer order receipt with item tracking and order-to-order binding.InventoryCOD 6500 COD 99000830
381380When you post a purchase return order, a reservation entry with reservation status Surplus is created.InventoryCOD 6500
381402"You cannot change the Type field on the Item because there exists at least one Purchase Line then includes this item" error message when you configure a master template for the Item table when purchase order lines with blank item numbers exist.InventoryTAB 27
381403The Item Tracking Specification report cuts off characters.InventoryREP 6520
381408"1,123 is not an accepted value. The field can only have 2 decimals" error message when you enter a value with 3 decimals or more in the Minimum Quantity field on the Sales Price or Purchase price page.InventoryTAB 7002 TAB 7012
381442A date conflict error is not raised when a reservation exists between a purchase order and a job planning line, and you change the planning date on a job planning line to a date earlier than the expected receipt date of the purchase.InventoryTAB 1003
381443Date conflict error is not raised when a reservation exists between a purchase order and a service order, and you change the needed date on the service line to a date earlier than the expected receipt date of the purchase.InventoryTAB 5902
381625The application does not consider already calculated and assigned cross-dock opportunities.InventoryCOD 5780 PAG 5783 TAB 5768
381630The Item Statistics Turnover page drills down from the Purchases (LCY) /Sales (LCY) fields to item ledger entries instead of value entries.InventoryPAG 354
381734"The Dimension Value does not exist. Identification fields and values: Dimension Code='XXXX',Code='' error message when you run the Calculate Inventory batch job in the physical inventory journal.InventoryREP 790
381543A job planning line remains in the Planned status after you delete the scheduled and reserved supply.JobsPAG 498 TAB 1003
381544A column is not visible on jobs planning lines.JobsCOD 1008 PAG 1002 PAG 1007 PAG 88 PAG 1001
381387The Replan function does not allow you to recreate lines as Refresh does when the production order is M-T-O.ManufacturingREP 99001026
381406Inconsistent behavior with inventory put-aways when the location is set as default on the warehouse employee setup.ManufacturingCOD 7321 PAG 7375 TAB 5766
381414An item can be deleted even if it is part of a certified production BOM version.ManufacturingTAB 27
381685"The change leads to a date conflict with existing reservations.. Cancel or change reservations and try again" error message when you change the ending date on the production order line and move the due date to an earlier date.ManufacturingCOD 99000813 COD 99000815 TAB 5407
381397When you post a sales order that gives a campaign discount, a campaign ledger is not created.MarketingCOD 5051 COD 80 REP 205 REP 206
381373When you print a special order from the carry out action message on the requisition worksheet, only one out of two purchase order for the same vendor is printed.PurchaseCOD 333 REP 493
381381When a purchase order is created directly for a drop a shipment, the description is not taken from the sales line but from item card.PurchaseCOD 76
381386The Carry Out Action Msg. function can create a drop-shipment purchase order with no location defined even when you select the Location Mandatory check box.PurchaseCOD 333
381401The GetVendLedgerEntry function in the Gen. Journal Line table uses a wrong reference to CustLedgEntry instead of VendLedgEntry.PurchaseTAB 81
381575When a purchase order is created for a drop shipment, the modified variant description on the sales line is lost.PurchaseCOD 76
381701When you print a special order from the carry out action message on the requisition worksheet, only one out of two purchase order for the same vendor is printed due to different purchasing codes.PurchaseCOD 333 REP 493
381382Performance issue when you run Order Tracking.SalesCOD 99000778
381384When you restore an archived sales quote, the Unit Cost field is updated with the unit cost from the item card instead of the unit cost from the archived sales quote.SalesCOD 5063
381390In the Price List report, the Sales Type option is not translated on the printout.SalesREP 715
381876"The Service Shipment Line already exists. Identification fields and values: Document No.='',Line No.='40000'" error message when you create certificates of supply if they are not already created for the sales shipment documents.SalesREP 780
381900The Total Excl. VAT field is incorrect in the Archived Sales Order report.SalesREP 215 REP 216
381388Slow performance when the database contains a lot of workflow information.ServerQUE 1501 QUE 1502
381731The due date is not updated on service orders when you make orders from the service quote.ServiceCOD 5923
381375"Object of type CodeUnit with ID 131004 could not be found" error message when you run the SCM Warehouse - Shipping Codeunit.UpgradeCOD 1230
381413"Forecast Date must have a value in Production Forecast Entry: Entry No.=X. It cannot be zero or empty" error message when you apply a configuration package to import forecast entries.UpgradeCOD 8611 COD 8613
381377"There are multiple expiration dates registered for lot X" error message when you register a warehouse shipment with both serial and lot number tracking.WarehouseCOD 6500
381405Creating a pick is allowed for a location with the Require Pick option disabled, but not for production.WarehouseREP 7305
381597The destination Type and Destination No. fields are not validated on an inventory pick.WarehouseCOD 7322

Local application hotfixes

AU - Australia
IDTitleFunctional areaChanged objects
381370Invalid characters are generated in the BAS XML file after you update and export the file in the Australian version.FinanceCOD 6224 COD 11601
BE - Belgium
IDTitleFunctional areaChanged objects
381854The Set Applies-to ID function on the Apply General Ledger Entries page does not work as expected in the Belgian version.FinancePAG 11309 PAG 20
381407Purchase invoices with non-deductible VAT leads to incorrect statistics if multiple VAT posting groups are used in the Belgian version.PurchasePAG 161 PAG 400
CH - Switzerland
IDTitleFunctional areaChanged objects
381385“Applies-to Entry must have a value ..." error message when you post an order with an item that has No Stockkeeping set to Yes and has an item charge assigned in the Swiss version.PurchasePAG 42 COD 80 COD 90
381695Unused code in the No Stockkeeping feature in the Swiss version.SalesTAB 27
CZ- Czech
IDTitleFunctional areaChanged objects
381439The Related-Party Name field in the payment reconciliation journal should get the value from the Name field on the bank statement lines when you fill the payment reconciliation journal in the Czech version.Cash ManagementREP 11701
381441The Within Amt Tolerance and Outside Amt Tolerance fields in the Payment-to-Entry Match FactBox do not include payments and refunds for the calculation in the Czech version.Cash ManagementTAB 274
381459No dimension is transferred from the vendor ledger entry and the Adv.Letter entry to the bank reconciliation journal in the Czech version.Cash ManagementCOD 1255 TAB 1294
381848The posted cash document contains a line that reverses the rounding in the Czech version.Cash ManagementTAB 11730
381851The checking of the bank account format is incorrect in the Czech version.Cash ManagementCOD 11711 REP 11700 TAB 11705 TAB 11707 TAB 11709 TAB 11711
381852New export SEPA payment in the Czech version.Cash ManagementCOD 11720 COD 1221 TAB 1226
381421The Glob. Dim. No. field is not set up for dimensions 3-8 when you use automatic generation of dimensions in the Czech version.FinanceCOD 408
381424The VAT date and posting group must not be populated with the balancing entry for sales posting in the Czech version.FinanceCOD 5987 COD 80 COD 90 REP 20 TAB 81
381419When you use the Whse. Net Change template, the test field for the entry type is missing in the Czech version.InventoryTAB 83
381415You cannot deduct the same purchase advance letter from more than one purchase invoice in the Czech version.PrepaymentsPAG 31001 PAG 31021
381418If you have an invoice with a prepayment and you change the vendor/customer posting group on the invoice, you get more G/L entries than necessary in the Czech version.PrepaymentsCOD 31000 COD 31020
381846The VAT Recap page contains a prepayment although no advance invoice exists in the Czech version.PrepaymentsCOD 31000
381821The Compensation field on the Customer Ledger Entries page is not filled in correctly if you post credits in the Czech version.PurchaseCOD 31052
381831Incorrect currency code in sales and purchase archives in the Czech version.SalesREP 31091 REP 31092 REP 31095
381427"VAT Base (LCY) must have a value in VAT Amount Line" error message when you change the VAT Amount (LCY) field on the VAT Amount Lines Page for a subcontracting purchase order in the Czech version.VAT/Sales Tax/IntrastatTAB 39
381461The functionality for electronic evidence of turnover checks the values in the data response message in the Czech version.VAT/Sales Tax/IntrastatCOD 11730 COD 11732 COD 31120 COD 31121 COD 31132 COD 80
381464The calculation of amount is wrong in the Intrastat journal in the Czech version.VAT/Sales Tax/IntrastatREP 594
381820If you use reverse charge VAT and non-deductible VAT for the balance account, then the non-deductible VAT is not posted in the Czech version.VAT/Sales Tax/IntrastatTAB 81
381840The EET - Simplified sales regime does not work in the Czech version.VAT/Sales Tax/IntrastatCOD 31121 PAG 11741
381845The last modification is taken into account in the service for getting entries for the Intrastat journal in the Czech version.VAT/Sales Tax/IntrastatREP 594
381847If you use the Fixed Asset or Charge (Item) type on an invoice line and the Tariff No. field is filled in, then the Commodity Code field is not filled in the VAT Control report line in the Czech version.VAT/Sales Tax/IntrastatCOD 31100
381849Services and Intrastat in the Czech version.VAT/Sales Tax/IntrastatCOD 423 PAG 31062 PAG 5900 PAG 5905 PAG 5933 PAG 5934 PAG 5935 PAG 5936 PAG 5964 PAG 5966 PAG 5972 PAG 5975 PAG 5978 TAB 111 TAB 113 TAB 115 TAB 121 TAB 123 TAB 125 TAB 169 TAB 210 TAB 263 TAB 27 TAB 31062 TAB 32 TAB 37 TAB 39 TAB 5741 TAB 5900 TAB 5902 TAB 5990 TAB 5991 TAB 5992 TAB 5993 TAB 5994 TAB 5995 TAB 83
IDTitleFunctional areaChanged objects
381700In the Payment Journal Details FactBox, refunds are not calculated and this leads to an incorrect value in the Payments field in the DACH version.Cash ManagementPAG 35516 PAG 35517
381526The Copy Documents function leads to different results depending on whether the source is a sales order or an archived sales order in the DACH version.SalesCOD 6620
381359Performance issues with the Sales VAT Adv. Not. Acc. Proof report in the DACH version.VAT/Sales Tax/IntrastatCOD 12 PAG 315 REP 11009 TAB 254
DE - Germany
IDTitleFunctional areaChanged objects
381681"Lot No. X is not available on inventory or it has already been reserved for another document" error message when you register an inventory movement worksheet for a reserved inventory item in the German version.WarehouseCOD 7307 TAB 5767
ES - Spain
IDTitleFunctional areaChanged objects
381412Overdue and non-overdue open payments should be included in the Open Payments section in the Vendor - Overdue Payments report in the Spanish version.PurchaseREP 10748
381569The Recipient Bank Account field in the payment journal should be updated with the bank of the applying document and not always use the default one from the vendor card in the Spanish version.PurchaseCOD 442 COD 444 REP 393 TAB 81
FR - France
IDTitleFunctional areaChanged objects
381392If you suggest vendor payments from the payment slip card, even if the vendor ledger entries are posted with different dimension codes, then all suggested payment slip lines are assigned the same dimension code in the French version.Cash ManagementREP 10862 REP 10864
381898The Payment in Progress (LCY) field on the customer card should only be included in the calculation for entries where the payment is in progress in the French version.Cash ManagementCOD 10860
381457The Currency Exch. Rate field is incorrect if you use the Suggest Vendor Payments function on the Payment Slip page in the French version.FinanceREP 10862
IT - Italy
IDTitleFunctional areaChanged objects
381393If you post a vendor bill list, the Vendor Bill No. field of the posted bill list takes the number of the posted vendor bill list header, and the Vendor Bill No. field in the Vendor Ledger Entry table is missing in the Italian version.FinanceCOD 12173 TAB 12182
381395Blacklist entries are declared even if the total of the posted invoices does not exceed the blacklist threshold amount in the Italian version.VAT/Sales Tax/IntrastatCOD 12130
381396The purchase amounts of the blacklist communication are declared twice in the Italian version.VAT/Sales Tax/IntrastatCOD 12130
381568The operation occurred date that is reported in the VAT Entry table is not correct after you post a sales or purchase invoice in the Italian version.VAT/Sales Tax/IntrastatCOD 80
NA - North America
IDTitleFunctional areaChanged objects
381371In the G/L Register, the SourceName variable is too short and causes vendors with more than 30 characters in the name in the North American version.FinanceREP 10019
381649When a tax area code contains two or more sales tax jurisdictions by using the Expense/Capitalize Sales Tax functionality, incorrect G/L deferral entries are created in the North American version.PurchaseTAB 37 TAB 39
381372The Sales Credit Memo report footer is printed on all pages in the North American version.SalesREP 10073
381389The Service Invoices report does not show totals in the print preview in the North American version.ServiceREP 10474
381391When a manual payment is applied to an invoice, incorrect realized VAT amounts are generated if the Mexico Cash Basis Unrealized VAT type is used in the North American version.VAT/Sales Tax/IntrastatCOD 12
SE - Sweden
IDTitleFunctional areaChanged objects
381463The SIE Import functionality does not work as expected in the Swedish version.FinanceREP 11208 TAB 98
381566When you create reminders, and include a posting that is not due, then the first line of the not-overdue items is suggested twice in the Swedish version.FinanceCOD 392


Hotfix information

A supported hotfix is available from Microsoft. There is a "Hotfix Download Available" section at the top of this Knowledge Base article. If you are encountering an issue downloading, installing this hotfix, or have other technical support questions, contact your partner or, if enrolled in a support plan directly with Microsoft, you can contact technical support for Microsoft Dynamics and create a new support request. To do this, visit the following Microsoft website: You can also contact technical support for Microsoft Dynamics by phone using these links for country specific phone numbers. To do this, visit one of the following Microsoft websites:

PartnersCustomersIn special cases, charges that are ordinarily incurred for support calls may be canceled if a Technical Support Professional for Microsoft Dynamics and related products determines that a specific update will resolve your problem. The usual support costs will apply to any additional support questions and issues that do not qualify for the specific update in question.

How to obtain the Microsoft Dynamics NAV update files

Click the link in the "Hotfix Download Available" section at the top of this Knowledge Base article to download the cumulative update files. After you request the Microsoft Dynamics NAV update, a hyperlink will be sent to you in an e-mail.

The e-mail will contain a hyperlink and a password. You can use the hyperlink to download the Microsoft Dynamics NAV hotfix or the update files. When you click the hyperlink, the File Download - Security Warning dialog box opens. Then, you are prompted to run, to save, or to cancel the download.

If you click Run, the files start the download and the extraction process. You must specify a folder for the new files.

If you click Save, you must specify a path for saving the compressed file. When you open the file that you saved, you are prompted to specify a path for the files.

If you click Cancel, the download process stops.

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:
CountryHotfix package
AT - AustriaDownload the ATKB3209071 package
AU - AustraliaDownload the AUKB3209071 package
BE - BelgiumDownload the BEKB3209071 package
CH - SwitzerlandDownload the CHKB3209071 package
CZ- CzechDownload the CZKB3209071 package
DE - Germany Download the DEKB3209071 package
DK - DenmarkDownload the DKKB3209071 package
ES - SpainDownload the ESKB3209071 package
FI - FinlandDownload the FIKB3209071 package
FR - FranceDownload the FRKB3209071 package
IS - IcelandDownload the ISKB3209071 package
IT - ItalyDownload the ITKB3209071 package
IN - IndiaDownload the INKB3209071 package
NA - North AmericaDownload the NAKB3209071 package
NL - NetherlandsDownload the NLKB3209071 package
NO - NorwayDownload the NOKB3209071 package
NZ - New ZealandDownload the NZKB3209071 package
RU - RussiaDownload the RUKB3209071 package
SE - SwedenDownload the SEKB3209071 package
UK - United KingdomDownload the GBKB3209071 package
All other countriesDownload the W1KB3209071 package

How to install a Microsoft Dynamics NAV 2017 cumulative update

See How to install a Microsoft Dynamics NAV 2017 cumulative update .


You must have Microsoft Dynamics NAV 2017 installed to apply this hotfix.

More Information


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.