Use an HR System (HRIS) CSV Export with Zenpo Web Parts

Zenpo does not integrate with Workday, ADP, SAP SuccessFactors, PeopleSoft, or any other HR system. There is no connector, no sync, no credentials, and no scheduled import. Those products are named here only as systems that can export employee data to CSV.

The supported path is an HRIS CSV export workflow: export a CSV, store it in SharePoint, select it, and map columns.

Two products accept a CSV source: Zenpo Org Chart and Zenpo People Directory. Refreshing the data means replacing the file in SharePoint. The web part reads whatever the file contains when it loads.

The workflow

1. Export employee data to a CSV file from the HR system, or from any other source that can produce CSV.
2. Store the CSV in a SharePoint document library in the same site as the page.
3. Select the CSV as the web part's data source: Data source type → CSV file, then pick the Document library and the CSV file.
4. Map the columns to the roles the web part needs.

File and library rules

These rules are identical in Org Chart and People Directory.

Rule	Behavior
File type	.csv only. Not XLSX, not TXT. Only files ending in .csv appear in the picker. Renaming a spreadsheet to .csv does not convert it.
Library scope	Document libraries in the current site only. No cross-site sources. Hidden libraries are not offered.
Header row	The first row must name every column. Header names must be non-empty and unique (checked case-insensitively).
Delimiter	Comma or semicolon, detected automatically from the first non-empty line. Tabs and pipes are not supported.
Quoting	Quoted fields may contain the delimiter, line breaks, and doubled quotes ("").
Encoding	A leading byte-order mark is ignored. Windows and Unix line endings work. Blank lines are skipped. Values are trimmed.
Row limit	5,000 source rows. A larger file is refused, not truncated. Repeated-row Org Chart files can contain more rows than unique people.
Ragged rows	A short row is padded with blanks. Extra cells beyond the header are ignored.

CSV error messages

Both products show these messages in an error frame with a Retry button.

Situation	Message
The file has no content	The CSV file is empty.
No usable header row	The file has no header row. The first row must name each column.
One or more header cells are blank	The header row has unnamed column(s) at position {list}. Give every column a name.
Two headers share a name	Duplicate column header(s): {names}. Column names must be unique.
Headers but no data rows	The file has headers but no data rows.
The file could not be downloaded or read	The file couldn't be read as CSV — check that you still have access and that it's a real .csv file, not a renamed spreadsheet.
Over the row limit	This roster contains more than 5000 people. Refine the source or use a smaller organizational scope.

Column mapping

Neither product requires particular column names. You map roles to whichever columns your export contains. The web part may propose a mapping automatically. Always review it.

Recognition can match known export-style and API-style headers, including supported ADP aliases such as AssociateID and ReportsToAssociateID. Recognition only suggests mappings. Unrecognized or configurable exports remain manually mappable. Zenpo does not claim universal vendor-schema compatibility. It does not connect to, authenticate against, query, or synchronize with any HR system.

Photo is never detected automatically from a CSV. Map the column that holds a link if you want photos.

On Org Chart, an External marker field (optional) may be suggested from known headers such as Worker Type. Values are never preselected. See Configure the External Marker and Automatic Mapping Suggestions.

Hire date is detected automatically only when the file's headers match a recognizable HR export pattern. On a generic CSV, map it manually.

If the export has separate first-name and last-name columns, the Name role can combine two columns into one displayed name.

These column names are examples, not requirements:

Role	Example column
Person ID	EmployeeID
Manager ID(s)	ManagerEmployeeID
Name	FullName
Job title	JobTitle
Department	Department
Location	Location
Email	Email
Hire date	HireDate

Dates in a CSV

• Dates written as YYYY-MM-DD always work.
• Numeric dates like 04/05/2020 are read as day-first or month-first only when one of the numbers proves the order (a value above 12). When a date is genuinely ambiguous, the web part does not guess. It counts those values and asks you to choose.
• The Date format setting (Auto / Month / Day / Year / Day / Month / Year) appears once a hire-date column is bound and ambiguous values were found. Choosing a format applies to the whole source.
• Two-digit years are not parsed. Dates are treated as plain calendar dates, so they never shift with time zones.
• Notification: {N} {column} values could not be interpreted. Choose the source date format.

Org Chart from a CSV

A CSV source uses one of the four ID-based Relationship format choices. Manager lookup — SharePoint list only is not offered for files.

• Person ID is each person's own key. Manager fields hold their manager's key(s).
• Matching is exact and case-sensitive on trimmed values.
• A blank manager ID makes someone a root candidate. The values NO_MANAGER and -1 are also treated as "no manager".
• A manager cell may hold several keys separated by comma, semicolon, or pipe. Those are the only supported separators.

A PeopleSoft-style or customer-shaped person-hierarchy file can be repeated employee rows with Person ID, Manager ID, and Relationship type. Classify values such as DIRECT as Solid line and DOTTED as Dotted line. Not every PeopleSoft export uses that shape.

See Choose a Relationship Format and Repeated-Row Files.

People Directory from a CSV

CSV sources offer Person ID and Manager ID in place of the list-mode Manager role. Both keys must be mapped for the detail sheet's Manager and Also reports to rows to appear. The People Directory does not build a hierarchy. The keys only add those linked rows on a person's detail sheet.

Practical checklist

1. Export to CSV with a header row.
2. Confirm every column has a unique, non-empty name.
3. Include a stable person key and a manager key (for Org Chart), or the display fields you want (for People Directory).
4. Keep the file under 5,000 rows. Use a filtered export for larger organizations.
5. Upload it to a document library in the same site as the page.
6. Add the web part, choose CSV file, pick the library and file, and review the mapping.
7. If hire dates are involved and the web part reports ambiguous values, set the Date format.