Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate GroupMember Records #13

Open
nealmundy opened this issue Oct 11, 2019 · 0 comments
Open

Migrate GroupMember Records #13

nealmundy opened this issue Oct 11, 2019 · 0 comments

Comments

@nealmundy
Copy link

It is possible to create Public Groups whose members include Territories or Territories+Subordinates.

When an org is transitioned onto TM2, the enableRemoveTMGroupMembership permission will remove Group records that relate to Territories and Territories+Subordinates.

When that happens, any GroupMember records that reference those Group records will also disappear.

Customers will therefore need to migrate any GroupMember records that reference a Territory or Territory+Subordinates. If they do not, then any Users who are assigned to the Territories within a Public Group would lose visibility to the data that is shared with it.

Unfortunately it is not possible to build a SOQL query that gives us an idea of how many of our customers have actually created Public Groups that contain Territories / Territories+Subordinates as members. It is therefore difficult to say how commonplace this is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant