When using the Bulk User Import feature in CloudSOC, you may need to update only part of the user records without impacting the existing values. This article goes over the details on how to deal with blank or empty fields in your import file to avoid unintentionally removing user data.
Product: CloudSOC (CASB)
Feature: Bulk User Import
The 'bulk user import' process in CloudSOC works by reading a csv file formatted according to a template provided in the Admin Console. Here's how it behaves:
If a user record does not exist, CloudSOC treats it as a create action and adds the user.
If the user already exists, CloudSOC treats it as an update and replaces the existing data with the new values from the csv file.
However, if you're only trying to update some fields and leave others unchanged, and those fields are left blank in the spreadsheet, CloudSOC will interpret the blanks as instructions to remove the existing values, replacing them with empty fields.
To prevent CloudSOC from overwriting existing data with blanks, you can use a special column in the import template called operation. This column gives you control over how each record handles blank fields.
How to Use the operation Column:
This gives you flexibility to update only the fields you want, without accidentally clearing out important user data.
Example:
In this case, assuming both user records have existing values for the "secondary user id" attribute, and this table is used for the "bulk user import", then the secondary user id of the first user will be removed, while the second one will remain as is without any change.
| Last Name | First Name | Groups | Title | Admin | Access Profile | Work Phone | Cell Phone | Secondary User ID |
Active |
Operation |
|
| LN1 | FN1 | [email protected] | [u'ENDUSER'] | 1-2333411123 | 1-2333411123 | No | overwrite | ||||
| LN2 | FN2 | [email protected] | [u'ENDUSER'] | 1-2333411123 | 1-2333411123 | No | ignore_empty |