[Jason Wilder]

I am in the process of upgrading to NAV 2018.  My strategy is to only use AL for base pages that we have modified, everything else will be C/AL (heavily using events to reduce work for next upgrade though).

So I did my first 2 page extensions in AL yesterday (liked it, pretty fun) and came across a fairly annoying license issue.  I feel like I have seen a post on this somewhere but can’t seem to find it now.  The issue is when creating a Page Extension (guessing same issue for Table Extension) it requires me to use up a Page object in our license.  So this means that for every base Page I have modified to move to a Page Extension requires the use of another Page object.

For example in C/AL environment I added 2 fields to page 10 Country/Regions, no big deal.  In AL I have to use up one of our unused page id’s in our license range (we have purchased 500 pages 50000 to 50499). 

With close to 200 mods to base pages this will cost us $1,600 (I think it is $800 per 100 pages)  to start plus whatever other mods I make in the future.  If this same issue applies to table extensions then this is significantly more money as it is $800 (I think) for only 10 tables.

Am I missing something?  Hoping Microsoft picks up on this and resolves quickly.

——————————
Jason Wilder
Senior Application Developer
Stonewall Kitchen
York ME
——————————

[Jason Wilder]

Embarrassing having to update/answer my own thread. 

I received a response from another post that Microsoft is working on a solution for this.  Sounds like in the future there might be a specific range of objects that can be used for for table and page extensions against base objects.  I’ll post when this is confirmed for sure.

——————————
Jason Wilder
Senior Application Developer
Stonewall Kitchen
York ME
——————————
——————————————-

[Gerton Postema]

?Far from embarring I would say Jason, since this is very usefull information. Thanks for sharing.

——————————
Gerton Postema
Livit
——————————
——————————————-