Skip to main content

NAV 2013 R2 - Cumulative update 10 Released.

Hi all,

Please find below the details of  Cumulative Update 10 released for Microsoft Dynamics NAV 2013 R2.

Title - Cumulative Update 10 for Microsoft Dynamics NAV 2013 R2


Build No. - 37534
Release Date - August, 2014
Local Version Included - AU, AT, BE, CH, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, SE, UK, RU


Download Link



Note: Implementing this cumulative update will require a database conversion unless you have already implemented update rollup 5.



License Versioning -

Microsoft Dynamics NAV 2013 R2 Cumulative Update 10 introduces license key versioning to Microsoft Dynamics NAV. Observe the following specifications:

Microsoft Dynamics NAV 2013 R2 license keys will continue to be backward compatible with Microsoft Dynamics NAV 2013 instances.
Microsoft Dynamics NAV 2013 license keys cannot not be used with Microsoft Dynamics NAV 2013 R2 instances. Accordingly, newly issued 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.

Platform Issues Resolved in the Cumulative Update are -
------------------------------------------------------------------------------------------------------

  • The Show as Chart function crashes the client if you run it from the Job Ledger Entries page for a specific job.
  • Customizing the ribbon permanently hides an action.
  • The cursor jumps to a random record after validate error.
  • Delete in tree view deletes non-selected records.
  • System.IndexOutOfRangeException when running multiple NAV Servers.
  • The client crashes with a filter exception on a FactBox.
  • The web client shows error and cannot be closed.
  • If you try to add a record via OData using a page that does not include all of the primary key fields, you will encounter an error message referring to missing values.
  • Export to excel using an add-in fails.
  • If you drill down on a FlowField value, you may not see the expected underlying records.
  • Cannot export/import upgraded database.
  • When you use the FORMAT() function, the results can be different compared to previous release as it does not consider decimal places property correctly if these are defined at table level.
  • When you export to Excel using a PLLP language release, the language changes back to English on a client OS.
  • Cannot modify system tables by import objects from command prompt.
  • Cannot import objects.
  • When you import a fob file in builds > 7.1.36703, a list of errors is no longer shown.
  • Integration Management does not support multitenancy.
  • The web client crashes application pool when specifying a non-existing tenant ID.
  • QuickEntry does not work when a field is also in IndentationControls.
  • The license should check that it is compatible with NAV 2013 R2.
  • The program version for NAV 2013 R2 is incorrect.
  • TAB and ENTER give different results when running code from the OnValidate() trigger.
  • "Microsoft Dynamics NAV internal-only exception used to implement control statements Skip, Break, and Quit in Reports and XMLport." error message from NAS Services.
  • The win client crashes if you use Filter as You Type and you have set the display size to 125% in the Control Panel.
  • FlowFields with mixed SQL Data Type work in an unexpected way.
  • ISEMPTY leaks memory.
  • Problems using new database with imported application objects.
  • NAV crashes with server-side dotnet variables.
  • Bad performance when the lookup page contains a long text column and it is used as default filter.
  • Move disabled fields from About This Page to a separate FactBox.
  • SETSELECTIONFILTER does not work when only one line is marked.
  • The Delete function returns a wrong reference after a previous deletion was canceled, potentially causing the wrong entries to be deleted without notice.
  • Integer dataitem breaks security filter.
  • "Queries between data sources are not supported" error message from query object when used with Access Control and Permission tables (Data per Company = No).
  • If a security filter is applied to a permission set then all users experience strange permission errors even though the security filter was applied to their permission set.

-------------------------------------------------------------------------------------------------------

For information about previous Update Rollup / Cumulative update released for Microsoft Dynamics NAV 2013 Please Navigate to Hotfix Label or follow the Link.

All These links required valid Partner Source / Customer Source Login...

Regards,
Saurav Dhyani
saurav-nav.blogspot.com

Comments

Popular posts from this blog

VIEW SERVER STATE permission on SQL Server?

Hi all, Sometime While trying to Login into a database we face an error message as shown below. --------------------------- Microsoft Dynamics NAV Classic --------------------------- You cannot start Microsoft Dynamics NAV Classic because you do not have the VIEW SERVER STATE permission on SQL Server. Contact your system administrator. --------------------------- OK    ---------------------------

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing -