Skip to main content
Version: Next

Datasource Map

The Datasource Map tab provides a visual overview of the tables and relationships detected for a data source during semantic extraction. It gives Builders and Administrators a clear picture of how the underlying tables connect, without needing to inspect the schema directly.

Availability​

The Datasource Map is generated automatically as part of semantic extraction (see Operations). It is not available until at least one semantic extraction has completed.

If no semantic extraction has run yet, the tab shows an empty state noting that Datasource Maps are generated from the detected tables and their relationships.

What the Datasource Map Shows​

The map is an interactive graph visualization built from the same Descriptions and Hierarchies data available elsewhere in the editor. It displays:

  • Tables detected in the data source, distinguished by node color based on type
  • Relationships between tables, with connection strength reflected in the thickness of each edge
  • Column-level context feeding into the relationships, drawn from the semantic extraction results

The visualization reflects the data source's current semantic state. If you re-run semantic extraction, the map is regenerated to match — without leaving duplicate or orphaned entries behind.

If you add, edit, or deactivate a relationship in the Relationships tab, the map does not rebuild automatically — an "outdated" hint appears here instead. Rebuilding on every curation change would trigger unnecessary work, so it's a deliberate step.

  • Zoom in / out — use the zoom controls to focus on specific parts of the graph
  • Pan — click and drag to move around the map
  • Refresh — rebuild the map against the current relationships, and reload the current map state without leaving the tab

Best Practices​

  • Review the Datasource Map after the first semantic extraction to confirm the detected relationships match your expectations.
  • Use the map to spot missing or unexpected joins before users start generating charts from this data source.
  • If the map looks sparse or disconnected, check the Filters tab to ensure the relevant tables and columns are included, then re-run extraction from Operations.

See Operations for information on triggering and scheduling semantic extraction, Descriptions and Hierarchies for the underlying metadata the map is built from, and Relationships to correct or add the connections it draws.