MetaLocator supports multiple data sources including spreadsheets, text files, SalesForce and now Google Drive.
This integration allows you to import Google Sheets stored in Google Drive just as you would a CSV or spreadsheet from your computer. This allows you easily share access to the Google Sheet that contains your data with multiple contributors via Google Drive's existing sharing facilities.
When importing data, choose the new Google Doc icon as shown below:
Click the "Connect" button and authorize MetaLocator to view your Google Drive Sheets.
Important: If the system displays an Authentication error, simply click the button again, as this indicates the login token has expired.
For Enterprise users and subscribers to our Backgrounding Addon, the "Keep Google Sheets Data In Sync" box will be available. Check that box to create a Background Process which can be scheduled to run on a regular basis. See below for more detail.
When the "Keep Google Sheets Data In Sync" box is checked, the system will create a background process. That process can be found as shown below:
By default, the job is created but not scheduled. Toggle the Scheduled slider to enable the job. This will replay the same import process performed above on a regular basis. Be sure to consider if that replay will cause duplicates or otherwise overwrite or delete data. For example, if you choose "Replace" during the import, then manually add more records directly to MetaLocator and not your Google Sheet, the background process will delete those records as it replays the import with the "Replace" option.
A summary email will also be delivered to the account owner as shown below. It provides a basic summary of the record operations performed during the import.
If your drive token expires, or your Google Password changes, you can remove the locally stored token as shown below:
Once that token is removed, google imports will no longer function until the procedure to import data, as shown above, has been redone.
Running Jobs as Other Users
If running as a job as another user, the job will run with that user's Google Drive token, not the user that established the job. In the below example, John Smith's token. Therefore, he would need access to the Google Drive document and his token would need to be reset if the password changed or access was revoked.