One of the quirks of working with extensions is that you cannot run an object from the object designer. This is true for V1 and V2.
With V2 you can start an object (page) after deploy but this only works once and only in the WebClient.
If you just quickly want to check our a page or codeunit in the Windows client you can write a codeunit against an object that does not exist.
An example is the TowersOfHanoi app that Microsoft ships as example. This does not have a page extension to execute itself.
Works all the time.
Want to learn more about extensions? Contact me today!
Wizard pages are working on a revival from being almost forgotten. They were first introduced as form objects in Navision 3.0 as part of CRM. I instantly fell in love and started to create them for my own add-on.
Wizard pages have a few great advantages to normal pages and let’s go over them.
- Save Button – Even though it is not called “Save” the Wizard page is one of the few options in NAV you have to populate data, validate it and cancel the operation without a hassle.
- Overview – Essentially Wizard pages have fast tabs just like Card pages but the tabs are only displayed one at a time giving a clearer overview
- Validation – Wizard pages allow the programmer to clearly validate the contents of each fast tab before continuing to the next fast tab. Much more precise than normal database validation since with a wizard you can asume, program, for a really specifical order of entry.
- Explanation – On each page (tab) of the wizard you can write half a bible explaining to the user what to do. Be careful not to over do it since people these days are not used to sit down and read text anymore.