CSV file fields

CSV fields

The CSV file should be formatted to include the following fields in the particular order:

• User Details (required):
• • Primary Key

    It can be Username, Email, or SAML ID.

  • First Name
  • Last Name
  • Email Address
  • Username
  • Enabled/Disabled flag

    This field cannot be blank. Each row must contain enabled/disabled, true/false, 1/0 Boolean values.

  • Username of Manger

    This is used for the Org Chart.

• Permission Groups

  You can specify several groups separating them with vertical lines |.

• Profile Details (optional)

  Up to 50 profile fields can be synchronized.

For the example files, see User Sync Add-On Example Files on Worx.

Requirements for formatting data in fields

Encoding

The files must be UTF-8 encoded.

Primary key

The Primary Key must always be the first field and must contain a username, email, or SAML ID to be used to uniquely identify this user and search for it in Jive.

Advanced User Sync process takes the primary key of each row (always the first column) to use as its way to look up the correct user in Jive. If the user exists, it is updated with any new information in the file. If the user does not exist, it is created.

Order of fields

The order of the fields is important for the user sync to work correctly.

Dates

Dates must be formatted differently depending upon which field you are mapping to. Any Jive default date fields will be in UTC+offset standard format. For example, a date in Jive can look like this: 1997-07-16T19:20+01:00.

Any profile field that you custom created must be in standard MM/DD/YYYY format.

Jive default profile dates, such as Member Since and Last Logged In, are set by Jive, and cannot be synced.

Enabled/Disabled Flag

The Enabled/Disabled field is required, and each row must have a value. This cannot be blank. True/False or 1/0 are acceptable.

Addresses and multi-select fields

Portions of the address field and other multi-select fields should always be separated by a vertical line | with no spaces inbetween. For example, an address may look like this: Street|Street2|City|State|Country|ZIP.

Headers

If the add-on settings indicate that the CSV file has column headers, then they must exist in the file for the process to work. If the settings indicate that there are no headers, none should exist in the file.

You should configure your add-on to include a header if you have column names as the first row of your file. If you have data with no headers, make sure that option is cleared.

Bad information

Each row of your CSV file must contain valid data. Jive will not create or update users where invalid information is provided.

Unicode is fully supported, but the process will ignore any rows that include HTML, JavaScript, or characters invalid for the destination field. No ＆＊，／：；？ can be added to a username or an email address.

Empty fields

If you want to pass an empty or null value, make sure the comma delimiters are included with nothing in between them.

Text with commas

If you want to pass text that includes commas, such as biographies, titles, or free form text, you need to enclose the entire field value in double-quotes. For example, a title may look like this: "Director, Support".