Importing External Device Data for Bulk Edit

The Import for Bulk Edit tool is the final step in the Round-Trip workflow. This feature allows administrators to apply changes made in an external spreadsheet (CSV or Google Sheet) back to the Google Admin Console via Gopher for Chrome Premium. 

This is a round-trip workflow:

  1. Export your current device data from Gopher for Chrome Premium into a CSV or Google Sheet using Export for Bulk Edit Action.
  2. Edit the spreadsheet. Change locations, asset IDs, OU paths, notes, etc. (each device can get different values). How to access and edit is covered in the Export for Bulk Edit Action article.
  3. Reimport, covered in this article, the edited file back into Gopher for Chrome Premium.

View Tutorial

The Logic of the Import

  • Differential Updates: Only data that differs from the current record will be updated.
  • The Ignore Blanks Rule: If a cell in your spreadsheet is empty, the system will ignore it and keep the existing value on the device. It will not overwrite data with blanks.
  • The Gopher ID Anchor: Every row must contain the CDW Device ID (often referred to as the Gopher Device ID) and ideally the _gopher_checksum to ensure the mapping is 100% accurate.

Pro Tip: To shield your workflow from accidental data updates, you can use the Export for Bulk Edit feature to take a spreadsheet snapshot of your device fleet, allowing you to Force Import your backup data at any time to instantly restore your system to a specific previous state.

Running an Import to Update Device Data

  1. Open the Import Tool: Navigate to the Actions menu in the top right of the Device Search screen and select Import for Bulk Edit.
  2. Select Your Source Location: In the Source Location drop-down, choose either Google Drive (default) or CSV.
  3. Choose Your File: Click Select from Google Drive (or upload your CSV). Navigate to your file and click Select or Open.
  4. Click Continue.
  5. Wait for Validation: Gopher for Chrome Premium will automatically begin validating your data. This ensures your headers are correct and your Device IDs are valid.
  6. Review the Update Summary: Once validation is complete, the modal will display a summary showing the number of devices that Will be updated. Verify this matches the scope of your work.
  7. Execute the Import: Click Continue to start the update job. You can track the progress via the blue spinner in the side navigation bar.
  8. Refresh Your View: Once the background job is finished, click the Refresh Cache button on the main dashboard to view your updated device records.

Troubleshooting

  • Unexpected Device Count: If the Will be updated count is lower than expected, the system likely found that some rows in your sheet already match the live data perfectly, and no update was necessary.
  • Validation Errors: Ensure you have not renamed or deleted the original column headers from your export, as these are required for proper field mapping.
  • Checksum Conflicts: If you see an error regarding a _gopher_checksum mismatch, it means the device has been updated elsewhere since your last export. Perform a fresh export to resolve this.

Comments

0 comments

Please sign in to leave a comment.

Articles in this section

See more