Cumulative Update 34 for Microsoft Dynamics NAV 2017 (Build 29998)

Applies To
Dynamics NAV 2017

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
309785 The Job Queue does not run when it is started from a user from a trusted domain.
317398 The IMPORTFILE function (MediaSet) does not work with the CHANGECOMPANY function.

Application hotfixes

ID Title Functional Area Changed Objects
319005 There are too many parameters when you print a report. Administration COD 8800
322989 "The Config. Package Data does not exists." error message is displayed if you try to import new records in the Cash Flow Manual Expense table. Administration COD 8614
317565 When you partially apply multiple invoices to a credit memo, the print check displays incorrect lines. Finance REP 1401
319159 "Arithmetic operation resulted in an overflow" error message is displayed when you try to transfer the G/L entries to the Cost Accounting. Finance COD 1105
320322 It is possible to post an invoice/credit memo without specifying a Gen. Product Posting Group table. Finance COD 11
318559 An incorrect drill-down in the fixed assets statistics. Fixed Assets TAB 5612
319363 Incorrect value of Book value after a disposal on the fixed assets statistics. Fixed Assets PAG 5602
316492 A performance issue with high volumes of the serial numbers in the WMS location. Inventory COD 7307
318318 An outbound entry is not assigned the latest valuation date of the associated inbound item ledger entries in a backdated transfer scenario, which causes an inbound entry having a later valuation date than the posting date. Inventory COD 22
320881 "When selecting multiple Purchase Invoice Approvals, only one gets approved" error message is displayed. Purchase COD 1535
321938 A reject approval request creates double notification entries. Sales COD 1535
316306 Only the first expired lot is suggested on the Whse. Pick page when you have a pick according to the FEFO option after the lot was reclassified from the shipment bin and units with the same lot have been received. Warehouse COD 7312
317711 A performance problem is displayed when you run the Calculate Whse. Adjustment function within the item journal because it runs through every warehouse entry for an item or adjustment bin every time when it looks for adjustments. Warehouse PAG 9126 QUE 7300 REP 7315
318074 The warehouse employee with no location setup manages to update the Qty. to Ship field in all locations in the Warehouse Shipment Line table by running the Autofill Qty. to Handle field on the Warehouse Shipment page. Warehouse PAG 5769 PAG 5771 PAG 5780 PAG 7336

Local application hotfixes

BE-Belgium

ID Title Functional Area Changed Objects
322285 If you post a service invoice, the Enterprise Number field in the VAT Entry table is not filled in the Belgian version. Finance TAB 81

CZ- Czech

ID Title Functional Area Changed Objects
322925 If you choose the Bad Receivable option in the Vat Control Report, the export is incorrect in the Czech version. VAT/Sales Tax/Intrastat XML 31100
322855 The original document VAT date is missing on the sales credit memo in the Czech version. VAT/Sales Tax/Intrastat COD 31100 COD 80 PAG 44 TAB 36 TAB 49 TAB 81

FR-France

ID Title Functional Area Changed Objects
322860 Incorrect formatting of numbers in the Fixed Asset - Projected Value (Derogatory) report in the French version. Fixed Assets REP 10886

NL-Netherlands

ID Title Functional Area Changed Objects
315824 The reconcile vendor ledger entries functionality does not work as expected in the Dutch version. Purchase COD 11000006

NO – Norway

ID Title Functional Area Changed Objects
316300 If you use the remittance suggestion and the credit memos also get suggested, but they cannot be processed in the Norwegian version. Cash Management REP 15000001

Local regulatory features

ID Title Functional Area Changed Objects
320824 100% prepayment with partial shipments leads to incorrect invoice rounding in some scenarios. Financial Management COD 80 COD 90 TAB 37 TAB 39

ES-Spain

ID Title Functional Area Changed Objects
316804 The SII module has been updated in July 2019 in the Spanish version. Financial Management COD 10750

NA-North America

ID Title Functional Area Changed Objects
320132 The .XML file created for a posted sales invoice with CFDI Relation = 04 Substitution of previous CFDI should include Folio No. & CDFI related information of the previous invoice and the credit memo when you use the Mexico Electronic Invoicing module in the North American version. Financial Management COD 10145 COD 5980 COD 80 PAG 132 PAG 143 PAG 27006 PAG 42 PAG 43 PAG 5900 PAG 5933 PAG 5977 PAG 5978 PAG 9301 PAG 9305 PAG 9318 PAG 9319 TAB 27006

UK - United Kingdom

ID Title Functional Area Changed Objects
322444 Make the Tax Digital update (redesign test API) in the British version. Financial Management COD 1140 COD 1297 COD 10530 COD 10538 COD 10541 PAG 743 TAB 743

      

Resolution

How to obtain the Microsoft Dynamics NAV update files

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

Cumulative update CU 34 for Microsoft Dynamics NAV 2017

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