Cumulative Update 37 for Microsoft Dynamics NAV 2015 (Build 49425)

Applies to: Microsoft Dynamics NAV 2015

This article applies to Microsoft Dynamics NAV 2015 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 2015, including hotfixes and regulatory features that were released in previous cumulative updates.

Note You must convert the database if you are upgrading to this cumulative update from a cumulative update earlier than cumulative update 9 (build 41779). For more information, see Converting a Database in Help for Microsoft Dynamics NAV.

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 2015, see released cumulative updates for Microsoft Dynamics NAV 2015. Cumulative updates are intended for new and existing customers who are running Microsoft Dynamics NAV 2015.

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
230972 Excel Add-In Manifest deployment is broken since September CU for Localized versions.
231472 Exception NavNCLDotNetInvokeException appears.
223908 The progress indicator does not close and the page is not updated.
229801 The Request page that saves a GUID variable crashes the client.

Application hotfixes

ID Title Functional area Changed objects
229097 If you set the Dimension filter field on the Account Schedule Overview page and drill down on the values, the filter on the Drill Down page is incorrectly set if you use the asterisk (*). Finance PAG 120 PAG 490 REP 25
229966 Payment tolerance warning message is not displayed when you apply a payment in LCY to an invoice in FCY. Finance COD 226 COD 227 COD 426
230564 IC Partner OnDelete refers to the Customer No. field instead of the Vendor No. field. Finance TAB 413
230816 Error message "The value of ROUND parameter 2 is outside of the permitted range. The current value is: 0. The permitted range is: from 1 to 2.147.483.647" shows when you run the Calc. Regenerative Planning function on the Planning Worksheet page. Manufacturing COD 5431 REP 99001017
227907 The GetFirstBusUnit function has a return value of Code 10 on the G/L Budget Entries page. In this function, the return value is filled with table 120 Business Unit field 1 Code (Code 20). Marketing PAG 120 PAG 490 REP 25
228106 When you create a sales return order by using the Get Posted Document Lines to Reverse function and you choose the posted shipments, the system does not check if prices include VAT. Sales COD 6620
230268 A Service Charge G/L sales line is created on first sales line but not at the end of the document when the sales order is released. Sales COD 56 COD 57 COD 60 COD 66 COD 70
230306 Drop shipment data from the Purchase Order No. and Purchase Order Line No. columns in the Sales Order Line table are removed when you invoice sales order through a sales invoice document. Sales COD 80 TAB 37
229181 An error is displayed when you use the Split Line feature on a warehouse pick and using lot numbers with more than 15 lot numbers take and place lines. Warehouse PAG 5771 PAG 5780 PAG 7316 PAG 7376 PAG 7378 PAG 7383 TAB 5767
229915 Create Put-Away creates an empty record in the Bin Content table which is no longer removed later in the process if you set the bin code to blank. Warehouse COD 5760 COD 7307 COD 7313 REP 7305 TAB 5767
231617 You can't validate imported data for the From Bin Code and From Zone Code fields from the Warehouse Journal Line table by using the Rapid Start function. Warehouse TAB 7311

Local application hotfixes

