Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 262 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
AL Page Extensions using existing Page license
jwilder
Member Posts: 263
I am upgrading to NAV 2018 and have run into a license issue. We currently have purchased access to pages 50000 to 50499 and have used up almost all of those pages.
Part of my strategy to upgrade to NAV 2018 is to create page extensions for all of our page mods to base objects. In doing this I have to assign the page extension to a new page object id. This would mean that I have to pay for more pages to do customizations on an existing base NAV page.
For example there are few fields I have added to Page 10 Countries/Regions. In order to do this in AL it requires an additional page in our object range. it will require me to purchase more pages. Do people agree this is the way it is or am I missing something?
Part of my strategy to upgrade to NAV 2018 is to create page extensions for all of our page mods to base objects. In doing this I have to assign the page extension to a new page object id. This would mean that I have to pay for more pages to do customizations on an existing base NAV page.
For example there are few fields I have added to Page 10 Countries/Regions. In order to do this in AL it requires an additional page in our object range. it will require me to purchase more pages. Do people agree this is the way it is or am I missing something?
Jason Wilder
jwilder@stonewallkitchen.com
jwilder@stonewallkitchen.com
0
Best Answer
-
Options
larshaedersdal
Member Posts: 12
There has been some heated discussions on Yammer regarding that topic. It seems that Microsoft is willing to change this to some degree. This is a quote from a Microsoft Pricipal Program Manager
We have discussed this and I would like to air our current thinking to get your feedback before we move forward with this. The proposal is that we allow objects in the range 80.000 to 99.999 to be used at no additional cost for either table extensions or page extensions. These objects can be used to extend objects that are in the range of 0-1.000.000. This will allow extending the base application as well as any customisations made in the 50.000 to 99.999 range
If your intention is to extend an existing solution you will have to buy objects in the 50.000 to 79.999 range or do code customisation
I still havn't got a confirmation on this.5
Answers
We have discussed this and I would like to air our current thinking to get your feedback before we move forward with this. The proposal is that we allow objects in the range 80.000 to 99.999 to be used at no additional cost for either table extensions or page extensions. These objects can be used to extend objects that are in the range of 0-1.000.000. This will allow extending the base application as well as any customisations made in the 50.000 to 99.999 range
If your intention is to extend an existing solution you will have to buy objects in the 50.000 to 79.999 range or do code customisation
I still havn't got a confirmation on this.
jwilder@stonewallkitchen.com