Load Users into CX Directory Task

About the Load Users into CX Directory Task

The Load Users into CX Directory task is used to save CX user data to Qualtrics. This task allows you to keep your CX user data up-to-date on a regular basis. To use this task, you must first load data into Qualtrics using a data extractor task.

Setting Up a Load Users into CX Directory Task

1. Create an ETL workflow.
2. Select Data source (ETL extractor). In this step, you’ll extract data that you can load to another destination. See using Building ETL Workflows for more information. Your task must import the following fields:
   
   • Unique Identifier
   • FirstName
   • LastName
   • Email.
     Qtip: We recommend using the extract data from SFTP files task. The user data example file is configured for use with this task.
     Qtip: There is a maximum file size of 100 MB.
     Qtip: If your organization uses SSO, include a Username column to be filled in with the values from your Active Directory that you are passing us for the username attribute. The #brandID will be appended to the username automatically upon upload of the file. If your organization doesn’t use SSO, this column should generally match the email column.
3. Click Add a data destination.
   
4. Choose the Load Users into CX Directory task.
   
5. Select the data extracting task you set up earlier.
   
6. Begin mapping your imported data fields to CX user attributes using the dropdown menus. Fields marked with an asterisk are required. You can also map fields via a file upload.
   Qtip: By default, all existing CX user attributes in your license will be included in your mapping. You can remove any unneeded fields by clicking Delete row in the Options menu next to the field.
   Qtip: If your source field and CX directory field names match exactly, then they will be automatically mapped for you!
7. If needed, you can map individual values for each field by clicking Map values. This is useful if you want to use different data values in Qualtrics. See Mapping Fields and Values for more information on mapping individual values.
   Example: In our imported data file, we have the value “Europe” but want this saved as “EMEA” in Qualtrics. This can be done by mapping values.
8. You can remove any unnecessary fields by clicking Delete row next to the field.
   Qtip: You must remove any unmapped CX user attributes.
9. If needed, click Add field to add additional fields to your mapping. When adding a new field, you can map to an existing CX user attribute, or create a new one.
   Qtip: If creating a new field, you must give the field a name. Be careful when naming your field, as you cannot edit or delete it without contacting your Brand Administrator.
   
10. If your license has SSO enabled, you can enable Import as SSO Users to import these users with their SSO username. This will allow the user to access Qualtrics via SSO.
11. When finished, click Save.
    Qtip: The task will not let you save if your mapping is incomplete. If the Save button is grayed-out, then double-check your mapping.
12. Toggle your workflow On.
    

When the workflow runs, your users will be imported to Qualtrics and saved in your CX user admin.

Mapping Fields and Values

When setting up this task, you can map your imported data fields via a file upload. This section covers how to map fields and individual field values using a file.

Mapping Fields

1. While setting up the task, click Download a sample mapping. Open this file in a spreadsheet editor on your computer.
2. Add your field mappings using the downloaded file as a template. When creating your mapping file, keep the following in mind:
   
   • Each column in the file is 1 field mapping.
   • The value in the first cell in the column is the source field name.
   • The value in the second cell in the column is the Qualtrics field name.
   • Your file cannot exceed 100MB.
   • Save your file as a CSV file.
3. In the task in Qualtrics, click Upload file and choose the mappings file on your computer.
4. You can then manually adjust your mappings and map individual field values.

Mapping Values

1. After mapping your fields, click the Options menu next to a field and select Map values.
2. Click Download CSV template.
   
3. Add your value mappings using the downloaded file as a template. Do not delete the “from” and “to” headers. When creating your mapping file, keep the following in mind:
   • The imported field values should go in the “from” column.
   • The field values you want saved in Qualtrics should go in the “to” column.
   • You can include up to 1000 mappings in your file.
   • Save your file as a CSV file.
4. In the task, click Upload file and choose your mappings file.
5. By default, blank values are not imported. If you’d like blank values to be imported as something, enable the Map blank values to a default value and then specify the value in the Default value box.
   
   Example: Let’s say I’m importing employees and we have a field for “Office Location.” Some employees are remote and therefore do not have a value for this field. Instead of skipping this field for employees without a value, I can specify a different value, such as “Remote” to be imported for these employees.
6. If necessary, you can manually adjust your mappings by typing in the appropriate boxes.
7. You can manually add additional values by clicking Add Row.
8. To remove a mapping, click the minus sign ( – ) to the right of the mapping.
9. When finished, click Done.

Troubleshooting Tips

This section covers common issues that can appear when setting up this task.

• After selecting the task, you may see the error Directory not found, try reloading the page. This error appears if your license does not have access to CX user admin. To enable CX user admin, contact your XM Success Manager.
• After selecting the task, you may see the error Unique ID is required to be enabled to use this extension. This error appears when your license does not have unique identifiers. To enable unique identifiers, contact your XM Success Manager.
• If the Save button is grayed-out, then that means your mapping is not complete. Make sure that any fields included in the task are completely mapped.

FAQs