Why table calculations compute across the view in Tableau - Quick Recap

Recall & Review

beginner

What does it mean that table calculations compute across the view in Tableau?

It means that table calculations use the data as it appears in the current visualization, considering the arrangement of rows and columns to perform calculations.

beginner

Why do table calculations depend on the layout of the view?

Because table calculations operate on the displayed data, their results change if the rows or columns in the view change, as they compute based on the position of data in the view.

intermediate

How can you control the direction of a table calculation in Tableau?

You can specify the direction (across rows, down columns, or specific dimensions) in the 'Compute Using' option to control how the calculation moves across the view.

intermediate

What happens if you change the dimensions in the view after applying a table calculation?

The table calculation result may change because it recalculates based on the new arrangement of data in the view.

beginner

Give a real-life example of why table calculations compute across the view.

Imagine a sales report showing monthly sales by region. A running total table calculation sums sales across months as shown in the view. If you add or remove regions or months, the running total changes because it computes across the visible data.

In Tableau, what does a table calculation compute across?

A The original data source only

B The data as arranged in the current view

C Only the first column of data

D Random rows in the data

Table calculations compute based on how data is arranged in the current view, not just the original data source.

Which option lets you change how a table calculation moves across the view?

A Compute Using

B Filter Shelf

C Data Source

D Marks Card

The 'Compute Using' option controls the direction and dimensions the table calculation uses.

If you add a new dimension to the view, what happens to an existing table calculation?

A It recalculates based on the new view layout

B It stays the same

C It deletes automatically

D It ignores the new dimension

Table calculations recalculate because they depend on the current view's layout.

Why might a running total change when you rearrange columns in Tableau?

A Because the data source changed

B Because Tableau caches results

C Because filters reset

D Because table calculations compute across the view layout

Running totals depend on the order and arrangement of data in the view.

Which of these is NOT true about table calculations in Tableau?

A They depend on the view's layout

B They can be customized with 'Compute Using'

C They always use the original data source order

D They recalculate when the view changes

Table calculations do not always use the original data source order; they use the order in the current view.

Explain why table calculations in Tableau compute across the view and how this affects their results.

Think about how the data is shown in the visualization and how that changes the calculation.

Describe a scenario where changing the dimensions in a Tableau view changes the result of a table calculation.

Consider a sales report with months and regions.

Practice

1. What does it mean when we say table calculations in Tableau "compute across the view"?

easy

A. They calculate values only from the original data source, ignoring the view.

B. They always compute totals without considering the layout.

C. They use the data visible in the current chart or table to perform calculations.

D. They only work on filtered data, not the entire view.

Solution

1. Step 1: Understand the meaning of "compute across the view"

   Table calculations use the data that is currently displayed in the view, not the entire data source.

2. Step 2: Relate to how Tableau uses visible data

   Since the calculation depends on the view, changing the layout or filters changes the calculation.

3. Final Answer:

   They use the data visible in the current chart or table to perform calculations. -> Option C

4. Quick Check:

   Table calculations depend on visible data [OK]

Hint: Table calculations use only data shown in the view [OK]

Common Mistakes:

• Thinking calculations use all data regardless of view
• Confusing table calculations with data source filters
• Assuming calculations ignore layout changes

2. Which of the following is the correct way to set the direction for a table calculation in Tableau?

easy

A. Right to Left

B. Compute Using > Table (Across)

C. Filter > Exclude

D. Data Source > Refresh

Solution

1. Step 1: Identify how to set calculation direction

   In Tableau, you set the direction by choosing 'Compute Using' and selecting options like 'Table (Across)'.

2. Step 2: Confirm correct syntax and option

   'Compute Using > Table (Across)' is the correct way to tell Tableau to calculate across the table horizontally.

3. Final Answer:

   Compute Using > Table (Across) -> Option B

4. Quick Check:

   Direction set by Compute Using [OK]

Hint: Use 'Compute Using' to set calculation direction [OK]

Common Mistakes:

• Confusing filter options with calculation direction
• Using data source refresh instead of compute using
• Selecting invalid directions like 'Right to Left'

3. Given a table with sales data by Region and Month, if a table calculation is set to compute using 'Table (Down)', what will it calculate?

medium

A. Sum of sales across all regions horizontally

B. Sum of sales only for the first month

C. Sum of sales ignoring the view layout

D. Sum of sales down each region column vertically

Solution

1. Step 1: Understand 'Table (Down)' direction

   'Table (Down)' means the calculation moves vertically down each column in the table.

2. Step 2: Apply to sales by Region and Month

   Since months are likely arranged down rows, the calculation sums sales down each region's column vertically.

3. Final Answer:

   Sum of sales down each region column vertically -> Option D

4. Quick Check:

   Table (Down) = vertical calculation [OK]

Hint: 'Table (Down)' means calculate vertically down columns [OK]

Common Mistakes:

• Thinking 'Table (Down)' calculates horizontally
• Ignoring the table layout and direction
• Assuming calculation ignores months

4. You set a table calculation to compute using 'Pane (Across)', but the results are not as expected. What is a likely cause?

medium

A. The calculation is computing only within each pane horizontally, but the view has no panes defined.

B. The data source is not connected properly.

C. The calculation is ignoring the pane boundaries and computing across the entire table.

D. The filter is excluding all data.

Solution

1. Step 1: Understand 'Pane (Across)' scope

   'Pane (Across)' computes horizontally but only within each pane, which is a section of the view.

2. Step 2: Check if panes exist in the view

   If the view has no panes (no partitioning), the calculation may behave unexpectedly because it expects pane boundaries.

3. Final Answer:

   The calculation is computing only within each pane horizontally, but the view has no panes defined. -> Option A

4. Quick Check:

   Pane scope needs panes in view [OK]

Hint: Check if panes exist when using 'Pane (Across)' [OK]

Common Mistakes:

• Assuming 'Pane (Across)' ignores pane boundaries
• Blaming data source connection for calculation issues
• Confusing filters with calculation scope

5. You want to calculate the running total of sales by Month within each Region in a view that shows Regions as rows and Months as columns. Which 'Compute Using' setting should you choose for the table calculation to work correctly?

hard

A. Pane (Across)

B. Pane (Down)

C. Table (Across)

D. Table (Down)

Solution

1. Step 1: Analyze the view layout

   Regions are rows, Months are columns, so months run horizontally across the view.

2. Step 2: Determine running total direction and scope

   Running total by Month within each Region means calculating horizontally across each pane (each Region is a pane).

3. Step 3: Choose correct 'Compute Using'

   'Pane (Across)' computes across columns within each pane (Region), which fits the requirement.

4. Final Answer:

   Pane (Across) -> Option A

5. Quick Check:

   Running total by Month across each Region = Pane (Across) [OK]

Hint: Match compute direction to months layout and pane to regions [OK]

Common Mistakes:

• Choosing 'Table (Across)' which ignores pane boundaries
• Using vertical directions when months are horizontal
• Not considering pane boundaries for regions