Skip to main content

News From Microsoft Desk...

Hi All,

While Browsing Partner Source and Microsoft Team Blog i found out some interesting link and thought of sharing them.


Below are some updates from Microsoft on Team Blog -



1. Filter values specified on a request page for a report are not saved by the Web Client

This article says that its a limitation of web client that the values are not saved in Report Request Page as it happens in Role Tailored Client. The Link provides the Updated Limitation of Web Client in NAV 2013 R2.

Read Complete Article on Microsoft Team Blog.

2. Temporary Issue with Single Sign-On for Office 365

On August 13, the Single Sign-On (SSO) protocol that is used in Microsoft Azure Active Directory (Azure AD) was updated, which unfortunately caused the SSO implementation in Microsoft Dynamics NAV 2013 R2 to fail temporarily. As a result, users could not log into Microsoft Dynamics NAV using their Office 365 credentials.The problem was resolved. The new design will be part of the Cumulative Update 11 for Microsoft Dynamics NAV 2013 R2. 

Read Complete Article on Microsoft Team Blog.

3. Compatibility with SQL Server 2014

Microsoft Dynamics NAV 2013, Microsoft Dynamics NAV 2013 R2, and Microsoft Dynamics NAV 2009 R2 are compatible with SQL Server 2014!

Please note that this applies to the following editions of Microsoft SQL Server:
Standard Edition

Enterprise Edition

Read Complete Article on Microsoft Team Blog.

4. Announcement about Tax Updates Dependent on Cumulative Updates (CU) in Microsoft Dynamics NAV

Effective July 15, 2014, all Tax Updates (commonly referred to as Regulatory Features) will be developed based on the latest Cumulative Updates as their baseline instead of the current practice of basing the same on an RTM release.

Effective October 1, 2014, all Tax Updates for Microsoft Dynamics NAV will be developed on CU and will be released only through Cumulative Updates. Microsoft Dynamics NAV will no longer release individual .fob or text files for a Tax Update.

Read Complete Article on Microsoft Team Blog.

Hope you find the information useful.

Regards,
Saurav Dhyani
www.sauravdhyani.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.