Skip to main content

NAV 2013 R2 - Cumulative Update 26 Released.

Hi all,

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

Title - Cumulative Update 26 for Microsoft Dynamics NAV 2013 R2


Build No. - 43896


Release Date - Dec, 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
376644
Performance issues when ALStream.READTEXT(Text,[Length]) makes one MByte buffer if no optional length is specified.
376735
SETSELECTIONFILTER works incorrectly when you switch from a page to a subpage.
376803
OData returns incorrect recordsets when you use complicated filters.
359260
ODATA parameter $TOP returns incorrect datasets.
371512
|OData filtering does not work with pagination.
363406
When you use substringof as the filter expression in an OData query, only the subset of records as per the Max Page Size server setting are considered.
363138
Some filters do not work in OData queries.
363112
Unexpected behavior when you use $top with an OData query that includes multiple filters.
376388
Old version of Report Viewer 2012 on the Dynamics NAV DVD.
376674
The Dynamics NAV client and server crash when the code on the XML Port Request page is executed.
376653
In some cases, it is not possible to remove elements when you do customizations.
-----------------------------------------------------------------------------------------------------------

For information about previous Update Rollup / Cumulative update released for Microsoft Dynamics NAV 2013, NAV 2013 R2, NAV 2015 & NAV 2016 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 searching for the error i figured out the issue was due to - Design change in NA

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.