By using this website, you agree to our Terms of Use (click here)
If you use Type A, then you have to put all Items in a Restriction Group. Then the User will only be able to see the Items in the Restriction Group / Restriction Groups that they belong to.
Your saying that every single item needs to be in at least one restriction group in order for other restriction groups to take effect?
Not every single item. But an Item won't be restricted unless it's in a Restriction Group. So you'd have to login as a user who does not have access to a certain Restriction Group, then you'll see that they don't have access to the Items in that Restriction Group. That's with Type A Restriction Groups.
That is what I'm doing:
Add several items to a restriction group
Add a user to said restriction group
Result: The user can still see all items.
Tried this as well:
Add an item to a restriction group.
Do NOT add the user to said restriction group
Result: User can still see the items in the restriction group. The only way to hide the items in the restriction group is to use an inverse group. The effect I want is this: Add user to restriction group, user can only see items in that group, no other items
Restrictions Groups is a Nightmare - if you've made a mistake - How do you delete a restriction Group, and re-setup one?
You can't. Set them up in a test tenant and verify before doing so in production.
You can try voting here but it doesn't seem to be going anywhere.
https://feedback.acumatica.com/ideas/ACU-I-1037
And yes, they are a nightmare!
Agreed, can't delete them. Can only deactivate them. Similar challenge when trying to delete Attributes.