Preflight checks for Domo

✦TL;DR

Atlan uses the [DataSet API](https://developer.domo.com/portal/72ae9b3e80374-list-data-sets) to fetch dataset metadata from Domo.

||

Your AI can read this via Docs MCPcurl -fsSL "https://docs.atlan.com/install-docs-mcp" | bashConnect

Before running the Domo crawler, you can run preflight checks to perform the necessary technical validations. The following preflight checks are performed:

Datasets API

Atlan uses the DataSet API to fetch dataset metadata from Domo.

✅ Check successful. Datasets API is working.

❌ Check failed

For example: {"code":101,"message":"Access denied","status":403,"httpMessage":"Forbidden"}}#STATUS:403

Dashboards API

Atlan uses the Page API to fetch dashboard metadata from Domo.

✅ Check successful. Dashboards API is working.

❌ Check failed

For example: {"code":101,"message":"Access denied","status":403,"httpMessage":"Forbidden"}}#STATUS:403

Cards API

Atlan uses the DomoStats cards API to fetch card metadata from Domo. This checks the format of the response and tries to find the Id, name, and description columns.

✅ Check successful. Cards API is working.

❌ Check failed. <Response received from the API>

Card-dashboard relationship API

Atlan uses the DomoStats card-dashboard relationship API to fetch card-dashboard relationship metadata from Domo. This checks the format of the response and tries to find the cardId and pageId columns.

✅ Check successful. The card-dashboard relationship API is working.

❌ Check failed. <Response received from the API>

Dataset-card relationship API

Atlan uses the DomoStats dataset-card relationship API to fetch dataset-card relationship metadata from Domo. This checks the format of the response and tries to find the dataSourceId and cardId columns.

✅ Check successful. The dataset-card relationship API is working.

❌ Check failed. <Response received from the API>