Data Source Page — Use Data Source page to preview data and set metadata

The challenge of transforming raw data into meaningful visual insight has driven the evolution of business intelligence tools for decades. Early BI platforms like Business Objects and Cognos required analysts to work through complex ETL pipelines and rigid schema definitions before any visualization could be rendered, often consuming days of effort just to validate that the correct data had been ingested. Tableau disrupted this paradigm by introducing an interactive, visual-first approach to data analysis, and at the heart of this approach lies the Data Source page — a unified interface where users can preview their data, set metadata, define relationships, and verify data quality before ever dragging a field onto a canvas.

The core question the Data Source page addresses is deceptively simple: How can an analyst rapidly verify that the right data, in the right shape, with correct types and semantics, is available before committing to analysis? Without this validation step, downstream visualizations inherit silent errors — wrong aggregations due to mistyped fields, incorrect joins producing duplicated rows, or string fields masquerading as dates. The Data Source page exists precisely to catch these issues at the point of ingestion rather than after hours of dashboard development.

The Data Source page is the gateway between your raw data and Tableau's analytical engine. Understanding its architecture requires familiarity with several foundational concepts that govern how Tableau interprets, transforms, and presents data for visualization. These principles operate in concert: connection parameters determine what data is available, the data model defines how tables relate, metadata controls how fields are interpreted, and the preview grid provides immediate feedback on the cumulative effect of all configuration decisions.

The diagram above represents a typical state of the Data Source page after connecting to a PostgreSQL database and dragging three tables onto the canvas. Notice how the Connection Pane provides a searchable inventory of all available tables, while the canvas displays relationship noodles (the dashed lines) connecting tables via their key columns. The data preview grid at the bottom reflects the result of these relationships, showing denormalized output with data type indicators (Abc for strings, # for numbers, 📅 for dates) on each column header. Toggling between the Preview and Metadata views using the buttons in the upper-right corner of the grid allows you to shift between row-level inspection and field-level configuration — a workflow you will use constantly in practice.

Tableau's Data Source page provides a rich set of metadata configuration capabilities that directly influence how the VizQL engine processes queries. Understanding the mechanism behind data type inference, role assignment, and field aliasing is essential for producing accurate and performant visualizations. When Tableau connects to a data source, it reads the schema metadata from the source system — column names, native data types (e.g., VARCHAR, INTEGER, TIMESTAMP) — and maps them to Tableau's internal type system.

Data Type Mapping

Metadata Operations Available on the Data Source Page

• ✓ Change Data Type — Click the type icon in the column header to re-cast a field (e.g., change a ZIP code from Number to String to prevent aggregation).
• ✓ Rename Field — Double-click a column header to assign a human-readable alias without altering the underlying source column name.
• ✓ Hide Field — Right-click and select Hide to remove a field from the Data pane on worksheets while retaining it in the data model.
• ✓ Assign Geographic Role — Set a string or number field to a geographic role (Country, State, City, ZIP Code, Latitude, Longitude) to enable automatic geocoding on maps.
• ✓ Set Default Properties — Configure default aggregation (SUM, AVG, COUNT, etc.), number format, color, and comment for a field. These defaults propagate to every worksheet that uses this data source.

The Data Source page's canvas operates on two distinct layers that together form Tableau's data model. The logical layer is the default view where you create relationships between tables — these are flexible, context-aware associations that Tableau resolves at query time based on which fields you use in a visualization. The physical layer is accessed by double-clicking any logical table and is where you define traditional SQL joins (inner, left, right, full outer) and unions. Understanding when to use each layer is one of the most impactful decisions you make on the Data Source page.

A key architectural insight is that the logical layer defers join execution until a visualization is rendered, meaning Tableau generates the most efficient SQL for each specific combination of fields. If a bar chart uses only fields from the Orders table, Tableau will not join to Customers at all, avoiding unnecessary row multiplication. The physical layer, by contrast, materializes the join immediately — useful when you need to union yearly tables or perform a lookup join within a single logical table but inappropriate when the tables have different granularities (e.g., one row per order vs. one row per customer).

Consider a scenario where you are building a sales dashboard and need to connect to a PostgreSQL database containing four tables: orders, order_items, products, and customers. The orders table has columns order_id (INT), customer_id (INT), order_date (DATE), and zip_code (INT). Walk through the full Data Source page configuration.

One of the most consequential decisions made on the Data Source page is choosing between relationships (logical layer) and joins (physical layer). While both mechanisms combine data from multiple tables, they differ fundamentally in when and how the combination occurs, and these differences have profound implications for data accuracy and query performance.

The Data Source page is not merely a static configuration screen — it connects directly to Tableau's broader data management architecture. The choices you make here cascade into performance characteristics, refresh schedules, and governance workflows across the Tableau ecosystem.

As you advance in Tableau proficiency, the Data Source page becomes the control plane for increasingly sophisticated data architectures. Published data sources, for instance, allow a data engineering team to curate metadata, set default aggregations, and certify a data source so that downstream analysts work from a single source of truth. Virtual connections extend this further by separating connection credentials from data source definitions, enabling row-level security policies that follow the data regardless of which workbook consumes it. All of these capabilities trace back to the foundational metadata configuration you learn on the Data Source page.