why I can not delete a access role name in production ruleset.
This rule is for testing some changes, I cannot delete other associated ‘Access of Role to Object’.
why I can not delete a access role name in production ruleset.
This rule is for testing some changes, I cannot delete other associated ‘Access of Role to Object’.
Can you try after removing the privileges and AROs from the role?
First, you have to remove AROs associated with the Access Role Name, and then you should be able to delete it.
@RameshSangili I cannot delete AROs because they are all useful. I just saved the access role as in the production rule set for testing, and there is still a formal version available. I just want to delete the test version now that the testing is over.
@SohamM95 I cannot delete AROs because they are all useful. I just saved the access role as in the production rule set for testing, and there is still a formal version available. I just want to delete the test version now that the testing is over.
That is the reason why its not deletable. Even if you delete the production ruleset version, the original version will stay so it should not impact testing.
There are no other AROs in the production rule set. Only one access role name. I only want to delete this access role name.
The other AROs are in the formal ruleset and cannot be deleted. They did not make any modifications.
As shown by the error, this validation is added to prevent orphan RARO objects.
I believe discussions to change the functionality in the past were rejected (BUG-415181) because allowing role deletion from lower versions may not be possible in all cases. There could be some other access group in the system which have access only to lowest version like Sales Force Automation etc. In this case it is inappropriate to delete the role as deletion could result in orphan RARO objects.
General practice is not to delete the older versions of any rule but to change their availability to No/Withdrawn.