Repeated-Row Files
Some exports list the same person on more than one row: one row per manager. Pick a repeated-row Relationship format. Do not use Manager IDs in one field or Solid and dotted manager fields for that source. Those formats expect one row per person and report Person ID {key} appears more than once. Choose a repeated-row relationship format.
The 5,000 limit counts source rows, not unique people. A repeated-row file can hit the cap with fewer unique people than 5,000. See Zenpo Org Chart.
Repeated rows — first manager is solid
Use this when there is no type column. Map Person ID and Manager ID.
The first row for a person establishes the solid-line manager. Later rows establish additional reporting managers. Content (name, title, and the other mapped fields) comes from the first row. If a later row disagrees, editors see later rows carry different content ({values}) — the first row's values are shown.
Repeated rows — relationship type field
Use this when another column states what each row means. Map Person ID, Manager ID, and Relationship type.
Under Classify relationship values, set each distinct value to Solid line, Dotted line, or Ignore. Row order does not matter. Every value must be classified before the chart uses this format. One data issue is raised per unclassified value, not per row.
If you open the file and immediately see many data issues, classify the values. The empty-chart body in that case is The source and fields are mapped. What's missing is what each Relationship type value means: in the pane, under Relationships → Classify relationship values, set every value to Solid line, Dotted line, or Ignore.
PeopleSoft-style person-hierarchy files
A PeopleSoft-style or customer-shaped person-hierarchy file can look like repeated employee rows with:
- Person ID (often
EMPLID) - Manager ID (often
SUPERVISOR_IDorMANAGER_ID) - Relationship type
You may need to classify discovered values such as DIRECT as Solid line and DOTTED as Dotted line. That manual step is expected when the meanings cannot safely be inferred.
Not every PeopleSoft export uses this shape. Configurable extracts differ. If the headers and values are unrecognized, map the fields by hand. Zenpo does not claim universal vendor-schema compatibility and does not join multiple HR exports for you.
Do not map POSITION_NBR as Person ID or Manager ID unless its values actually match the employee keys. See Map Person ID and Manager ID.