Documentation

Territory Mapper help

For the Salesforce administrator who has just installed Territory Mapper, or who inherited it. These pages are in reading order, not alphabetical — and The two hierarchies is the one not to skip.

Setting it up for the first time? Start at Admin setup. Four of the steps cannot be shipped with the package and have to be done by hand in your org, and three of them fail silently when missed.

• Contents Everything Territory Mapper does, in the order it is worth reading.

• Getting started Your first territory model, in about ten minutes.

• The two hierarchies There are two trees, and they have nothing to do with each other.

Install and set up

• Installing Territory Mapper Getting the package into your org, and the one thing that has to be true before you start.
• Setting up the org Everything that has to be true before Territory Mapper works, in the order to do it.
• Geocoding clean rules Salesforce's built-in geocoding data integration rules turn a billing address into a latitude and a longitude and write them onto the record, along with an accuracy telling you how precisely the address matched.
• Defining territory roles What a territory role is, why the package ships none, and how to add yours.

Using Territory Mapper

• The map window Everything on screen, and what each piece is for.
• Building a territory model Read The two hierarchies first if you have not.
• Drawing and editing boundaries Drawing a boundary means selecting census areas.
• People, roles and assignment Two different things get attached to a territory, and mixing them up is the second most common confusion in this product after the two hierarchies.

When something is wrong

• The exception queue Assignment Exceptions is where every record that could not be assigned ends up, with the reason and what to do about it.
• Coverage gaps A coverage gap is an area inside your territory model that no territory covers, and where records are actually landing.
• Troubleshooting By symptom.

• Vocabulary The words this documentation uses, what they mean, and — where they differ — what the app calls the same thing.