Contents

Everything Territory Mapper does, in the order it is worth reading. Fifteen pages: three to understand what you have, four to get it working, four to use it, three for when it is not working, and a glossary.

If you are in a hurry

1 · Understand what you have

Getting started

Your first territory model, end to end, in about ten minutes. Assumes the product is already installed and set up.

The two hierarchies

The page not to skip. Territory Mapper has two tree structures in it, they are unrelated, and almost every confusing thing the product does is explained by the difference between them.

• The geographic tree — fixed, four areas, read-only
• Your tree — yours, any depth, any names
• The part that catches everyone
• Where the two trees actually meet

2 · Install and set up

Four pages, in this order. Three of the steps in them fail silently — no error, no warning, nothing in a log — so each page says which of its steps those are.

Installing Territory Mapper

• Before you install: Enterprise Territory Management
• Installing the package, and who to install it for
• What the package does and does not bring with it
• Checking the install took

Setting up the org

• The order of the setup steps, and what breaks if you skip each one
• The GIS callout credential — and the second step people miss
• Granting users access to the credential
• The three permission sets
• Allowing the app's origin in CORS
• Verifying the whole chain

Geocoding clean rules

The prerequisite. A record with no coordinates can never be assigned to a territory. This is the most likely cause of "it doesn't work".

• What clean rules are, and turning them on
• Backfilling the records you already have
• Verifying it in two minutes
• What "imprecise" actually costs you

Defining territory roles

• Why the package ships no roles
• Adding each role, field by field
• Flat, hierarchical, or both
• Grouping roles
• Reporting on Role in Territory

3 · Using Territory Mapper

The map window

Everything that is on screen and what each piece is for.

• The territory tree, and the map
• City search
• The background map
• The legend — and why it matters more here than on most maps
• The in-app help button

Building a territory model

• What a model is
• Planning one before you draw anything
• Creating the model, and naming it
• Adding a territory, and adding a child
• The rule that catches everyone: a territory must be mapped before it can have children
• Renaming, moving and deleting
• Seeing everything beneath a territory

Drawing and editing boundaries

• Turning map management mode on
• Choosing how fine your selection is
• The three ways to select: click, box, lasso
• Saving — and what saving does not do
• What happens to a neighbour
• Clearing a boundary, and what "and its descendants" means
• Reading the map

People, roles and assignment

Two different things with similar names, kept apart on purpose.

• Membership — putting people in territories, and giving them roles
• Assignment — how records reach territories
• What is not assigned, and what does not happen
• Checking your work

4 · When something is wrong

The exception queue

Every record that could not be assigned, why, and what to do about it — organised by where the fix lives.

Coverage gaps

Areas inside your model that no territory covers. Normal, findable, and not the same thing as an orphan territory model.

Troubleshooting

By symptom: nothing is assigned, the map is blank, records went to the wrong territory, a territory disappeared, selection is slow.

5 · Reference

Vocabulary

The words that matter, the places this documentation and the app disagree, and words you will meet elsewhere that mean something different here.

About the pictures on this site

Every screenshot is generated by a harness and none is taken by hand. The pictures of the map are a single recorded session of the product being used — a model created, a boundary drawn by clicking the map, people assigned — captured against the public demo, whose dozen people are invented and whose email addresses are all on a domain that cannot resolve. The pictures of Salesforce Setup are captured against a real managed install with the running user's identity masked.

Two things to know before reading an image:

• 🔴 The map has no labels on it. No typeface has been chosen for map text yet, so territory names do not render on the map itself. A territory is identified by its colour, its position, and the legend — which is why the legend gets a section of its own.
• The demo's banner is cropped off the top of each image. The application is offset by exactly that much when the banner is present, so what you see is the geometry your own window has.