Domo - Refresh Dataset
First time using this Blueprint? Make sure you follow our Domo authorization guide.
Manually trigger a refresh of a dataset in Domo.
Authentication can be provided with either an access token or a combination of username and password. If both are provided, access token will be preferred.
This Blueprint will only kick off the refresh and will almost always return a status of success. It will not wait around to verify if the created refresh job was successfully completed, but it will create and store the generated job ID to shipyard-artifacts/domo-blueprints/variables/job_id.pickle
- A Vessel built with the Domo - Check Refresh Status Blueprint should be run immediately after this Vessel. This will ensure that you build your Fleet to act on the final status of your refresh.
|Access Token||DOMO_ACCESS_TOKEN||Password||➖||-||-||Access token to authenticate with Domo. Used in place of username/password.|
|DOMO_EMAIL||Alphanumeric||➖||-||-||Email that you use to log into Domo. Used with the password for authentication as an alternative method to providing an access token.|
|Password||DOMO_PASSWORD||Password||➖||-||-||Password associated to the email used to sign into Domo. Used with the email for authentication as an alternative method to providing an access token.|
|Client ID||DOMO_CLIENT_ID||Alphanumeric||✅||-||-||Client ID of your organization's Domo App.|
|Secret||DOMO_SECRET_KEY||Password||✅||-||-||Secret associated with the provided Client ID.|
|Domo Instance||DOMO_INSTANCE||Alphanumeric||✅||-||-||Typically found in the URL structure as https://DOMOINSTANCE.domo.com|
|Dataset ID||DOMO_DATASET_ID||Alphanumeric||✅||-||-||UUID of the dataset you want to download, typically found at the end of the URL.|
Below is the YAML template for this Blueprint and can be used in the Fleet YAML Editor.
blueprint: Domo - Refresh Dataset
DOMO_CLIENT_ID: null ## REQUIRED
DOMO_SECRET_KEY: null ## REQUIRED
DOMO_INSTANCE: null ## REQUIRED
DOMO_DATASET_ID: null ## REQUIRED