Why table calculations compute across the view in Tableau - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify how table calculations compute across the view in Tableau.

Tableau

WINDOW_SUM(SUM([Sales])) [1]

Drag options to blanks, or click blank then click option'

AOVER()

BPARTITION BY [Region]

CORDER BY [Date]

DINCLUDE [Category]

Attempts:

3 left

💡 Hint

Common Mistakes

Using PARTITION BY which segments data instead of computing across the whole view.

Using ORDER BY which sorts data but does not define the computation scope.

In Tableau, table calculations compute across the view by default using the OVER() function, which means they consider the entire partition or view.

2fill in blank

medium

Complete the code to calculate a running total that computes across the view.

Tableau

RUNNING_SUM(SUM([Profit])) [1]

Drag options to blanks, or click blank then click option'

AOVER()

BPARTITION BY [Category]

CORDER BY [Region]

DWINDOW_AVG([Profit])

Attempts:

3 left

💡 Hint

Common Mistakes

Using PARTITION BY which limits the calculation to segments.

Using WINDOW_AVG which calculates average, not running total.

The OVER() function allows the running total to compute across the entire view without partitioning.

3fill in blank

hard

Fix the error in the table calculation to compute percent of total across the view.

Tableau

SUM([Sales]) / [1]

Drag options to blanks, or click blank then click option'

ATOTAL(SUM([Sales]))

BRUNNING_SUM(SUM([Sales]))

CWINDOW_SUM(SUM([Sales]))

DSUM([Sales])

Attempts:

3 left

💡 Hint

Common Mistakes

Using TOTAL which is a quick table calculation but may not work in all contexts.

Dividing by SUM([Sales]) which is the current row's value, not the total.

The WINDOW_SUM(SUM([Sales])) computes the total sales across the view, which is needed to calculate percent of total.

4fill in blank

hard

Fill both blanks to compute the moving average across the view ordered by date.

Tableau

WINDOW_AVG(SUM([Sales]), [1], [2])

Drag options to blanks, or click blank then click option'

A-2

B0

C2

D1

Attempts:

3 left

💡 Hint

Common Mistakes

Using only positive numbers which limits the window to future rows.

Using zero for both start and end which computes only the current row.

The moving average window is set from 2 rows before (-2) to 2 rows after (2) the current row, computing across the view ordered by date.

5fill in blank

hard

Fill all three blanks to compute the rank of sales across the view partitioned by region and ordered descending.

Tableau

RANK_UNIQUE(SUM([Sales]), [1], [2], [3])

Drag options to blanks, or click blank then click option'

A'desc'

B'asc'

C'region'

D'table'

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'asc' when descending order is needed.

Not partitioning by region which ranks all data together.

Using wrong scope like 'cell' instead of 'table'.

The rank is computed descending ('desc'), partitioned by 'region', and computed across the entire table ('table').

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