CH - Switzerland
ID Title Functional area Changed objects
229463 Error message "Unknown swiss SEPA CT export payment type" shows if you try to use the Export Payments to File function for a foreign payment on the Payment Journal page in the Swiss version. Cash Management COD 11503 COD 1223 PAG 425 TAB 1226 TAB 288 XML 1000
229465 If you import a SEPA CAMT file into payment reconciliation journals, only the latest entry is applied automatically in the Swiss version. Cash Management COD 1240 COD 1248 TAB 1220
230200 "The Document Type must be Invoice" error message if you post a payment journal with the Reference No. field filled in the Swiss version. Cash Management COD 3010541
CZ- Czech
ID Title Functional area Changed objects
228746 EET Cash desk duplication in the Czech version. Cash Management COD 11735 COD 31121
228749 You can post a cash document with the resulting minus amount in the Czech version. Cash Management COD 11731
231731 When you delete a cash document, unlink payment to advance letter is not done in the Czech version. Cash Management TAB 11730
228651 The dimension in the GL entries record differs from the G/L Entry dimension record in the Czech version. Finance TAB 31051
229342 The Compensation field on the Customer Ledger Entries page is not filled in correctly if you post credits in the Czech version. Finance COD 11 COD 12 COD 31052 TAB 81
228668 Incorrect VAT date in the VAT entry on the Payment Discount page in the Czech version. Purchase COD 227
228719 Advance credit memo is printed incorrectly in the Czech version. Sales REP 31002
229210 Convert uppercase letters to lowercase for the Export VAT Control report in the Czech version. VAT/Sales Tax/Intrastat XML 31100
229365 VAT statement is exported incorrectly when you export total fields in the Czech version. VAT/Sales Tax/Intrastat XML 11762
DACH
ID Title Functional area Changed objects
229888 "You cannot post and apply general journal line %1, %2, %3 because the corresponding balance contains VAT" error message does not appear mistakenly in a certain scenario in the DACH version. Finance COD 13
DE - Germany
ID Title Functional area Changed objects
228429 The Place of Dispatcher field and the Place of Receiver field are not used anymore for company information in the German version. Finance PAG 1
ES - Spain
ID Title Functional area Changed objects
228994 The BaseImponible, CuotaSoportada and CuotaDeducible fields on SII xml fields are not calculated correctly on purchase credit memo with the Correction type set as blank in the Spanish version. Finance COD 10750
229398 If you set the EU Service field on the Vat Posting Setup page and export a sales invoice or a credit memo with the SII interface, lines with the No Sujeto type are in an incorrect section in the Spanish version. Finance COD 10750
229911 If you create sales or purchase credit memo and post lines with equivalence charge, the equivalence charge is calculated incorrectly if you have multiple lines in the document in the Spanish version. Finance COD 10750
230517 If you issue a sales credit memo with VAT exemption code for credit memos of type difference or empty, the Base Importable amount is positive in the Spanish version. Finance COD 10750 COD 10755
230522 Some fields in the initial upload of invoices are not filled correctly in the Spanish version. Finance COD 10750 COD 10755
FR - France
ID Title Functional area Changed objects
230008 At an attempt to create a SEPA vendor payment file using the Payment Slip feature in the FR database an error appears if the vendor invoice number has more than 20 characters in the French version. Cash Management TAB 10866
230512 SEPA vendor payment file cannot be validated successfully if the Summarize per vendor field is used and a certain number of invoices is applied in the French version. Cash Management XML 1000
IT - Italy
ID Title Functional area Changed objects
227749 The purchase invoices and purchase credit memos document number reported in the VAT report should correspond to the vendor invoice (or credit memo) external document number in the Italian version. Finance COD 12182 REP 12195 TAB 740
227754 If you export a VAT report DatiFAttura file and there are submitted reports in the system already, the exported file contains the all VAT reports data is archived in the database in the Italian version. Finance COD 12182 REP 12195 TAB 740
227759 The VAT report does not allow exporting the sale or purchase invoice if the customer or the version is classified as individual person and in the card is reported the fiscal code in the Italian version. Finance COD 12182 REP 12195 TAB 740
228116 The reverse charge VAT sale invoice entry has not to be included in the VAT report in the Italian version. Finance COD 12182 COD 12183 REP 12195
228468 Error message "Developer Message: The error message record is not temporary. Insert of error message aborted" shows when you try to release a VAT report in the Italian version. Finance COD 12182 COD 12183 REP 12195
228586 If you post non-deductible VAT purchase invoices, the VAT report proposes only the deductible base and amount part of the transaction in the Italian version. Finance COD 12182 COD 12183 REP 12195
229010 The Dati Fattura communication must be split in two files DTE (sales invoices/credit memos) DTR (Purchase invoices credit memos) in the Italian version. Finance COD 12182 COD 12183 REP 12195
229209 "00200 - Cannot find the declaration of element 'DatiFattura'. Line  2 - Column 31" error message is displayed by the tool of Agenzia delle Entrate when you try to upload the DatiFattura exported file in the Italian version. Finance COD 12182 COD 12183 REP 12195
229563 The Dati Fattura communication file name format is not compliant with the requirements in the Italian version. Finance COD 12182 COD 12183 REP 12195
229879 The DatiFattura communication file must not contain more than 1000 occurrences. The system should create as many files as are the total occurrences to be reported with the same file name in the Italian version. Finance COD 12182 REP 12195
229941 The split payment sale invoices are not correctly declared in the DatiFattura communication in the Italian version. Finance COD 12182 REP 12195
230046 The system gets an error message that is not correct when you insert the VAT registration number of a customer per vendor in the Italian version. Finance COD 12104
230052 The customers or vendors entries posted without VAT registration no. or/and fiscal code suggested in the VAT report are exported without any problem, the system does not get any error message in the Italian version. Finance COD 12182
NL - Netherlands
ID Title Functional area Changed objects
229822 REP 11000000 does not consider the currency amount rounding precision in the Dutch version. Cash Management REP 11000000
NO - Norway
ID Title Functional area Changed objects
232138 The File Export Errors FactBox field is missing on the Payment Journal page in the Norwegian version. Cash Management COD 10635 COD 10637
232149 An overflow error message ("The length of the string ...") that is related to the document number appears when you import the return file for a SEPA payment in the Norwegian version. Cash Management COD 10636
RU - Russia
ID Title Functional area Changed objects
226077 The Resp. Employees, Buy-from Vendor History FactBox, and Pstd. Invoices page displays incorrect result of drilldown in the Russian version. Finance PAG 9095

