The components needed to upgrade data directly from Microsoft Dynamics NAV 2009 R2 to Microsoft Dynamics NAV 2013 R2 are now available for download.
Download the upgrade toolkit from PartnerSource or from CustomerSource.
In order to use the toolkit to upgrade data from Microsoft Dynamics 2009 R2 or Microsoft Dynamics NAV 2009 SP1, you will also need the Microsoft Dynamics NAV 2013 development environment and Microsoft Dynamics NAV 2013 R2.
n the RoleTailored client, operations such as RENAME and COPY fail if the destination for the file operation is not on the computer running Microsoft Dynamics NAV Server. One solution is to configure Microsoft Dynamics NAV Server to delegate on behalf of the RoleTailored client as described in this topic.
We are happy to announce compatibility between Microsoft Office 2013 and the following versions of Microsoft Dynamics NAV:
•Microsoft Dynamics NAV 2009 R2
•Microsoft Dynamics NAV 2013
Today, I tried to export a fob file from a 2009R2 but strangely I got the following error:
NAV 2009
Security for Web Services (WS) in NAV 2009 is managed by using Windows Authentication.
This is the reason access to NAV 2009 Web Services requires the user to log into a domain and be a valid Windows Login in NAV.
As promised in the blog entry i will list down some common known things that we need to take care while estimating & developing RTC Reports in 2009 Versions.
* These are my faced issues and their resolutions, you may not agree with all these. If that will be case i would suggest you to share same with others.
One of the most interested change in Nav 6 . the closing period for costing will include item ledger entries and value entries . So we will not have any differences related to posting date between value entries and item entries.