As Microsoft has already announced, Dynamics NAV 2013 will run only RDLC reports and will discontinue the use of NAV classic reports. This means all customers upgrading to NAV 2013 will have to convert their classic reports to the RDLC format.
This early draft of NAV 2013 RDLC reporting guidelines was placed on the Microsoft Dynamics NAV Team Blog earlier in the year. As the original author notes, they’re essentially “a checklist at this point, which you can go through one by one. For example, it is a good practice to define the Page Width, Page Height, and margins in the Report Properties before starting to design your report.”
In Dynamics NAV 2009 Service Pack 1 also later Builds on SQL Server 2005, SQL Server 2008 also SQL Server 2008 R2, when a new user is created and synchronised sometimes following error is thrown.
And almost on cue, Microsoft has published an entire set of Learning Plans aimed at partners to prepare for Microsoft Dynamics NAV 2013!
Curious about NAV 2013′s new features? Microsoft has released a NAV 2013 fact sheet for end-use customers. New features include:
Some people asked me to update the original blog posting Outlook Synchronization and baseline implementation for Dynamics NAV 5.0 SP1 and Dynamics NAV 2009 SP1 since Microsoft did release Dynamics NAV 2009 R2. Let’s take the opportunity to mention latest news regarding Outlook Synchronization solution in a complete new blog, specifically written for Dynamics NAV 2009 R2.
Running NAS with Job Queue will start a timer to process Job Queue Entries every two seconds. In the original code the Timer is disabled before checking the Job Queue Entries and then enabled again after the process. If NAS will not be able to read the Job Queue Entry then the function will exit without enabling the Timer and nothing will be processed.
Vertalen
