Hey legends,
Investigation into Roles v Territory Roles
Role hierarchy represents management relationships, reporting rollups, approvals, and other hierarchical workflows. ETM allows us to simplify the sales branch of the role hierarchy to contain only roles for their purpose (Job Function not a team). Then use the territory hierarchy to extend access to records based on users’ territory assignments.
- Role hierarchy affects sharing settings for all standard and custom objects in Salesforce.
- Territory Management only affects the sharing settings of accounts and the standard objects that have a master-detail relationship to accounts.
Territory Roles track user functions within territories by creating territory roles and assigning them to territory users as needed. For example, create roles such as Territory Owner, Sales Manager, Mentor, Product Specialist, Associate or Sales Representative. Users can even have different roles in different territories
In the end we went with a very simple role structure
- Focus on data accessibility with consideration to reporting structure of the org.
- Each role in the hierarchy should represent a level of data access that a user or group of users needs.
- As a best practice, keep the role hierarchy to no more than 10 levels of branches in the hierarchy.
- Avoid Empty Roles
- Sharing setting “Grant Access Using Hierarchies” will be set to False. Records are shared via user Territory Assignment
#ETM0 discutindo
- Atividade recente
- Data de criação
- Recomendado
- Todas as perguntas
- Perguntas com uma resposta aceita
- Perguntas não respondidas
- Perguntas sem resposta aceita
When I'm publishing my territories to the ETM - not all of the logic is carrying over and populating for the territories and quite a few are blank after publishing. Trying to figure out why this is the case and looking to have the logic published from the carves.
Any insight?
@Bhavin Patel Hey Bhavin - here's the case (https://help.salesforce.com/s/case-view?caseId=5003y00000ugCK6AAM)
Case Number: 31383418
Hello. I am working on setting up collaborative forecasting with ETM. When I create forecast types I am not seeing the option to specify use of territory hierarchy. ETM and Collaborative forecasting are enabled. Is there something else I need to do? Do I need to request activation of some sort?
I have specified forecast managers for some of the territories (but not all).
I have set up two forecast types that use role hierarchy, and those are working
I would like to be able to use both types for different use cases in the org.
Thank you.
It is active. Attached are some screenshots
Hi, I am working on an engagement for a customer to migrate from TM 1.0 to ETM. We need to use ObjectTerritory2Association in order to link the accounts with the territories in ETM enabled org. This requires me to fetch data from two objects in TM 1.0 org- AccountShare and Group. I believe the Group data is created automatically by Salesforce upon the creation of Territories. However, I noticed a rather odd pattern in Group data in ETM orgs that a '1' is appended in front of all Group records in the DeveloperName field. Has anyone come across this behavior?
@Song Haidong, thanks. I understood the loading territories part. My concern is about the Group data. I am given to understand that as soon as the territories are loaded, Salesforce creates a record in Group object automatically against each territory record. Eg- If the territory name is ABC, Salesforce will create a record in the Group object with DevName ABC. However, in an ETM enabled sandbox, the DevName is coming as ABC1. I am not understanding why that 1 is being appended with it. Any idea on this? As far as I know, there is no explicit trigger written to create the Group records, it is an OOTB feature of Salesforce. Please correct me if my understanding is incorrect.
What out of the box reports do you use as Territory Planning admins? Ones that make your job easier - see accounts that have been assigned, unassigned, performance summary etc.
What reports that you share with your sales team after territories are created and before you activate a ETM model?
Hi @Nikhil Banka , as of right now, there is not any reporting within Territory Planning. You could, however, use the Account report in Salesforce after publishing the territories.
The information you share with your sales team after territories are created would be the territory shapes, which will take into consideration the data from reports that you would have included when starting the territory planning project.
After you activate ETM, it would probably be beneficial to discuss reporting with someone on from that side.
After switching to ETM, we have noticed that all of our reports that filter on roles are no longer correctly filtered. Does anyone know what could have caused this from the cutover or how to fix it (in bulk preferably)?
We do have a case open, but no answers yet. There seems to be something from Winter ‘19 that maybe wasnt applied until ETM was activated?
Hello Everybody. Apparently by queying the UserTerritory object in a very old org no results are returned and it's likely that TM1 has never been used. Is anything required to switch to ETM (i.e.open a support case) or it will happen seamlessly and without consequence? Thanks
If you are not using TM1 in the org, then no action is needed, if you are using it, then you will need to migrate, you can find the migration FAQ on left panel of this community under Information section.
I am working on pulling the metadata for Territory 1 out and converting to ETM. I was able to successfully pull out, munge and upload the TM1 to TM2 model, however I am not getting any of the territory assignment rules, etc. Is there an efficient way to pull the assignment rules, etc. from TM 1 and munge into TM2? I followed this guide for the Territory Model, which worked well but none of the other stuff comes across when following sample package.xml.
Hi Team-- our org migrated to ETM over the weekend and we're experiencing a few minor issues that I'm attempting to reconcile. One of those issues is that when a user tries to pull the new Territory (Territory2) field on an Opportunity standard report, that field isn't available the report field set. I've checked the field level permissions and users can definitely see it and they are even seeing it on the Opportunity page layout. Is there a setting or another permission I missed in order to report on this standard Opportunity field? Thanks!
Hi @Jason Edmondson We're starting on a migration plan too, do you have a list of steps/tasks you went through as part of the migration, would be useful as a reference if you can share.
Hello - I've been trying to setup ETM and came across an issue that's been stumping me. I've manually aligned accounts certain territories, run the account filter, then the opportunity filter (on all opps, all time). I run some audit reports and I find there are whole territories that don't have their opportunities aligned. The accounts are aligned, but the opportunities under those accounts are not. I've opened a support ticket for this, but was wondering if there was a solution staring me in the face. I've run a query on opportunities where the account is in the list of accounts returned from a ObjectTerritory2Association query - it returns a list of 1000 opportunities without a territory id value.
8.3.0
Thanks for following up Joey. Unfortunately, it wasn't the same issue for me. From what I could tell the filter code completed successfully with no error email like you mentioned.
After working with Support, we were able to pinpoint the issue only occurred when I bulk processed everything from the setup page - that is, new opportunities were placed into the right territory. We never pinpointed what the issue was there, instead we agreed I should just run a manual data load to align opportunities to the right territory. Whenever we go through some territory re-alignment I may need to dig into the apex a bit more.