In Summer ’14, Territory Management 2.0 became available through a Beta program. It is an exciting offering, but still has some limits to consider before making the switch from the original Territory Management. Here are three reasons why you might want to consider using Territory Management 2.0.
Our Favorite Features:
- Maintain multiple versions of your territory hierarchy in production. This has all sorts of implications; first, it allows you to maintain historical information about territory assignment.
You can see over time how an Account moved from one territory to another. Second, if you want to restructure your territories, you can create a draft version of your territory model in production and activate it when you’re ready with the click of a button, making if much easier to restructure your territories.
- Preview your territory assignments before publishing! Before activating a new territory model in production, ensure your account assignment rules are working as expected by running a report to view how accounts will be assigned to territories in the new model. This allows you to see how your actual production data will be assigned before restructuring your territories, allowing you to modify your approach if accounts are not assigned as expected and reduce some of the risk associated with restructuring territories.
- Enable Collaborative Forecasting! While Territory Management 2.0 is not integrated with Collaborative Forecasting (meaning that you will not have the ability to forecast by territory), you can forecast using the role hierarchy. This works well in organizations that are using territory management for controlling visibility but not forecasting purposes. Why would you want to take advantage of Collaborative Forecasting? Read my blog on this here.
There are a few limits to Territory Management 2.0 that I will cover in a future blog to help with your decision making around whether or not Territory Management 2.0 is the right feature for you.
How do I get list of account assign to any Territory(Territory2 object) under active Model