Edit

Share via

Use Advanced Configuration Uploads

  • Article

For highly trained users, Microsoft Viva Glint the Advanced Configuration Uploads option allows you to view file upload details, perform custom data access uploads for users in bulk, and complete complex data updates.

Review upload types

  • MANAGERS_UPLOAD: To upload custom results data access for dashboard users in bulk.
  • Retroactive User Updates: To perform an upload to user data in closed surveys.
  • ROLE_UPLOAD: To upload users to a Viva Glint User Role, follow the guidance in this article: Import and export Viva Glint User Roles.

Note

To upload employee data, follow the guidance in this article: Upload your employee attributes to Viva Glint.

Caution

Uploads performed in Advanced Configuration do not calculate derived fields or transform date formats to yyyy/mm/dd. If data should be derived, like Tenure from Hire Date, load data through the Viva Glint People page or SFTP.

Perform a MANAGERS_UPLOAD

When several users need customized data access to their Viva Glint Dashboards, use the MANAGERS_UPLOAD to update their access in bulk. To grant 1 or a few users access to custom segments of data, grant custom access from their user profile: Learn more.

To upload custom access for multiple users:

  1. Prepare a file using the custom data access export in User Roles.

  2. Save your file in .csv format with a comma separator and UTF-8 encoding.

  3. In the Advanced Configuration menu, select Uploads.

    1. Upload Type: Select MANAGERS_UPLOAD from the dropdown list.
    2. Apply To: For the survey and cycle dropdown menus, make no selection. These selections apply to retroactive uploads only and not to custom access uploads.
    3. Incremental:
      1. Switch on this toggle to append access to users in your file.
      2. Switch off this toggle to overwrite all access for users in your file. Users not included in the file aren't impacted.
    4. Use exact case from the file for the First/Last name: Ignore, this setting doesn't apply to custom access uploads.

  4. Drag and drop your .csv file or browse to choose it in the Drag and drop to upload section.

  5. In the Upload Job Details page that appears, confirm that the Uploaded Lines Summary matches the changes in your uploaded file.

  6. Select Apply Upload to Database to upload new values to and kick off a process to refresh reporting data.

  7. In the Load import file into database? dialog, select Yes.

  8. Go to some users' profiles to confirm that customized access appears as expected.

    For example, the custom data access for this user:

    manager reference population add or remove survey uuid Cost Center Manager Level 1 Region Country City
    [email protected] 0 ADD aa1aa1aa-a1a1-1a1a-1a1a-111111111a11 37651
    [email protected] 0 ADD aa1aa1aa-a1a1-1a1a-1a1a-111111111a11 17123
    [email protected] 1 ADD aa1aa1aa-a1a1-1a1a-1a1a-111111111a11 7890
    [email protected] 2 ADD aa1aa1aa-a1a1-1a1a-1a1a-111111111a11 EMEA Ireland Dublin

    Displays on Ana's profile like this:

    Screenshot of a user's custom Cost Center, Manager Team, and Location access.

Perform Retroactive User Updates

When a survey closes, employee attributes that display in reporting don't update with regular employee data uploads. To update data in reporting in a closed survey, use the Retroactive User Updates option to apply new values. This option applies new data to past versions of user data and doesn't touch current employee information.

Note

To retroactively update a Manager Hierarchy, always use the RETROACTIVE_PULSE_UPDATE Data App and not the Retroactive User Updates option. Learn more.

Important

If your organization can't save files in .csv format, Retroactive User Updates isn't an opton. Instead:

  1. Import an .xlsx file to the People page.
  2. Create a User Role and add these users to the role.
  3. Use the RETROACTIVE_PULSE_UPDATE Data App and select your User Role in roleOrDistributionList.

To perform a Retroactive User Updates upload:

Caution

  • Do not perform a retroactive update while a Viva Glint survey is live.
  • Deleted user data can't be retroactively updated.

  1. Export survey cycle data with the EXPORT_USERS_FROM_SURVEY_CYCLE Data App for the surveys that need to be updated. Learn more.

    Note

    Keep this export of original survey cycle data in case any retroactive updates need to be reverted.

  2. Prepare an update file with the EXPORT_USERS_FROM_SURVEY_CYCLE file from Step 1.

    1. To preserve special characters and formatting, always open files by importing data from .csv in Microsoft Excel.
    2. Delete all columns except for First Name, Last Name, Email, Employee ID, Status, and the attributes that need to be retroactively updated (for example, Department).
    3. Delete all user rows for employees whose data remains the same.
    4. Correct values for users and attributes that need to be updated.
      1. For example: To correct Department = ‘Sales’, ‘SALES’, ‘sales’, which create three values where there should be one in reporting, update all users to Department = ‘Sales’.
    5. Save your edited file with corrected values in.csv format.

  3. In the Advanced Configuration menu, select Uploads.

  4. In the Choose job type dropdown list, select Retroactive User Updates.

  5. In the Survey dropdown list, select your survey.

  6. In the Survey Cycle dropdown list, select your survey cycle.

  7. Switch on the Incremental toggle.

  8. Drag and drop your .csv file or browse to choose it in the Drag and drop to upload section.

  9. Confirm the File to be Uploaded and select Upload.

  10. In the Upload Job Details page that appears, confirm that the Attribute(s) and Updated users count match the attributes and count of users in your uploaded file.

  11. Select Apply Upload to Database to upload new values and kick off a process to refresh reporting data.

  12. In the Load import file into database? dialog, select Yes.

  13. Confirm changes to attributes in your Dashboard and Reports.

Note

Depending on the number of attributes and users involved, it may take up to an hour to see changes reflected in reporting.