In this blog we will see how we can modify standard page by adding few fields and modify property of existing fields.
For this I assume table extension is already created and now would like to add fields in page layout by creating page extension
Now I decided to create a small module that will help you manage the Extensions and Ids.
Besides what I showed in the first post, I added to the module an extra feature: now you have the possibility to get the free Ids: if for example you have 2 table extensions with Ids 50251 and 50254, the free Ids are considered the ones not used within the ones used, so in this example: 50252 and 50253. You can do this by specifying and extra parameter to the function.
Although this should technically be part of the base install, since V2 extensions are pushed as the “best thing since sliced bread”, it doesn’t seem like this is the case. Just try installing a base version of 2018 without using the Cronus database as the database. This would be the case for any customer that you are upgrading. Now, after you installed NAV 2018 with your custom database, try publishing an app file.
I picked up a new challenge these days: for one of our (quite big) customers, we need to develop a solution, based on extensions. In short: ready for the future, easy to upgrade. When I would explain the case in a paragraph, you’d say “this is not NAV”, although when you would really look deep into it, it’s ideal for an Extension-scenario, obviously in combination with Business Central.
Finally Extensions V2 supports DotNet (At least in the Developer Preview.
But as soon as you fire this up, perhaps with the help of TXT2AL, you’re met with assemblies not resolved. Both assemblies from standard DotNet (from the global assembly cache) and standard NAV DLLs.