Local regulatory features

IT - Italy
ID Title Functional area Changed objects
232511 New setup field to control inclusion of VAT exempt entries on the VAT Settlement comms. report Financial Management COD12151 PAG472 PAG473 TAB325

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 37 for Microsoft Dynamics NAV 2015

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 2015 database:

Country Hotfix package
AT - Austria Download the CU 37 NAV 2015 AT package
AU - Australia Download the CU 37 NAV 2015 AU package
BE - Belgium Download the CU 37 NAV 2015 BE package
CH - Switzerland Download the CU 37 NAV 2015 CH package
CZ- Czech Download the CU 37 NAV 2015 CZ package
DE - Germany Download the CU 37 NAV 2015 DE package
DK - Denmark Download the CU 37 NAV 2015 DK package
ES - Spain Download the CU 37 NAV 2015 ES package
FI - Finland Download the CU 37 NAV 2015 FI package
FR - France Download the CU 37 NAV 2015 FR package
IS - Iceland Download the CU 37 NAV 2015 IS package
IT - Italy Download the CU 37 NAV 2015 IT package
NA - North America Download the CU 37 NAV 2015 NA package
NL - Netherlands Download the CU 37 NAV 2015 NL package
NO - Norway Download the CU 37 NAV 2015 NO package
NZ - New Zealand Download the CU 37 NAV 2015 NZ package
RU - Russia Download the CU 37 NAV 2015 RU package
SE - Sweden Download the CU 37 NAV 2015 SE package
UK - United Kingdom Download the CU 37 NAV 2015 UK package
All other countries Download the CU 37 NAV 2015 W1 package

How to install a Microsoft Dynamics NAV 2015 cumulative update

See How to install a Microsoft Dynamics NAV 2015 Cumulative Update .

Prerequisites

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

More Information


See more information about software update terminology and Microsoft Dynamics NAV 2015.

Upgrade Toolkit for Upgrading Data from Microsoft Dynamics NAV 2009 R2 or SP1 to Microsoft Dynamics NAV 2015

The cumulative update includes an upgrade toolkit for upgrading a Microsoft Dynamics NAV 2009 R2 or Microsoft Dynamics NAV 2009 SP1 database to Microsoft Dynamics NAV 2015. The upgrade toolkit includes several application objects in FOB files that simplify the upgrade process for those of you coming from Microsoft Dynamics NAV 2009 R2 or Microsoft Dynamics NAV 2009 SP1. For more information, see the attached whitepaper.

Status


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