Skip to main content
Community Hub

Preflight checks for SAP Analytics Cloud

TL;DR

Before running the SAP Analytics Cloud crawler, Atlan checks that it can authenticate with your OAuth client and read the file repository and model catalog.

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

Before running the SAP Analytics Cloud crawler, you can run preflight checks to perform the necessary technical validations. Preflight checks run in Direct extraction only. The following checks are completed, in this order:

Authentication​

Shown as SAC API in Atlan. Atlan requests an access token from the OAuth Token URL, using the client ID and client secret you provided.

✅ Check successful if Atlan obtains an access token.

❌ Could not authenticate to SAP Analytics Cloud if the token request fails. Confirm the token URL, client ID, and client secret, and that the OAuth client is still enabled and its secret hasn't expired. The token URL must be the Token URL of the OAuth client, not the Authorization URL or the OAuth2SAML Token URL.

File repository​

Atlan lists one item from the file repository (GET /api/v1/filerepository/Resources), which holds folders, stories, and models.

✅ Check successful if the call succeeds.

❌ SAC preflight check 'fileRepositoryCheck' could not complete if the call fails. Confirm that the OAuth client has the File Repository Read access option.

Model catalog​

Atlan lists models from the Data Import service (GET /api/v1/dataimport/models).

✅ Check successful if the call succeeds.

❌ SAC preflight check 'modelCatalogCheck' could not complete if the call fails. Confirm that the OAuth client has the Data Import Service access option.

note

Preflight checks don't test the Data Export service or the story listing. If the OAuth client lacks access to these, the checks pass but the crawl returns no model columns or no Live models. See Set up SAP Analytics Cloud for the access the OAuth client needs.

See also​