This article details how to properly format a source with values that adhere to destination field requirements, including character length and valid characters. The table below lists the required fields and their requirements for OneSync and each destination type, as well as the formatting for Groups. Unique fields are denoted by an asterisk (*). You can click here for definitions for each field and mapping term.
OneSync fields are based off of LDAP attributes. Thus, it is best practice to avoid using the following special characters, unless they are required to properly format the field value or path (e.g. firstname.lastname@example.org; CN=ContainerName,OU=OrgUnit; /GSuiteOU).
- Forward slash (/)
- Backward slash (\)
- Left square bracket ([)
- Right square bracket (])
- Colon (:)
- Semicolon (;)
- Vertical bar (|)
- Equal sign (=)
- Plus sign (+)
- Asterisk (*)
- Question mark (?)
- Left angle bracket (<)
- Right angle bracket (>)
- Double quote (")
- At symbol (@)
|Field||Min Length||Max Length||Notes|
|Organizational Unit Path||1||255||
Organization Units should be formatted from most specific to least specific (e.g. OU=Most Specific,OU=Least Specific).
|*mailNickname||1||64||Cannot begin with a period.|
Requires 3 out of 4 of the following: lowercase, uppercase, digits, symbols (not including spaces).
Up to 64 characters before the @ symbol, and 48 characters after.
Must be formatted with a forward slash (e.g. /OrgUnitPathName)
|*primaryEmail||1||64||No more than one period in a row.|
GSuite password sensitivity and settings can be edited in the gsuite admin console.
Comma separated value (CSV) files are text files that store tabular data and use commas as delimiters. You can manually edit CSV files in a text editor, but it is recommended that you edit them via Excel for visual ease. You can click here for details on how to open CSVs in Excel without losing data.
Note: When using Microsoft Excel to edit and format your CSV data, you must save your file as type "CSV (Comma delimited)".