Fix Data Issues and Missing People
People can be off the chart for three different reasons. Check Unassigned first, then skipped rows in Data issues, then rows the web part never received. The warning chip above the chart is visible to everyone who can see the page, not only to editors.
Three causes of missing people
Check in this order.
1. They are outside the charted tree
The chart draws one tree at a time. Valid top-level people outside that tree are listed by name in the Unassigned strip beneath the chart. They are not drawn as nodes.
Choosing a Root person does the same for everyone outside that branch.
This is the most common cause. See Hierarchy Models: Manager Lookup and ID + Parent ID.
2. The row has a structural problem
Rows that report to themselves, or rows caught in a circular reporting loop, are skipped. They appear in the Data issues panel. They are not drawn.
3. The web part never received the row
The selected View filter and item limit apply before the chart sees the list. A reader only ever sees rows their SharePoint permissions allow. Those people never reach the chart, so they do not appear as Unassigned and they do not appear as skipped rows.
The Data issues panel
A warning chip appears above the chart when the data has something worth reporting. It opens Data issues, described as structural values that need attention — fix them in the source data.
Chip wording:
- {N} row skipped or {N} rows skipped when only skipped rows exist
- {N} data issue(s) when there are also flagged rows
- Setup check when there are no bad rows but the web part has a suggestion
When the chart cannot draw anything and a diagnosis exists, the panel opens by itself once.
Shared list-load errors (access lost, missing list, throttling, view threshold) are documented on Common Error Messages.
Per-row reasons you can see
| Reason shown | Meaning |
|---|---|
| reports to self | The row's manager or parent key is its own key. The row is not drawn. |
| circular reference | The row is part of a reporting loop. The rows in the loop are not drawn. |
| manager {key} not found — branch kept as a separate root | The referenced manager is not in the loaded rows, often because the selected view filtered that manager out. The person and their branch still render, as another root. |
| Dates: {N} {column} values could not be interpreted. Choose the source date format. | Hire dates are ambiguous. Set Date format. |
A branch that breaks off as a separate root is usually a view problem: the manager's row was not loaded. Fix the view so every manager is included, or accept the extra root and look for that person in Unassigned if they are not the charted tree.
Likely-cause suggestions
When the shape of the data explains a widespread failure, the panel adds one diagnosis:
- {N} rows loaded, but the mapped Name field '{column}' is empty on nearly all of them. Pick a different Name column, or use the derived First + Last name mapping.
- The Manager field '{column}' doesn't resolve against this list's items — its values point outside this list. Map a Person or Lookup column that points at this list, or switch Structure to ID + ParentID.
- Employee ID is not mapped. Select the column containing each employee's unique key — ParentID needs a key column to resolve against.
- The ParentID field '{column}' doesn't hold employee keys — its values look like names or emails and don't match the ID column '{column}'. Map the column that carries each person's manager KEY.
- {N} manager references point at people the view '{view}' filters out. Bind an unfiltered roster view so every manager is included.
Empty structure
List mode: No structure found / No rows in the list have a mapped Manager. Map a Manager (person or lookup) column — or switch Structure to ID + ParentID in the pane.
CSV mode: No rows in the file link to a parent. Check that the ID and Parent ID mappings point at the columns that carry each person's key and their manager's key.
CSV file errors (empty file, missing headers, renamed spreadsheet) are listed on Use an HR System (HRIS) CSV Export with Zenpo Web Parts.