You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey Vjeko,
we have multiple apps, most of them have a dependency on the biggest one.
When I create an .al file using one object type and retrieve an id in app A and then create a new .al file using the same object type in a different app using a .objidconfig with the same id range your extension will possibly retrieve the same id. The AL extension will give an error saying the object number is used already but your extension will "accept" the number with no further warning.
Problem is that app A will compile but app B (which has a dependency on app A) won't.
Are we meant to separate our id ranges by app? Or are you going to add a feature that cross-checks all id's using the same object type within all apps in the future? Or are we plainly using the extension in a wrong way?
We would very much like to use your extension as it would make our life significantly easier.
The text was updated successfully, but these errors were encountered:
Hi Vjeko,
I'm running a team of 6 developers for a BC14 project with 20 apps with dependencies. The lack of Cross App numbering prevents us from using AL-object ID Ninja. We simply cannot allocate fixed object id ranges to every app.
Please consider implementing Cross App Numbering within a Project.
Hey @petterssonmv , look into the app pool feature. It's not really documented by vjeko but you will find a .md in this repo which should help you.
In short, we created an app pool for all of our apps, used the same id range in the .objidconfig and that was pretty much the perfect solution for us.
Hope this helps!
Hey Vjeko,
we have multiple apps, most of them have a dependency on the biggest one.
When I create an .al file using one object type and retrieve an id in app A and then create a new .al file using the same object type in a different app using a .objidconfig with the same id range your extension will possibly retrieve the same id. The AL extension will give an error saying the object number is used already but your extension will "accept" the number with no further warning.
Problem is that app A will compile but app B (which has a dependency on app A) won't.
Are we meant to separate our id ranges by app? Or are you going to add a feature that cross-checks all id's using the same object type within all apps in the future? Or are we plainly using the extension in a wrong way?
We would very much like to use your extension as it would make our life significantly easier.
The text was updated successfully, but these errors were encountered: