3.1 Data Types, Roles, Organization & Default Properties

3.1 Data Types, Roles, Organization & Default Properties

A field has several independent properties in Tableau: its stored data type, analytical role, discrete or continuous behavior, aggregation, geographic role, display name, and default formatting. Diagnose each property separately. Turning a field blue does not make it a string, and converting a field to a dimension does not change the values stored by the source.

Data types

Common Tableau data types include string, number (whole), number (decimal), Boolean, date, date and time, geographic, and spatial values. A type mismatch can break joins, produce null calculations, or prevent a field from receiving a geographic role. Use the type icon in the Data pane or Data Source page to inspect and change a type when conversion is valid.

Parsing deserves special care. A value such as 03/04/2026 is ambiguous without a known locale. An identifier such as 00127 should usually remain a string so its leading zeros survive. Converting bad strings with INT, FLOAT, DATE, or DATEPARSE can yield null; test rejected values rather than silently treating them as missing. Boolean calculations return TRUE or FALSE and are useful for filters, flags, and dynamic zone visibility.

Dimensions, measures, discrete, and continuous

A dimension slices or identifies marks; a measure is normally aggregated. Discrete fields create headers and distinct categories. Continuous fields create axes and a continuous range. These concepts cross one another: a measure can be discrete, and a date can be either a discrete date part or a continuous date value. The pill color reports discrete versus continuous, not dimension versus measure.

Tableau infers roles from source metadata, but an analyst can change them. A numeric customer ID is usually a dimension, not a quantity to sum. A discrete profit band is still derived from a measure. Choose the role that expresses the analytical question.

Geographic roles

Assign a geographic role when values represent supported locations such as Country/Region, State/Province, City, Postal Code, or an appropriate code. The role adds generated Latitude and Longitude fields and enables geocoding; it does not alter source values. Ambiguous place names may require Edit Locations to specify a country or region. Custom latitude and longitude fields can be assigned their respective roles. Verify unknown and ambiguous locations rather than accepting a misleading map.

Names, aliases, and field organization

Renaming a field changes its Tableau display name without renaming the source column. An alias changes how members of a discrete dimension are displayed—for example, showing Corporate instead of CORP—without changing the underlying member. Aliases are not a data-cleaning substitute when the source keys truly need correction.

Folders organize fields in the Data pane. Choose Group by Folder, create meaningful folders such as Customer, Orders, and Calculations, and place fields in them. Folders affect authoring navigation, not the data model or query results. For reusable drill paths, create a hierarchy by dragging one field onto another or by choosing Create > Hierarchy, name it, and order fields from broad to detailed, such as Region, State, City. Authors then use the plus and minus controls to drill.

Default properties

Default properties make repeated view construction consistent. Depending on the field, Tableau supports defaults such as aggregation, number format, date format, color, shape, sort, comment, geographic role, and fiscal-year start. Setting Sales to a currency format changes its display, not its stored numeric value. Setting a measure's default aggregation to AVG changes what newly created pills use; an existing pill can still be changed manually.

Aliases apply to members of a discrete dimension. Number formats apply presentation rules such as decimal places, units, percentages, and currency. A default sort determines the normal member order but can be overridden in a worksheet. A comment records business meaning and appears to authors in the Data pane. Treat defaults as governed metadata that saves work, not as security controls.

Data quality review

Before analysis, profile the fields against three practical dimensions:

• Completeness: Are required values present? Count nulls and check whether missing rows or periods exist.
• Consistency: Are categories, units, formats, and key types represented the same way across sources?
• Accuracy: Do values reconcile to an authoritative control total or accepted business rule?

A field can be complete but inaccurate, or accurate for present rows while missing an entire region. Record the rule and the denominator used. For example, a 2% null rate means little unless the analyst knows whether null is acceptable and which population was tested.

Safe configuration sequence

1. Inspect sample values and source metadata.
2. Set the correct data type without losing significant formatting such as leading zeros.
3. assign dimension or measure and discrete or continuous behavior based on the question.
4. Apply geographic roles and resolve unknown locations.
5. Rename fields, define aliases, comments, formats, and aggregations.
6. Organize fields into folders and construct meaningful hierarchies.
7. Reconcile completeness, consistency, and accuracy before publishing.

The core distinction is between data meaning and display behavior. A format, alias, folder, or hierarchy improves authoring and communication but does not repair incorrect source data.