Some tips about NAV 2009 Form Transformation
I notice that (at least in Belgium) it's still quite a "hot topic" on how to handle NAV 2009 Forms and pages. Should we develop pages? Or should we develop forms, transform them and start from there? Or should we maintain a 100% form transformation to pages and never touch the page designer?
Well, my comments on this: it depends. It all comes down to the context. It all comes down to the customer's needs, the support you want to give … and your knowledge (probably the most important one). I have been diving into this lately and came across some interesting links, advice and such, which I wanted to share with you. Probably there is already a lot online about this … but hey … "repetitio mater studiorum est"
.
As you already know, there is a lot about developing in NAV 2009 on "Microsoft Dynamics NAV 2009 Developer and IT Pro Documentation". Also specifically things about NAV 2009 Form Transformation.
Here are a few tips.
Get familiar with the Core Application
It wouldn't make sense to transform to pages, to set up the TIF tool, while you're not familiar with the page types and other page-related stuff (taskpanes, actions, promotion of actions, … ). Here is a link that can help you with that.
Furthermore, learn how Microsoft dealt with certain difficulties. There are a number of occasions where Microsoft had to redesign a certain form. You can learn a lot from this. Check it out here. On this page, you can find a number of "how to's" as well (How to handle Matrix forms, how to handle journals, …).
Get familiar with the Form Transformation tool
What can you expect from the Transformation Tool? How can you debug it? How can you influence the transformation process? These are all stuff you have to know to efficiently use it. Therefore, get familiar with it's architecture.
Furthermore, the Form TransformationLog Output file is a very useful tool to see what is going on. First of all, you can get an impression on how much work a form transformation is going to be (export all forms, run the transformation and view the output), and it shows you what work exactly has to be done. Check out here for an explanation about the Log file.
Next, how to influence and work with the tool? There are a number of mapping rules, and you should get familiar with it. Here is the one and only starting point for you.
Get familiar with the most common troubleshoot examples
Here they are:
I'm sure a lot of them will be added. Keep this page in your favorites as a reference.
I could get into every single topic separately (and may be in the future, I might do that), but hey, it's there online already - out in the open. Microsoft has put a lot of work into it … so my advice would be: use and abuse!