Import user considerations

Last Updated : Aug 04, 2020 |
  • If the comprofileset has associated handlelist or commprofilelist, you cannot merge or replace commprofileset attributes name and Isprimary.

    To move handlelist and commprofilelist from one commprofileset to another, perform the following:

    1. Perform Replace - Import file with no commprofileset.

    2. Perform Update (merge/replace) - Import file with the new commprofileset with associated handlelist and commprofiles.

  • For security reasons, you do not export the Password fields in the XML file.

    When you import the same file to a new system, you must provide the password for users with any administrative role. For security reasons, the system does not export the Password fields to the XML file. Therefore, import of users with any administrative role fails, if the password is not provided.

    To import users with any administrative role, in the XML file for the users, add the following XML tag after the <username> tag:

    <userPassword> provide password for user </userPassword>

    For Partial Merge/Replace import type, if you do not specify the password, the existing password remains.

  • To enhance the performance of a file with large user records, split the file into smaller file sizes. For example, you can split a user import file of 15 Kb into three files of 5 Kb each. To speed up the import process, schedule three import jobs in parallel. System Manager has the ability to process multiple files concurrently.