Hello Everyone,
I was developing a Dimension update solution for one of our client and found one interesting thing about NAV Objects Permissions limit.
Yes, NAV Objects Permissions do have a defining limit. We can define maximum 80 Tables permissions in Object Permissions.
Kindly refer below snapshot for reference.
If any Developer tries to Define more than 80 Tables in Object Permissions, Developer would get warning "You have reached the allowed number of permissions".
NAV considers first 80 Tables defined Object Permissions and would delete rest if are defined more when OK button is pressed.
Kindly refer below snapshot for reference.
I hope this would help you a lot.
Your valuable comments and feedback are appreciated.
Just out of curiosity, and not knowing your specifics, could you make the one object deal with 80 of the tables, and then when it's done, have that object run a different object to deal with the next 80 tables you're trying to update the dimensions on? Kind of a squirrely way to go, but it might work. And thanks for the heads up on the limit!
ReplyDeleteThx for your comment, and yes I had to create 2 separate Objects and the second Object is ran after execution of first object is completed.
DeleteWhy in God's name would you need to add permissions for 80 tables?
ReplyDeleteHello Dave,
DeleteI was developing a tool which included updates of Dimensions and G/L Accounts with many to one mapping in entire NAV (including Posted and Ledger Data). So i had to provide permissions of that many tables.
It is look like wrong design. Do you really need indirect rights for all these tables?
ReplyDeleteAlso you don't need add rights for tables which don't store data(like temporary tables).
And why do you need rights to delete/insert records? Better to restrict as much as possible...
Hello,
DeleteI was developing a tool which included updates of Dimensions and G/L Accounts with many to one mapping in entire NAV (including Posted and Ledger Data). So i had to provide permissions of that many tables.
And yes the permissions were restricted as per requirement.
I agree with other users, it looks strange to use more than 80 tables in permissions but, in case you need to do it, maybe you can split your code in another objet for specific permissions...
ReplyDeleteHello David,
DeleteThx for your comment, and yes I had to create 2 separate Objects for providing remaining Tables permissions and that second object is ran after execution of first object is completed.