You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: