Skip to main content

Power BI Troubleshooting in Catalog

Use this guide when lineage through Power BI Dataflows looks incomplete or stale, when search does not return an expected Dataflow, or when metadata in Catalog still looks wrong after you fix tenant settings. Work through the sections that match your situation.

Lineage or Metadata Still Looks Wrong After Admin API Changes​

When Admin API Settings are correct but graphs or upstream paths still look empty or old, the gap is usually timing or scope rather than the toggle itself.

  1. Refresh or republish the affected semantic data sets in Power BI so mashup and related metadata match what you expect in the service.
  2. Wait for Power BI to show consistent metadata for those assets in the admin experience you use outside Catalog, then plan for one full Catalog extraction afterward.
  3. Confirm warehouse objects for the same logical environment, for example DEV compared to prod, are actually in Catalog and match what the Dataflow queries.
  4. Re-run validation only after both warehouse sync and Power BI extraction have completed successfully for that cycle.

No Upstream Lineage From a Data Set That Uses Dataflows​

Check these common causes when a Dataflow-backed data set shows no upstream objects in Catalog.

  • Admin API metadata is off or scoped wrong - If DAX and mashup expressions or detailed metadata are disabled or the security group for your Catalog service principal is missing, Catalog doesn't receive enough information to resolve Dataflow-backed tables. Fix the settings, then refresh data sets and wait for the next extraction.

  • Warehouse not in Catalog - Lineage only connects assets Catalog already knows about. Add or expand the warehouse integration for the database your Dataflow queries, then sync again.

  • Stale Power BI metadata - Refresh or republish the data set in Power BI, then run another Catalog extraction cycle.

  • M shape not recognized - If the data set's M does not expose both Dataflow ID and entity in a supported Power BI Dataflows or Power Platform Dataflows pattern, Catalog does not connect the data set to the flow. Compare the model's M to the supported patterns in Power BI Dataflows in Catalog, republish after changes, and wait for extraction.

Lineage Is Partial or Stops at Some Columns​

Column-level lineage depends on how clearly Power Query steps map fields to upstream columns. Heavy merging or indirection inside the Dataflow or data set can limit column-level links even when table-level lineage appears. For column renames and Table.RenameColumns behavior in Power Query, see Troubleshoot Power BI Lineage When Columns Are Renamed. When one entity effectively draws from multiple warehouse sources in parallel, column-level lineage can stop where Catalog cannot pick a single resolved path.

Parameterized or Dynamic M Logic​

Organizations often use M parameters for environment or database names. Resolution depends on what Catalog can infer from exported metadata. If you use complex parameter wiring or highly dynamic connection logic and lineage stays incomplete after you try the other guidance in this article, contact Support with a short description of the pattern. Do not include credentials.

Client-Managed Extraction​

If you run castor-extract-powerbi yourself, compare your log output and output files with a recent successful run on the current extractor. If extraction completes but lineage doesn't improve, gather the run timestamp and open a Support ticket so the team can trace ingestion with you.

When You Cannot Tell Which Workspace an Asset Belongs To​

Depending on how names are shown in lineage, you might not see the Power BI workspace at every step in the graph. When many workspaces share similar content, use consistent data set and report naming that includes the environment so you can tell assets apart.

Cannot Find a Dataflow in Search or Dashboards​

You find Power BI Dataflows in the same places as other Power BI visualization models: under Dashboards in the left navigation or through Catalog search. There is no separate left navigation entry only for Dataflows. Quick search and advanced search both surface visualization models; Dataflows use the name and description text Catalog receives from Power BI, with the same optional tag and field search behavior described in Catalog search. If you still cannot locate a flow, work through this list:

  1. Match the Power BI name
    Search using the Dataflow name as it appears in Power BI, not an informal label, folder title, or workspace nickname. Catalog indexes the visualization model name and description from the tenant.

  2. Include visualization models in advanced search
    In advanced search, confirm Visualization models is included in the result types you filter on. If that type is unchecked or your filters are very narrow, Dataflows disappear from the result set even when they are synced.

  3. Confirm the Power BI integration is healthy
    In Settings > Integrations, check that the Power BI integration is active, not paused, and that credentials are valid. A paused integration or an expired secret stops new extraction, so search and lineage stop updating until you fix the connection.

  4. Allow first sync or a full cycle after big changes
    For Catalog-managed Power BI, the first ingestion can take up to 48 hours. After you change admin settings, workspaces, or major model definitions, wait for at least one successful extraction before you assume a Dataflow is missing.

  5. Check workspace and access in Catalog
    If your Catalog user or team does not have access to the workspace or asset scope where the Dataflow lives, you might not see it in lists or search even when extraction succeeded for the tenant.

For a concise summary of how search applies to visualization models, see the Advanced Search Results and How Is Search Performed sections in Catalog search.

What's Next?​