This article applies to Microsoft Dynamics NAV 2013 R2 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 2013 R2, 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.
Note Implementing this cumulative update will require a database conversion unless you have already implemented cumulative update 5.
Licenses versioning
Microsoft Dynamics NAV 2013 R2 cumulative updates and license key versioning:
-
Microsoft Dynamics NAV 2013 R2 license keys are backward compatible with Microsoft Dynamics NAV 2013 instances.
-
Microsoft Dynamics NAV 2013 license keys may not be used with Microsoft Dynamics NAV 2013 R2 instances. Microsoft Dynamics NAV 2013 license keys will not work with Microsoft Dynamics NAV 2013 R2 CU10 (or later) instances.
-
Microsoft Dynamics NAV 2013 and Microsoft Dynamics NAV 2013 R2 license keys are not forward compatible with Microsoft Dynamics NAV 2015 instances.
More details is made available in the October 2014 release of the Microsoft Dynamics Perpetual Licensing Guide.
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 2013 R2, see released cumulative updates for Microsoft Dynamics NAV 2013 R2. For a complete list of all hotfixes released in cumulative updates for Microsoft Dynamics NAV 2013 R2, view the following CustomerSource and PartnerSource pages:
CustomerSource
Overview of Released Application Hotfixes for Microsoft Dynamics NAV 2013 R2
Overview of Released Platform Hotfixes for Microsoft Dynamics NAV 2013 R2
PartnerSource
Overview of Released Application Hotfixes for Microsoft Dynamics NAV 2013 R2
Overview of Released Platform Hotfixes for Microsoft Dynamics NAV 2013 R2Cumulative updates are intended for new and existing customers who are running Microsoft Dynamics NAV 2013 R2.
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
Note You may have to compile the objects in your database after you apply this hotfix.
|
ID |
Title |
|---|---|
|
378763 |
Removing and re-creating a ribbon group removes captions. |
|
378934 |
The Restore Defaults option that is used when you customize the Role Center page also resets the navigation pane. |
|
377334 |
The Dynamics NAV windows client fails to connect after failover when you use a SQL Server Always On High Availability cluster unless the NST has been restarted. |
|
378056 |
The Debugger stops when it is triggered after CurrReport.SKIP. |
|
378149 |
Import navdata cmdlet fails. |
|
379212 |
Add new methods to Dynamics NAV OpenXml add-in(s). |
|
379168 |
The new Activity buttons cannot be fully removed from the Navigation pane in the Windows client unless you choose the Restore Defaults action. |
|
379047 |
Excel add-in(s) crashes Excel when the server is limited during export to Excel. |
Application hotfixes
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
378862 |
No empty-element tags should be exported for SEPA according to ISO20022 rules. |
Cash Management |
XML 1000 XML 1010 |
|
379017 |
"SWIFT Code must have a value in Bank Account: No.=XXX. It cannot be zero or empty." error message when you try to export a SEPA file and you do not inform the SWIFT code in the Spanish version. |
Cash Management |
COD 1221 COD 1223 COD 1230 TAB 1226 |
|
379086 |
The Start balance (LCY) field on the Bank Acc. - Detail Trial Balance report is not shown. |
Cash Management |
REP 1404 |
|
378550 |
A wrong G/L account is used when you unapply a payment that has been posted with a payment discount, payment discount tolerance, or payment tolerance with a low amount. |
Finance |
COD 12 |
|
378652 |
The Recurring Journal page allows posting of lines that have already expired. |
Finance |
COD 13 |
|
379114 |
Auto transfer from G/L leads to double cost ledger entries. |
Finance |
COD 1105 |
|
378847 |
Quantity picked is not updated correctly after you undo an assembly order. |
Inventory |
COD 900 |
|
378650 |
The remaining quantity for a production order component is negative when it is consumed with no expected quantity. |
Manufacturing |
COD 22 |
|
378720 |
Assembly orders are duplicated when you change the customer in a sales order that has assembly-to-order items. |
Manufacturing |
TAB 36 TAB 904 |
|
378850 |
The Expected Capacity Need field is not properly calculated when you manually validate a production order routing line. |
Manufacturing |
TAB 5409 |
|
379075 |
The remaining quantity of a production order component is negative when it is consumed with no expected quantity and the quantity per is revalidated. |
Manufacturing |
TAB 5407 |
|
378530 |
A purchase or sales order with a line type of Item, a blank No. field, and a description can be posted as a text line on an invoice but the posted invoice cannot be copied to another document with the Copy Document function. |
Sales |
COD 80 COD 90 TAB 111 TAB 113 TAB 115 TAB 121 TAB 123 TAB 125 TAB 6651 TAB 6661 |
|
379031 |
Invoices within the grace period are not suggested in reminders. |
Sales |
COD 392 |
|
378970 |
"An attempt was made to change an old version of a Sales Header record. The record should first be reread from the database. This is a programming error" error message when you create a sales invoice through the Get Shipment Lines function. |
Sales |
COD 60 COD 70 TAB 111 TAB 121 |
|
379210 |
The Invoice Post Buffer table is not temporary when you post from a service order although it is temporary when you post from purchase and sales orders. |
Service |
COD 5988 |
Local application hotfixes
APAC
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
378883 |
The Invoice check box on the sales order header shows a wrong value in the APAC version. |
Sales |
COD 80 |
CZ- Czech
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
379178 |
Modification selection of banks or cash desks in the Czech version. |
Cash Management |
PAG 11745 PAG 370 PAG 371 TAB 11705 TAB 11707 TAB 11709 TAB 11711 TAB 11731 TAB 11736 TAB 270 |
|
379176 |
The Cash Desk Book and Cash Desk Account Book reports ignore the permissions for Cash Desk No. field and show all the information even if the field is not filled in in the Czech version. |
Finance |
REP 11740 REP 11741 REP 11742 |
|
379182 |
Incorrect message in the Advance Letters function when you use the Post Refund and Close Ad. Letter options in the Czech version. |
Prepayments |
COD 12 COD 31000 COD 31020 REP 11700 |
|
378860 |
The Sales Adv. Letter Statistic – VAT (LCY) field should be editable in the Czech version. |
Prepayments |
PAG 31004 |
|
379250 |
The VAT Control Report - Suggest Lines function merges VAT Entries in the Czech version. |
VAT/Sales Tax/Intrastat |
COD 31100 |
ES - Spain
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
379197 |
Wrong ledger entries are created after you unapply a payment that applies both the bill and the invoice when the invoice has been posted before the bill in the Spanish version. |
Finance |
COD 12 |
|
379144 |
"The file contains too much lines. The file contains 1002 lines and the maximum is 1000 lines" error message on the Tax Authorities web site if you try to upload an Intrastat file that is exported from Dynamics NAV with more than 1000 lines in the Spanish version. |
VAT/Sales Tax/Intrastat |
REP 593 |
|
378998 |
The VAT Registration No. field is incorrectly exported for EU customers and vendors in the 349 Declaration report if it already contains the country/region code in the Spanish version. |
VAT/Sales Tax/Intrastat |
REP 10710 TAB 9 |
IT- Italy
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
379081 |
No empty-element tags should be exported for SEPA according to ISO20022 rules in CBI Payment Request.00.04.00 XMLport in the Italian version. |
Cash Management |
XML 12100 |
|
378794 |
The exported Withholding Tax file should contain the withholding tax amounts in the AU001009 field and not in the AU001010 field in the Italian version. |
Purchase |
COD 12132 |
|
378866 |
The VAT Exemption Register report does not show any information in the Italian language in the Italian version. |
VAT/Sales Tax/Intrastat |
REP 12181 |
|
378904 |
If a foreign vendor has a tax representative set and when you post a purchase invoice, the VAT registration number that is used in the VAT Entry should be the one from the tax representative and not the one from the vendor in the Italian version. |
VAT/Sales Tax/Intrastat |
REP 12120 |
|
378693 |
The Communicazione Polivalente files should respect the limits established by the law of 40000 lines and 5MB in the Italian version. |
VAT/Sales Tax/Intrastat |
COD 12131 COD 12133 |
RU - Russia
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
378855 |
The Ingoing Cash Order page cannot be printed from a posted record when you use a manual check payment in the Russian version. |
Finance |
COD 12 |
Local regulatory features
ES- Spain
|
ID |
Title |
Functional area |
Changed objects |
|---|---|---|---|
|
166312 |
Changes in reporting delayed payments of commercial transactions for Microsoft Dynamics NAV 2013 R2 for Spain. |
Financial Management |
REP10748 |
Workaround
OData Filtering
If your solution uses OData web services with a combination of filters on $orderBy desc and $top, this results in errors in Dynamics NAV 2015 Cumulative Update 13. To avoid this error, add the following entry to the CustomSettings.config file for the Dynamics NAV Server instance:
<add key="EnableODataStrictFiltering" value="false"/>
This disables support for complex filters.
Resolution
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 2013 R2 database:
|
Country |
Hotfix package |
|---|---|
|
AT - Austria |
Download the ATKB3157488 package |
|
AU - Australia |
Download the AUKB3157488 package |
|
BE - Belgium |
Download the BEKB3157488 package |
|
CH - Switzerland |
Download the CHKB3157488 package |
|
CZ - Czech Republic |
Download the CZKB3157488 package |
|
DE - Germany |
Download the DEKB3157488 package |
|
DK - Denmark |
Download the DKKB3157488 package |
|
ES - Spain |
Download the ESKB3157488 package |
|
FI - Finland |
Download the FIKB3157488 package |
|
FR - France |
Download the FRKB3157488 package |
|
IS - Iceland |
Download the ISKB3157488 package |
|
IT - Italy |
Download the ITKB3157488 package |
|
NA - North America |
Download the NAKB3157488 package |
|
NL - Netherlands |
Download the NLKB3157488 package |
|
NO - Norway |
Download the NOKB3157488 package |
|
NZ - New Zealand |
Download the NZKB3157488 package |
|
RU - Russia |
Download the RUKB3157488 package |
|
SE - Sweden |
Download the SEKB3157488 package |
|
UK - United Kingdom |
Download the GBKB3157488 package |
|
All other countries |
Download the W1KB3157488 package |
How to install a Microsoft Dynamics NAV 2013 R2 cumulative update
See how to install a Microsoft Dynamics NAV 2013 cumulative update.
Prerequisites
You must have Microsoft Dynamics NAV 2013 R2 installed to apply this hotfix.
More Information
See more information about software update terminology and Microsoft Dynamics NAV 2013 R2.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
