5
Before removing a page or a report, we mark the object as ObsoleteState = Pending in version N.
In version N+1, we delete the object.
But in version N+1, we also create new objects.
For that, we use the intellisense in VSCode that gives us the next available object number in the app object range.
The con comes the fact intellisense recycles the object number deleted, without looking at the object numbers in use in version N, beside the fact the package is in the alpackage folder for the AppSourceCop.
The consequence is errors coming from AppSourceCop about the fact all actions/fields/public procedures has been changed within the same object id between version N and N+1.
Could the object numbering be improved?
It would require to consider objects declared in the previous version as still in use.
In version N+1, we delete the object.
But in version N+1, we also create new objects.
For that, we use the intellisense in VSCode that gives us the next available object number in the app object range.
The con comes the fact intellisense recycles the object number deleted, without looking at the object numbers in use in version N, beside the fact the package is in the alpackage folder for the AppSourceCop.
The consequence is errors coming from AppSourceCop about the fact all actions/fields/public procedures has been changed within the same object id between version N and N+1.
Could the object numbering be improved?
It would require to consider objects declared in the previous version as still in use.
STATUS DETAILS
Needs Votes
Business Central Team (administrator)
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future.
Best regards,
Business Central Team