Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

[DX], OrgPath, OrgLoginId, LoginId, Password, FirstName, LastName, EmailAddress, ContactEmail, CanViewReports, ForcePasswordChange,[OrgProfileFieldName, OrgProfileFieldValue]*

Note:
The first column indicates whether a user should be deleted (D) or deactivated (X). Leave empty to create/update and activate the user
OrgPath: is optional if no OrgLoginId has been set. Add user to this organization
OrgLoginId: is optional if LoginId has been set. Don't update if empty. Used as a secondary look up key to find an existing user (if LoginId is empty)
LoginId: can be user name or email address. Optional if OrgLoginId has been set. Used as a primary look up key to find an existing user
Password: if the user already exists and left empty - the password is not updated
FirstName: will not be updated if empty
LastName: will not be updated if empty
EmailAddress: will not be updated if empty
ContactEmail: will not be updated if empty
CanViewReports: 'True' or 'False'. Anything not 'True' (e.g. empty) for new users will be interpreted as 'False'. For updates, will not be updated if not 'True' or 'False'.
ForcePasswordChange: 'True' or 'False'. Anything not 'True' (e.g. empty) for new users will be interpreted as 'False'. For updates, will not be updated if not 'True' or 'False'.
OrgProfileFieldName: case-insensitive OrgProfileFieldName (must exist for the organization at OrgPath)
OrgProfileFieldValue: value of the OrgProfileValue (will not be updated if empty, *remove* to delete the value)
[OrgProfileFieldName, OrgProfileFieldValue]* means that those columns can occur 0, 1, n times
A new user is created if a non-existing OrgLoginId is speficied or no LoginId is set
*remove* can be used to remove a user property/fieldvalue since leaving it empty doesn't update the property/fieldvalue
*remove* can be used for all columns except: [DX], LoginId, Password and OrgProfileFieldName.

...

2) Place that zip file in the directory that was configured.

3) Done!


The background thread will check if there is a file in that directory.  Then the following will occur:

1) The zip file is extracted using the password.

...

The new user importer can be manually used via the "Client tool" command line.  Similar to the "User Upload", except that it is able to handle csv files with varying column order as configured in the org attributes.  If no order is specified (as per above) default order is assumed.

...