This article applies to Microsoft Dynamics NAV 2016 for all countries and all language locales. See RELEASE NOTE Microsoft Dynamics ® NAV 2016 Russia.
Overview
This cumulative update includes all hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2016, 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 2016, see released cumulative updates for Microsoft Dynamics NAV 2016. Cumulative updates are intended for new and existing customers who are running Microsoft Dynamics NAV 2016.
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 |
|---|---|
|
200769 |
OData filters using the StartsWith() method fail to return qualifying records if the EnableODataStrictFiltering value is set to TRUE. |
|
200814 |
Page opened modally only shows the first 20 rows. |
|
201039 |
The Sana Commerce extension cannot be installed due to platform query issues. |
|
201799 |
User permission error in the Web client displays a server error message and causes two unnecessary and confusing errors in the event viewer. |
|
202752 |
Cannot include menu suites across dependencies in extensions V1. |
|
204108 |
Multiple rows from Excel are not copied on the General Journal page without validation errors or warnings. |
|
204910 |
The Post & Print to PDF function from the request window does not allow you to save PDF files. |
|
205080 |
Compilation of assembly error is displayed when you assign return value of a Try function to a Table field. |
|
205090 |
UNBINDSUBCRIPTION in the OnBeforeCompanyOpen function crashes the client. |
|
205184 |
Error when logging in as a O365 user where the full name contains Hebrew characters. |
|
205337 |
The Excel Add-In does not correctly identify shown data as temporary and open to a data export leak. |
|
205756 |
The color of the Subordinate Style property is too light compared with NAV 2013 R2 or earlier versions and cannot be easily read in lists and FactBboxes. |
|
208597 |
The FORMAT function incorrectly returns 0 rather than 7 as weekday for Sunday. |
Application hotfixes
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
203345 |
When you use both deferral code and currency code with a currency exchange rate that has been changed on the purchase header, Dynamics NAV creates unexpected G/L and VAT entries. |
Finance |
COD 12 COD 80 COD 90 |
|
204189 |
The quantity invoiced on a purchase order is not updated after you create the invoice through intercompany and there is item tracking. |
Finance |
COD 427 |
|
204655 |
"You may not enter numbers manually. If you want to enter numbers manually please activate Manual Nos. in No. Series XXX." error message if you manually try to change a number series value that has a relationship with another number series value with manual and automatic numbering. |
Finance |
TAB 18 TAB 23 |
|
205312 |
"The Assembly Header does not exist" error message on the Pick Worksheet page after you process a partial pick of a component of an assembly item by using a basic-warehouse location with the Require Shipment, Pick, and Bin Mandatory settings. |
Finance |
COD 900 |
|
206826 |
G/L inconsistency error message appears on posting a sales order with 100% prepayment, price incl. VAT, and partial shipment. |
Finance |
COD 80 COD 90 |
|
207185 |
"Date is not valid" error message when you try to run the Close Income Statement report. The error message does not point to the reason for the error. |
Finance |
REP 94 |
|
207621 |
The consolidation currency adjustment for closing rate accounts due to the change in exchange rate are posting with a global dimension and a dimension value inherited from other consolidated entries incorrectly. |
Finance |
COD 432 |
|
208624 |
Sales and purchase budgets are mixed up on the Sales and Purchase Analysis By Dimensions pages. |
Finance |
COD 7150 |
|
208919 |
Analysis View Budget entries are not deleted after you delete budget lines. |
Finance |
TAB 96 |
|
210417 |
The quantity invoiced on a purchase order is not updated after you create the invoice through intercompany and there is item tracking. |
Finance |
COD 427 |
|
202033 |
Inconsistent results in the requisition worksheet depending on whether a calculate plan is run for each location separately or in one run. |
Manufacturing |
COD 99000854 REP 699 |
|
202772 |
Absent registration is not considered when you use constrained capacity. |
Manufacturing |
COD 99000810 |
|
204345 |
"The length of the string is 11, but it must be less than or equal to 10 characters. Value: '200.000'' error message when you delete a line on the Planning Worksheet page. |
Manufacturing |
COD 99000778 |
|
205175 |
The Calc. Regenerative plan suggests a line based on the Components at Location option when the item is an assembly item and not a component. |
Manufacturing |
COD 99000854 |
|
205829 |
Dampener quantity is not considered when you run the Calc. Regenerative Planning report in the Planning Worksheet page with lot-for-lot reordering. |
Manufacturing |
COD 99000854 |
|
208091 |
A send-ahead quantity is not considered when a production order is created through the Calc. Regenerative Planning function on the Planning Worksheet page. |
Manufacturing |
COD 99000810 |
|
205305 |
The attachment is not embedded in the email body when you log an interaction with the Send Word Docs. as Attmt. option. |
Marketing |
COD 5054 |
|
208170 |
The Payment Total field on the Vendor - Payment Receipt report should have a different caption to make clear that its purpose is for payment tolerance totals. |
Purchase |
REP 411 |
|
209761 |
The Buy-from Vendor No. field is deleted after you post the receipt and re-open a drop shipment purchase order. |
Purchase |
TAB 38 |
|
205055 |
"Quantity Invoiced must not be greater than the sum of Qty. Assigned and Qty. to Assign" error message when you try to print a blanket order with item charges that has been partially shipped and invoiced. |
Sales |
TAB 37 TAB 39 |
|
205847 |
When you post a batch for sales invoices, the Replace Posting Date value does not work with a certain Sales & Receivables setup. |
Sales |
COD 80 COD 90 |
|
210213 |
The invoice discount is not distributed to the document lines correctly in scenarios with partial invoicing, and no confirm message is shown. |
Sales |
PAG 46 PAG 54 |
|
210399 |
"Amount must be positive in Gen. Journal Line Journal Template Name='',Journal Batch Name='',Line No.='0'." error message when you post a sales or purchase order with prepayment and prices incl. VAT. |
Sales |
COD 80 COD 90 |
|
202716 |
When you use the functionality to undo consumption for posted service shipment lines, Dynamics NAV reverses consumption in service ledger entries, however the reversal is not reflected in the general ledger. |
Service |
COD 5819 |
|
204621 |
"Select a Dimension Value Code for the Dimension Code XX for G/L Account XX." error message if you try to post a service order that creates some rounding, and one of the dimensions on the Invoice Rounding G/L Account page is set to Code Mandatory. |
Service |
COD 5986 COD 5987 |
|
211138 |
The Undo Shipment and Undo Consumption functions on the Service Shipment Lines page creates new entries with the posting date from the Service Shipment header and not from the original posting date. |
Service |
COD 5819 |
|
201925 |
"Qty. to Handle (Base) in Tracking Specification for Item No. X, Serial No.: Y, Lot No.: Z is currently A. It must be B" error message when you post a warehouse shipment. |
Warehouse |
COD 7307 |
|
204343 |
For a warehouse employee, it is necessary to have the permission that allows changes on item cards or modifications in sales and purchase documents. This should not be necessary. |
Warehouse |
COD 5804 COD 5895 |
Local application hotfixes
AT - Austria
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
210194 |
Although 1000 lines with 0,16 kg exist in the Intrastat journal, the total weight in the file appears with 0,00 when the authorities expect 160 kg in the Austrian version. |
VAT/Sales Tax/Intrastat |
REP 11106 |
BE - Belgium
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
203940 |
"The operation cannot complete because it uses a feature that is not supported (.NET Framework Interoperability)" error message when you try to select a file name on the EB Payment Journal page by using the Web client in the Belgian version. |
Finance |
REP 2000005 |
|
208891 |
VAT settlement creates wrong entries in case of non-deductible reverse charge VAT in the Belgian version. |
VAT/Sales Tax/Intrastat |
REP 20 |
CH - Switzerland
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
208075 |
The Import Post Code report cannot be used anymore after a format change in the Swiss version. |
Administration |
REP 11502 |
DACH
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
208580 |
The SetGLAccountNoInVATEntries function slows down the posting routine significantly in the DACH version. |
Finance |
COD 12 PAG 315 TAB 254 |
DE - Germany
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
204365 |
Test report does not check the missing Intratstat Code value on the Country/Region Code page in the German version. |
Finance |
COD |
ES - Spain
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
206339 |
The New Page field does not have any effect in the VAT Statement report preview and print if the VAT Statement Name value is set up with the two-column report template in the Spanish version. |
Finance |
REP 12 |
|
204097 |
The Base field is incorrect in the VAT Entries page and in the Sales and Purchase Invoice Books page if you post an invoice with a payment discount in the Spanish version. |
Purchase |
COD 80 COD 90 |
|
203848 |
The Bills Account value is used incorrectly if you unapply a payment and a refund for a customer which uses the payment method that creates bills in the Spanish version. |
Sales |
COD 12 |
|
206544 |
The Make 347 Declaration report takes a long time to export the file in the Spanish version. |
VAT/Sales Tax/Intrastat |
REP 10707 |
|
210613 |
No Taxable VAT operations should be included in the 340 VAT Declaration page in the Spanish version. |
VAT/Sales Tax/Intrastat |
REP 10743 |
FR - France
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
206421 |
The conditions in a workflow are not kept if you switch to another language in the French version. |
Finance |
COD 1530 |
|
207156 |
The G/L Detail Trial Balance report does not show entries when they have the same G/L Account, Document No., Posting Date, and Amount values in the French version. |
Finance |
REP 10804 |
|
208539 |
The G/L Detail Trial Balance report does not show entries when they have the same G/L Account, Document No., Posting Date, and Amount values in the French version. |
Finance |
REP 10804 |
|
208794 |
The general ledger entries with zero amount should be excluded from the Export G/L Entries - Tax Audit report in the French version. |
Finance |
REP 10885 |
|
209011 |
When you group entries in the Intrastat journal, the result is not correct in the French version. |
VAT/Sales Tax/Intrastat |
REP 594 |
IT - Italy
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
206930 |
The Certification Utica 2017 declaration file structure has been modified and the file is no longer accepted in the Italian version. |
Finance |
COD 12132 |
NA - North America
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
205957 |
The beginning balance line is listed twice on the Trial Balance Detail/Summary page in the American version. |
Administration |
REP 10021 |
|
205876 |
The description from the Cross Reference No. field does not populate correctly on the purchase order when it is created from the Planning Worksheet page in the American version. |
Inventory |
COD 76 TAB 246 TAB 5717 |
|
206359 |
A negative lead time calculation is allowed (for example, 6W-8W) and it causes the planning system to hang and not respond in the American version. |
Inventory |
COD 5404 TAB 23 TAB 27 TAB 38 TAB 39 TAB 5700 TAB 99 |
|
208265 |
"There are multiple expiration dates registered for Lot ....." error message when you post a reclassification journal to change the expiration date in the American version. |
Inventory |
COD 6500 COD 6501 |
NO - Norway
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
204943 |
If you export the SEPA CT file for a vendor whose payment is set to Remittance, and the Remittance Account is set to Foreign, the content of the Recipient Ref. Abroad field of the Payment Info page are not exported to the file in the Norwegian version. |
Cash Management |
COD 1221 |
RU - Russia
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
207729 |
The system does not allow consecutive filling of fields in the general journal for vendors or customers who use agreements in the Russian version. |
Finance |
TAB 81 |
|
209178 |
The system blocks the Sales Corrective Credit Memo and Get Corr. Doc. Lines process when the Enable Red Storno value is set to Yes and you use the Customs Declaration feature in the Russian version. |
Inventory |
COD 12422 |
Local regulatory features
RU - Russia
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
202215 |
Changes in VAT Declaration (2017) |
Financial Management |
TAB12405, TAB12411, REP12455, REP12456, REP12461, REP14962, REP14963, COD12423, PAG12413, PAG12443 |
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 2016 database:
|
Country |
Hotfix package |
|---|---|
|
AT - Austria |
Download the CU 18 NAV 2016 AT package |
|
AU - Australia |
Download the CU 18 NAV 2016 AU package |
|
BE - Belgium |
Download the CU 18 NAV 2016 BE package |
|
CH - Switzerland |
Download the CU 18 NAV 2016 CH package |
|
CZ- Czech |
Download the CU 18 NAV 2016 CZ package |
|
DE - Germany |
Download the CU 18 NAV 2016 DE package |
|
DK - Denmark |
Download the CU 18 NAV 2016 DK package |
|
ES - Spain |
Download the CU 18 NAV 2016 ES package |
|
FI - Finland |
Download the CU 18 NAV 2016 FI package |
|
FR - France |
Download the CU 18 NAV 2016 FR package |
|
IS - Iceland |
Download the CU 18 NAV 2016 IS package |
|
IT - Italy |
Download the CU 18 NAV 2016 IT package |
|
IN - India |
Download the CU 18 NAV 2016 IN package |
|
NA - North America |
Download the CU 18 NAV 2016 NA package |
|
NL - Netherlands |
Download the CU 18 NAV 2016 NL package |
|
NO - Norway |
Download the CU 18 NAV 2016 NO package |
|
NZ - New Zealand |
Download the CU 18 NAV 2016 NZ package |
|
RU - Russia |
Download the CU 18 NAV 2016 RU package |
|
SE - Sweden |
Download the CU 18 NAV 2016 SE package |
|
UK - United Kingdom |
Download the CU 18 NAV 2016 UK package |
|
All other countries |
Download the CU 18 NAV 2016 W1 package |
How to install a Microsoft Dynamics NAV 2016 cumulative update
See How to install a Microsoft Dynamics NAV 2016 cumulative update.
Prerequisites
You must have Microsoft Dynamics NAV 2016 installed to apply this hotfix.
More Information
See more information about software update terminology and Microsoft Dynamics NAV 2016.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
