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

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 - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.