Documentation and naming conventions in Tableau - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use consistent naming conventions in Tableau?

Which of the following is the best reason to use consistent naming conventions for fields and worksheets in Tableau dashboards?

A It allows Tableau to generate more colors for charts.

B It automatically improves the dashboard loading speed.

C It helps team members quickly understand the purpose of each field and worksheet.

D It reduces the file size of the Tableau workbook.

💡 Hint

Think about how clear names help people working together.

Consistent naming helps everyone quickly know what each field or worksheet is for, making collaboration easier.

❓ lod_result

intermediate

Calculate total sales per region with clear naming

Given a Tableau data source with fields Sales and Region, which calculated field formula correctly sums sales per region with a clear and descriptive name?

Tableau

SUM([Sales])

A Name: Total Sales by Region; Formula: { FIXED [Region] : SUM([Sales]) }

B Name: SalesSum; Formula: SUM([Sales])

C Name: Sales per Region; Formula: SUM([Region])

D Name: TotalSales; Formula: SUM([Sales]) + [Region]

💡 Hint

Look for a formula that fixes the calculation by region and a descriptive name.

Option A uses a Level of Detail expression to sum sales per region and names the field clearly to reflect this.

❓ visualization

advanced

Best practice for dashboard element naming

Which naming practice for dashboard elements (worksheets, filters, parameters) improves accessibility and maintenance?

A Use descriptive names that include the element type and purpose, like 'Filter - Sales Region'.

B Use short codes like 'F1', 'P2' to keep names brief.

C Name all elements with the same generic name like 'Chart'.

D Use random names to avoid revealing data details.

💡 Hint

Think about how clear names help users and developers find elements easily.

Descriptive names that include type and purpose help users and developers understand and find dashboard elements quickly.

🔧 Formula Fix

advanced

Identify the naming issue in this Tableau calculated field

A Tableau calculated field is named totalSales but is used inconsistently in the workbook as TotalSales and total_sales. What problem can this cause?

A Tableau automatically corrects the names, so no problem occurs.

B The dashboard will load faster due to multiple names.

C The workbook file size will increase significantly.

D Tableau will treat these as different fields, causing confusion and errors.

💡 Hint

Consider how Tableau handles case sensitivity and naming consistency.

Tableau treats differently named fields as separate, which can cause confusion and errors if naming is inconsistent.

🎯 Scenario

expert

Designing a naming convention for a large Tableau project

You are leading a large Tableau project with multiple developers. Which naming convention strategy best supports collaboration, version control, and easy maintenance?

A Prefix all calculated fields with developer initials and date, e.g., 'JS_202406_TotalSales'.

B Use descriptive names including element type, purpose, and version, e.g., 'Calc_TotalSales_v2'.

C Name fields only by their data source column names without modification.

D Use a flat naming style with no prefixes or suffixes to keep names short.

💡 Hint

Think about clarity, versioning, and teamwork in naming.

Including element type, purpose, and version in names helps teams track changes and understand field roles clearly.