Map Person ID and Manager ID
ID-based Relationship format choices need a Person ID and one or more manager ID fields. The values in the manager fields must match values in Person ID.
What to map
| Relationship format | Required ID fields |
|---|---|
| Manager IDs in one field | Person ID, Manager ID(s) |
| Solid and dotted manager fields | Person ID, Solid-line manager ID. Dotted-line manager ID(s) (optional) if you have additional reporting lines |
| Repeated rows — first manager is solid | Person ID, Manager ID |
| Repeated rows — relationship type field | Person ID, Manager ID, plus Relationship type |
| Manager lookup — SharePoint list only | Manager only. The list item ID is the person key |
Person ID is this person's key in the source. It is not a job title, email, or display name.
How matching works
Matching is exact and case-sensitive on trimmed values. Write the same key the same way in both columns.
A manager ID that does not match any Person ID does not silently guess another person. For a solid-line manager, that person becomes a root candidate and appears in Unassigned unless you chart their branch. For an additional reporting manager, that line is dropped. See Unassigned People and Unresolved Managers.
Multiple-manager separator
Multiple-manager separator appears when a mapped manager field can hold more than one key in a single cell (Manager ID(s) or Dotted-line manager ID(s) (optional)).
Supported separators:
- Auto — comma, semicolon, or pipe
- Comma
- Semicolon
- Pipe
Auto detects comma, semicolon, and pipe. There is no other delimiter. Do not put a custom character in the control. If your source uses something else, split the keys in the source or pick a different Relationship format.
Keys that look like people keys but are not
Map a manager field only when its values actually match Person ID. Many HR exports also carry seat, record, or job numbers. A column such as POSITION_NBR is often that kind of number, not an employee key. If you map a field whose values do not match, the chart reports it rather than guessing.
PeopleSoft-style files sometimes include REPORTS_TO that holds a seat number. Map it as Manager ID only when those values overlap your Person ID column.