When configuring CSV files for bulk updates, the following formatting rules must be followed.
- Properties with multiple values, such as Tags or Divisions, must be separated using “I” in a single column.
Example: To replace a member’s existing Tags with the new Tags Top Member and Executive, the CSV file must read: Top Member|Executive.
- For Target Values, the full hierarchy of the Target Value must be specified.
Example: To append the Target Value San Francisco to a member, the CSV file must read: USA^California^San Francisco.
- When updating member privileges, use T to grant Can Manage Organization privileges and F to revoke them.
- All Property Values are case sensitive except Tags, Attributes and Target Values.
Example: If the tag awesome exists in the program, but the value in the CSV file is AwEsOmE, the awesome tag will be applied to the member. However, if a Division China exists in the program, but the CSV value is china, the uppercase China value will not be applied to the member.
- With the exception of Divisions, if a value does not match an existing name in the program, the system will automatically create that value.
Example: If the CSV file contains the Tag california, but this Tag does not exist in the program, the system will automatically create this new tag and apply it to the member. However, if the CSV file contains a Division for San Francisco, but the value does not exist in the program, the system will simply discard the value instead of automatically creating a new Division.