Cumulative Update 28 for Microsoft Dynamics NAV 2016 (Build 49968)

Applies to: Dynamics NAV 2016

This article applies to Microsoft Dynamics NAV 2016 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 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
231828 Problems with auto-scrolling up in the Web client when you enter lines in document orders, purchase order lines, or sales order lines.
251402 Menu items are lost when you add them to a user with specific permissions.
253226 The client crashes if you change a copied permission set.
254589 Dynamics 365 (CRM) SDK in the cmdlets requires TLS 1.2 to be set.
254647 "Cannot assign a scope id. The maximum number of methods for 8" error message is displayed.
255511 NAV APP for Android-based tablet and phone blanks out all fields when you edit a record.
255726 It is not possible to remove an added element from the navigation pane.
256166 Upgrade does not set permissions on System Tables, which blocks synchronization.

Application hotfixes

ID Title Functional area Changed objects
235046 If you print a check with the One Check per Vendor per Document No. option set to True, the general journal batch workflow causes an additional restriction when posting. Administration REP 1401
251569 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
253383 The No. of Records field on the Copy Company Data page is always 0. Administration PAG 8639
254321 If you use the Adjust Exchange Rate function for subsequent years, an incorrect G/L account is used. Finance REP 595
254728 The G/L Register report does not print the journal numbers correctly if they are longer than 4 digits. Finance REP 3
255469 The Additional Fee and Interest Amount fields are displayed oddly in a printed Reminder report. Finance REP 117
253531 Update of dialog stops when you run an Adjust Cost - Item Entries batch job over midnight. Inventory COD 5811 COD 5895 REP 188 REP 189 REP 190 REP 191 REP 192 REP 193 REP 5186 REP 5198 REP 94
254339 Availability check warning is not raised when you change a shipment date related to an assembly item to an earlier date than the date when a stock is available. Inventory COD 311 COD 5790 TAB 901
252306 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
252705 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
252197 "The length of the string is Value1, but it must be less than or equal to Value2 characters" error message when you resume an interaction if a salesperson code has more than 7 characters. Marketing COD 5051 COD 5054 COD 5055 COD 5057 COD 5058 COD 5064 COD 5940 TAB 110 TAB 112 TAB 114 TAB 120 TAB 122 TAB 124 TAB 13 TAB 18 TAB 21 TAB 23 TAB 25 TAB 270 TAB 271 TAB 281 TAB 36 TAB 38 TAB 382 TAB 454 TAB 5050 TAB 5065 TAB 5071 TAB 5072 TAB 5076 TAB 5077 TAB 5079 TAB 5080 TAB 5083 TAB 5084 TAB 5092 TAB 5093 TAB 5096 TAB 5102 TAB 5107 TAB 5109 TAB 5200 TAB 5802 TAB 5900 TAB 5965 TAB 5970 TAB 5990 TAB 5992 TAB 5994 TAB 6650 TAB 6660 TAB 751 TAB 753 TAB 81 TAB 83 TAB 91 TAB 28071 TAB 28073 TAB 28075 TAB 28077 TAB 2000001 TAB 32 TAB 11730 TAB 11731 TAB 11735 TAB 11736 TAB 31000 TAB 31020 TAB 31050 TAB 31057 TAB 16587 TAB 11000000 TAB 11401 TAB 15000004 TAB 12403 TAB 12450 TAB 12451 TAB 12452 TAB 12453 TAB 12454 TAB 12455 TAB 12470 TAB 12471 TAB 14901 TAB 14902 TAB 14927 TAB 11200
253087 "There is no customer related to contact ContactName, which is specified in the opportunity" error message when you run the Assign Sales Quote function from the Opportunity page. Marketing PAG 5124 TAB 5092
254152 "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
253142 "Quantity (Base) is not sufficient to complete this action" error message when you post a warehouse shipment partially for a transfer order with lot tracked items. Warehouse COD 5704 COD 99000836

Local application hotfixes

CH - Switzerland
ID Title Functional area Changed objects
254295 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
254501 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
254630 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
254674 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
255829 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
256322 Differences in the application behavior in a general journal and in the cash documents in the Czech version. Finance TAB 81 TAB 11731
DACH
ID Title Functional area Changed objects
255063 "Total Weight must have a value in Intrastat Jnl. Line" error message when you use the Create File function in the DACH version. Finance REP 11014
ES - Spain
ID Title Functional area Changed objects
251156 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
253771 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
254497 "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 except posted payment orders in Cartera in the Spanish version. Finance COD 7000004
254614 "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
255490 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
252252 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
252593 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
252600 If the sales or purchase credit memos are posted by using their own VAT posting setup, the posted VAT settlement entry is included in the wrong total of the VAT settlement communication in the Italian version. VAT/Sales Tax/Intrastat COD 12151 TAB 325
253534 The un-deductible part of purchase invoices and the 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
NA - North America
ID Title Functional area Changed objects
254460 If check stub reports 10401 or 10411 are printed with the One Check per Vendor per Document No. option set to True, the general journal batch workflow causes an additional restriction when posting in the North American version. Administration REP 10401 REP 10411
NO - Norway
ID Title Functional area Changed objects
255477 You notice that captions on the Sales Shipment report are badly formatted causing overlapping and misplaced fields in the Norwegian version. Finance REP 208
UK - United Kingdom
ID Title Functional area Changed objects
254499 The Day Book Vendor Ledger Entry report shows an incorrect Total Actual Amounts field when the Payment Discount Rcd. Field is filled in the British version. Purchase REP 10535
RU - Russia
ID Title Functional area Changed objects
252751 Incorrect print form is used for the FA Phys. Inventory INV-1 report in the Russian version. Finance REP 12486
253908 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
253909 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

Resolution


How to obtain the Microsoft Dynamics NAV update files

This update is available for manual download and installation from the Microsoft Download Center.

Download Cumulative update CU 28 for Microsoft Dynamics NAV 2016

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 28 NAV 2016 AT package
AU - Australia Download the CU 28 NAV 2016 AU package
BE - Belgium Download the CU 28 NAV 2016 BE package
CH - Switzerland Download the CU 28 NAV 2016 CH package
CZ- Czech Download the CU 28 NAV 2016 CZ package
DE - Germany Download the CU 28 NAV 2016 DE package
DK - Denmark Download the CU 28 NAV 2016 DK package
ES - Spain Download the CU 28 NAV 2016 ES package
FI - Finland Download the CU 28 NAV 2016 FI package
FR - France Download the CU 28 NAV 2016 FR package
IS - Iceland Download the CU 28 NAV 2016 IS package
IT - Italy Download the CU 28 NAV 2016 IT package
IN - India Download the CU 28 NAV 2016 IN package
NA - North America Download the CU 28 NAV 2016 NA package
NL - Netherlands Download the CU 28 NAV 2016 NL package
NO - Norway Download the CU 28 NAV 2016 NO package
NZ - New Zealand Download the CU 28 NAV 2016 NZ package
RU - Russia Download the CU 28 NAV 2016 RU package
SE - Sweden Download the CU 28 NAV 2016 SE package
UK - United Kingdom Download the CU 28 NAV 2016 UK package
All other countries Download the CU 28 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


Status


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