First, I might as well be up-front: the basic process of converting Dynamics NAV classic reports to RDLC layouts is clunky, time-consuming, and somewhat error-prone. This is caused in large part because you have to repeatedly work back and forth between the NAV classic report designer and the Visual Studio report designer (if you don’t understand why, see Converting Dynamics NAV Classic Reports To RDLC – Part 1).
Garbage collector in NAV 2009 is set to DISABLED by default. Do not ask me what does it mean and why it is disabled. I do not know. Regardless the value DISABLED, this settings just means that Workstation mode is used for GC
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:
Vertalen
