Skip to main content

NAV 2013 R2 - Cumulative Update 23 Released.

Hi all,

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

Title - Cumulative Update 23 for Microsoft Dynamics NAV 2013 R2


Build No. - 42610


Release Date - Sep, 2015


Local Version Included - AU, AT, BE, CH, CZ, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, SE, RU, UK

Download Link

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


Platform Issues Resolved in the Cumulative Update are -

-----------------------------------------------------------------------------------------------------------
ID
Title
375612
It is impossible to convert a database to version 2015.
375589
Web Service calls return misleading status.
375358
If you change a value that is used in the CaptionClass functionality, the change is not reflected until you restart the client.
375670
The development environment appears blurred on high-DPI displays.
375648
"The filter "@Change Log Setup (Table)" is not valid for the Name field on the Object table. Did not expect a '('" error message when you use the EVALUATE function.
375726
Excel add-in with ACS and WAN access.
375676
The RoleTailored client crashes when a modal page is open in the background.
375567
The Export to Excel function does not respect the HideValue property.
375734
"Server page is not open" error message when closing a page.
375770
Scrolling in the development environment does not work properly in Windows 10.
375766
Some tenant operations do not work in Windows.
375768
The development environment hangs in Windows 10 when coming out of hibernation or sleep.
375772
The Update-NavApplicationObject PowerShell commandlet fails in Windows 10.
-----------------------------------------------------------------------------------------------------------

For information about previous Update Rollup / Cumulative update released for Microsoft Dynamics NAV 2013, NAV 2013 R2 & NAV 2015 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    ---------------------------

RTC Report It is not possible to instantiate the Visual Studio bridge.

Hi all, As a Navision developers I have Multiple Versions of Navision running in single Machine. As discussed Earlier in the post how to run multiple Version of RTC in single machine. So my machine have following details for RTC Versions - NAV 2009 R2    - is installed. NAV 2009 SP1  - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 SP1 IN\ NAV 2009         - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 IN\ This approach has been working great for execution of Classic and RTC Clients. However, after installing Dynamics NAV 2009 R2, if i tried to view the Layout for an NAV 2009 SP1 Report i was getting the following error: ---------------------------  Microsoft Dynamics NAV Classic  ---------------------------  It is not possible to instantiate  the Visual Studio bridge.  ---------------------------  OK    --------------------------- After searchi...

NAV 2013 R2 - Cumulative update 12 Released.

Hi all, Please find below the details of  Cumulative Update 12 released for Microsoft Dynamics NAV 2013 R2. Title - Cumulative Update 12 for Microsoft Dynamics NAV 2013 R2 Build No. - 38053 Release Date - October, 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.