Product » Implementation » People Data Integration

People Data Integration

Sonar6 provides a method for automatically importing changes of people information and organizational structure from your people system-of-record (typically an HRIS or payroll system). The process is straightforward, but will require IT expertise.

Process

Set up your system-of-record to export a "people file". This is a flat file export of people data in a specific format.

The people file is sent to the Sonar6 server from your system. The transfer format is via SFTP. Credentials will be provided as part of the integration process.

The Sonar6 server processes the file, and a summary email is sent back. This processing happens nightly, and will manage all changes to people data and org structure. This includes moving all review data to an employee’s new manager for changed reporting lines.

People File

The People File can be set to run in two configurations (you need to tell us your chosen configuration).

A. The file contains only data changes. This means that people "deletes" need to be marked explicitly.

B. The file contains all people data. People "deletes" are handled implicitly (if a person is no longer in the file, then they are treated as deleted)

The People File needs to be organized with column headings as per this file (which includes maximum column widths).

Sample people file .xls format

The file formats supported are:

1. Excel 95-2000 xls (BIFF5)

Notes for advanced users

The import process only affects people data. It cannot be used to change configuration content (like competency names), or performance review content (like employee ratings or goals)

New people must have a Role-Type and Role-Category, and a valid unique email address, otherwise they will not be created.

All people must have a unique-key-field. This is normally their Employee ID, but can be their name. Which field is used is set universally.

Passwords do not have to be sent for existing people. This is only used for initial configurations. If this field is used these need to be encrypted.

The preferred name format is "First-name Last-name"; but other formats including "Last-name, First-name" can be used. Contact us if you have unusual name requirements.

Tags & Roles will not be created if they do not exist in your configuration. To add new Tags and Roles either use the Advanced Setup (if you have access) or contact support.

Configuration options

  • People file configuration A or B. Does the file contain all data or just changed data.
  • Unique-key-id. The unique identifier for people can be their employee ID or name.
  • Name Format. First-name Last-name, or something different.