SalesforceLabs
Add Territory Management
What do you want exactly about territory mgt? A table? With which column? How would you define the badness score for a territory? Would you need also a visual diagram as the role explorer? What would be the goal of such visualization ?
in conclusion tell me more about this new feature you would like!!
thank you
I think a visual diagram similar to the role would be very useful and if it's possible to also show dependencies? E.g. currently in my org we are on the original territory management and we know we need to transition to the enterprise territory manager before June, however, we have territories referenced in code, custom fields, custom objects etc. So finding out the dependencies is very manual at the moment.
On Sat, 6 Feb 2021, 11:58 Vincent FINET, [email protected] wrote:
What do you want exactly about territory mgt? A table? With which column? How would you define the badness score for a territory? Would you need also a visual diagram as the role explorer? What would be the goal of such visualization ?
in conclusion tell me more about this new feature you would like!!
thank you
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/VinceFINET/OrgCheck/issues/23#issuecomment-774462508, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHN7HK6RU3ZN7Y672ZIIBOTS5UVFBANCNFSM4XGGL3ZQ .
As a starter:
- the datamodel around Territory management v1 is here: https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_erd_territory.htm
- the datamodel around Territory management v2 is here: https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_erd_territory2.htm
So to answer your ask around TMv1:
- TM is a feature that needs to be enabled, so in short, the sobject might not be in the database just because the feature is not ON
- there is an end of life for this feature --> Summer 21 so not so sure if it's worth it to develop a feature for something that will retire in 3 months... (see https://help.salesforce.com/articleView?id=The-original-Territory-Management-module-will-be-retired-in-the-Summer-20-release&type=1&mode=1)
So maybe would be nice to have directly that ask for TMv2 ??? What do you think? Or you think that feature needs to happen now so that more people will get the tool....?
Agree on the feature development just for 3 months may not be worth it, however, would have been very useful for migration to ETM. Also, we don't know how many orgs have left it until now to migrate. On that note - are there any templates for the migration to TMv2, something like a checklist of tasks to cover, just so one doesn't miss out migrating anything?
Definitely a useful feature to have on the TMv2 then.