Zenpo Org Chart FAQ
Direct answers for Org Chart. Longer rules live on the dedicated pages linked below.
Does Zenpo Org Chart connect to Microsoft Graph, Azure AD or my HR system?
No. It reads a SharePoint list or a CSV file that you control, as the signed-in user. There is no Microsoft Graph use, no directory wiring, and no connection to any HR system.
Can I build the chart from a CSV instead of a SharePoint list?
Yes. Store a .csv file in a document library in the same site, then choose CSV file as the data source type. See CSV and SharePoint List Sources.
Can I use a Workday, ADP, SAP SuccessFactors or PeopleSoft export?
Yes, as a CSV file you export and store in SharePoint yourself. That is an HRIS CSV export workflow, not an HR system connection. Known export-style and API-style headers, including supported ADP aliases, may be proposed as mappings. Recognition only suggests mappings. You review them. Unrecognized or configurable exports remain manually mappable. Zenpo does not claim universal vendor-schema compatibility. See Automatic Mapping Suggestions.
Does a "Workday-style" or "PeopleSoft-style" notice mean Org Chart is connected to that system?
No. It means the file's headers and values resemble that vendor's typical export shape. There is no connection, no live sync, and no API call to any HR system.
How do I describe who reports to whom?
Set Relationship format under Relationships. There are five choices, including one field that holds several manager IDs, separate solid and dotted fields, two repeated-row formats, and Manager lookup — SharePoint list only. See Choose a Relationship Format.
What makes someone appear at the top of the chart?
The chart draws one selected hierarchy. A person with no resolved solid-line manager is a root candidate. With Root person on Auto-detect top, the displayed tree is the root candidate with the most people beneath them. Other root candidates appear as Unassigned and are not drawn. See Unassigned People and Unresolved Managers.
Some people are missing from the chart. Where are they?
There are three causes. Check in this order.
- They are unassigned people — root candidates outside the selected hierarchy.
- Rows with a reporting-line problem are skipped and reported in Data issues: a row that reports to itself, or rows in a circular reporting loop.
- Rows the web part never received: the selected View filter and item limit apply first, and a reader only sees rows their SharePoint permissions allow.
See Fix Data Issues and Missing People.
Why does Data issues say a branch was kept as a separate root?
The solid-line manager is not among the loaded rows. Often that manager's row is filtered out by the selected view. The person becomes a root candidate. Their reports stay attached beneath them. They appear in Unassigned unless you set Root person to them. They are not automatically another displayed top of the chart. The panel text is Manager ID {key} does not match any Person ID in this source — branch kept as a separate root.
Can someone report to two managers?
Yes. One person may appear under their solid-line manager and under additional reporting managers. Extra appearances are leaves marked ⇄. See Multiple Managers and Additional Reporting Lines.
Can I export the chart as an image?
Yes, when PNG export is on, from Full tree mode. The export always draws every branch expanded, whatever is collapsed on screen. A very large chart can be refused: This chart is too large to export as an image. Set a Root person in the property pane to export one branch at a time. Setting a Root person is the remedy.
How large a roster can it handle?
Up to 5,000 source rows. A larger source is refused rather than truncated. Repeated-row files can contain more rows than unique people. A notice appears above 3,000 loaded people. Charts read best at up to about 500 visible nodes. This Help does not promise that a 5,000-row chart will expand or export quickly.
I opened my file and immediately saw a wall of "data issues." What happened?
You are almost certainly on Repeated rows — relationship type field with one or more values in Relationship type not yet classified. Go to Relationships → Classify relationship values and set each value to Solid line, Dotted line, or Ignore. One data issue = one unclassified value, not one per row. See Repeated-Row Files.
My CSV didn't get any automatic field suggestions. Is the file broken?
No. Suggestions depend on recognizing headers and sample values. Known API-style and export-style names, including supported ADP aliases, may be recognized. An unrecognized or configurable extract may get no suggestion. Map Person ID and the manager field(s) by hand. That is not an error.
My file has a column that looks like an employee or job number, for example POSITION_NBR. Should I map that as the Manager ID?
Only if its values actually match the values in your Person ID column. If they do not, the chart tells you so rather than silently guessing. See Map Person ID and Manager ID.
Why does my Workday export show something like "Engineering (Supervisory)" as a department name?
That text is written by Workday itself, inside the exported data. Org Chart displays field values exactly as they appear in the source. It never adds, removes, or rewrites part of a value.
Some org shapes render as a tall single column of cards next to a lot of empty space. Is that expected?
No. That was a layout defect, fixed as of v0.6.1.25. If you see it on a current build, report it. It is not expected behavior on any shape.
Can I map more than six values as external?
The External marker field (optional) itself must contain six or fewer distinct nonblank values. You then select which of those values mean external. You cannot pick six values out of a large vocabulary. See Configure the External Marker.
When do I need to touch Multiple-manager separator?
Only when Manager ID(s) or Dotted-line manager ID(s) (optional) can hold more than one key in a single cell. The choices are Auto — comma, semicolon, or pipe, Comma, Semicolon, and Pipe. Auto detects those three. There is no other delimiter.