You’re offline. This is a read only version of the page.
What is the easiest way to set Read/Create only for All users on the LogisiticsPostalAddress table.
Our Executive group stated "no users should be able to change addresses in the system".
My approach was to create a new Role that had a table level privilege of Create for the LogisticsPostalAddress table and then assign this new Role to other Roles. And set the Table Permissions Framework to Create/Delete. Then maybe Overide the Role???
Is this a good approach? Also, I am confused as to what security level will take precedence if one Role states "Full Control" and another Role states "View". What access will the user have if both Roles are assigned to that user?
Thank you for your help!
*This post is locked for comments
I have the same question (0)
I'm afraid you can't easily do that with roles setup. Create access level includes read as well as edit access levels. Note also that LogisticsPostalAddress is a date-effective table, so when you create a new record and specify ValidFrom, and a record for the same location with a different ValidFrom value and empty ValidTo already exists, then you'll actually modify the existing record, too, as its' ValidTo field will be updated by the kernel. Consider creating an XDS policy that will restrict access to the table.
As to effective access level in case of two or more roles per user: AX uses the maximum available access level, so in case of "Full Control" and "View" the effective level will be "Full Control".
Share
Report
All responses (
Answers (
4
