Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IdRanges by Object Type in App.json #6187

Closed
Vibaek opened this issue Oct 2, 2020 · 3 comments
Closed

IdRanges by Object Type in App.json #6187

Vibaek opened this issue Oct 2, 2020 · 3 comments
Labels
suggestion This is either a suggestion of a completely new feature or a fairly big change request.

Comments

@Vibaek
Copy link

Vibaek commented Oct 2, 2020

I have an OnPrem Customer solution with multiple extensions that all should fit within Customers purchased Object ranges.
Typically you do not have as many Table object as Pages/Report etc.

Example:
50 Tables and Codeunits available + 100 Pages and Reports available in Customer Licens.
"Ext A" needs 40 Tables and 50 Pages. "Ext B" and "Ext C" both needs 5 tables each, total og 50 tables.

IdRanges in App.json :
"Ext A" : 50.000 - 50.050 OK
"Ext B" : 50.050 - 50.059 (No tables available !)
"Ext C" : 50.060 - 50.069 ( No Tables available !)

How should I handle this Issue - IdRange by Object Type would be an option ?

@Vibaek Vibaek added the suggestion This is either a suggestion of a completely new feature or a fairly big change request. label Oct 2, 2020
@Vibaek
Copy link
Author

Vibaek commented Oct 2, 2020

I know one solution could be to re-assign some Object ranges in the Customer License, but some Types as Reports are locked from 50.000 - 50.099 as a result of licens conversion from older NAV versions.

@MetaK
Copy link

MetaK commented Mar 2, 2021

For consideration i will add:

If u have 20 tables and 100 pages in a extension, u can just:
add a range of 20 items (and dont use more than 20 pages/pagesext/report)
OR
add 100 items and without the programmer knowledgement, the app will give an error to the client when the client try to use the 21,22,23... tables.

This problem would be solved with the suggestion above:
making a range for tables 1..20 and another range for other items 1..99

Best regards!

@atoader
Copy link
Contributor

atoader commented Mar 7, 2021

Please go ahead and post this to our Ideas forum at https://aka.ms/BusinessCentralideas, or vote up the idea if its already there. We're constantly monitoring top Ideas and will consider them for a future release.

@atoader atoader closed this as completed Mar 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
suggestion This is either a suggestion of a completely new feature or a fairly big change request.
Projects
None yet
Development

No branches or pull requests

3 participants