Calculated Tables and Their Relationship to the Data Model

Calculated Tables and Their Relationship to the Data Model

Calculated tables can be connected or disconnected, depending on how you design and use them.

1. Connected Calculated Tables

These are calculated tables that are linked to other tables in the model through relationships.

They behave like normal tables in your data model.

Example: Connected Table

MonthlySales =
SUMMARIZE(
    Sales,
    Sales[Month],
    "Total Sales", SUM(Sales[Revenue])
)

Then, you can create a relationship between MonthlySales[Month] and your Date[Month] column.

Use case: You want to simplify visuals by summarizing monthly data but still want filters (like Date or Region) to apply.

2. Disconnected Calculated Tables

These are not connected to other tables by relationships — on purpose.

They’re mainly used for user interface elements, custom slicers, or what-if analysis.

Example: Disconnected Table (Common Use Case)

DiscountRate =
DATATABLE(
    "Discount", FLOAT,
    {
        {0.00},
        {0.05},
        {0.10},
        {0.15},
        {0.20}
    }
)

This table is disconnected — it doesn’t link to any other table.

You might use it with a measure like:

Adjusted Sales =
SUM(Sales[Revenue]) * (1 - SELECTEDVALUE(DiscountRate[Discount]))

Use case:

When a user selects a discount rate from a slicer, it dynamically changes the measure result — but doesn’t filter any table.

3. Why Many Calculated Tables Are Disconnected

• They’re often used for parameter selections (like “What-if analysis”).
• They help control measures dynamically without affecting model relationships.
• They act as helper tables to power visual interactions.

That’s why you often hear that “calculated tables are mostly disconnected” — because in practice, many of them are built for this purpose.

4. Quick Summary

In Short

• Not all calculated tables are disconnected.
• But many are intentionally left disconnected for control, simulation, and parameter selection purposes.