ACL update using Update Set

[Ziad Qadora]

Hello,

I recently created new write ACL and assigned to sn_customerservice_agent, but when I moved using an update set to out test instance I did notice that the role was snc_internal and not sn_customerservice_agent as it should be.

I went back to the dev instance and removed snc_internal and added sn_customerservice_agent on an update set.  When I committed the update set in the test instance and check the role, it is now showing both roles

Is this an expected behavior when making an update via an update set? 

I have attempted to back out the update set so that I can attempt with elevated role, but backing out the update set did not remove the sn_customerservice_agent role.

When I re-committed the update set with elevated role, both roles were still there.  

Thus, please let me know how I can do the update via an update set instead of manually removing the role in the test instance and possibly the production instance when the update sets are committed there?

Regards,

Ziad

[Ravi9 · Accepted solution]

AFAIK , if you have CSM plugin installed - i think oob behavior does that , what i know is - for csm they create 2 oob roles - snc_internal and snc_external - hence depending on what you change - it always tags one of the two to make sure it separates an external customer resource from an internal employee one

[Ziad Qadora]

We do have CSM installed, thank for the explanation.