Troubleshooting Workday Prism Analytics connectivity
Learn about troubleshooting Workday Prism Analytics connectivity.
Why do preflight checks fail even though my credentials are valid?
Workday Prism Analytics gates table access behind its own Prism Access Security Group, which is separate from the Integration System Security Group used to authenticate. A valid access token isn't enough—confirm that the Prism Access Security Group exists, nests your Integration System Security Group as an Unconstrained Security Group, and has been granted the required Domain Security Policies, then re-run Activate Pending Security Policy Changes.
Why don't Data Change Tasks appear as assets in Atlan?
Data Change Tasks aren't cataloged as their own asset type in Atlan. Each Data Change Task only shows up indirectly, as a Process asset connecting the Prism table it loads to its upstream source. See How Workday Prism Analytics lineage works for the full mechanism.
Why don't I see column-level lineage for Data Change Tasks?
Column-level lineage only builds when Atlan can resolve the Data Change Task's source to a real, structured, column-aware asset—either a Prism table, or a table in an externally-connected, crawled system. Data Change Tasks sourced from a Workday report, an FTP file, or a browser upload don't have that structure in Workday, so Atlan can only build table-level lineage for those.
Why do dotted-outline assets appear instead of my actual Snowflake table?
That's a partial asset. Atlan creates it when a Data Change Task's source can't be resolved to an asset that's already been crawled—either because that source system's connection hasn't been crawled in Atlan yet, or because the specific table hasn't been crawled. Once the relevant connection is crawled, the next Workday Prism Analytics crawl resolves the partial asset into the real one.
Why is my Prism table missing lineage to Data Change Tasks?
Confirm the Integration System User has Get access to the Integration Process and related Data Change Task Domain Security Policies (see set up Workday Prism Analytics), and that the Permission Data Changes preflight check passes. A Data Change Task that Atlan can't retrieve at all can't produce lineage.
Why aren't Prism tables organized into databases or schemas?
Workday Prism Analytics doesn't have a database or schema concept—Prism tables are cataloged as root-level assets directly under your connection. This is expected; see What does Atlan crawl from Workday Prism Analytics?.