Trim and clean text in Power BI - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ dax_lod_result

intermediate

Removing Extra Spaces with TRIM

Given a column 'CustomerName' with values like ' John Doe ', which DAX expression correctly removes all leading and trailing spaces but keeps single spaces between words?

A TRIM(CLEAN('Table'[CustomerName]))

B CLEAN('Table'[CustomerName])

C SUBSTITUTE('Table'[CustomerName], " ", "")

D TRIM('Table'[CustomerName])

💡 Hint

Think about which function removes spaces only at the start and end, not inside the text.

TRIM removes extra spaces at the start and end but keeps single spaces between words. CLEAN removes non-printable characters but does not trim spaces. SUBSTITUTE removes all spaces, which is not desired here.

❓ visualization

intermediate

Visualizing Cleaned Text Length

You want to create a Power BI card visual that shows the average length of cleaned product descriptions. Which measure correctly calculates the average length after trimming and cleaning the 'ProductDescription' column?

A AverageLength = AVERAGEX('Products', LEN('Products'[ProductDescription]))

B AverageLength = AVERAGEX('Products', LEN(TRIM(CLEAN('Products'[ProductDescription]))))

C AverageLength = AVERAGE(LEN(TRIM('Products'[ProductDescription])))

D AverageLength = AVERAGEX('Products', LEN(CLEAN('Products'[ProductDescription])))

💡 Hint

Remember to apply both TRIM and CLEAN before measuring length, and use AVERAGEX to iterate rows.

Option B correctly applies CLEAN and TRIM to each row's text, then measures length, and averages over all rows. Option B misses cleaning and trimming. Option B uses AVERAGE on a column of lengths which is invalid. Option B misses trimming.

❓ data_modeling

advanced

Handling Non-Printable Characters in Data Model

You notice your customer feedback text contains hidden non-printable characters causing filtering issues. What is the best approach to clean this text in your Power BI data model?

A Create a calculated column using CLEAN and TRIM functions on the feedback text.

B Apply only TRIM function to remove spaces from the feedback text.

C Use SUBSTITUTE to replace spaces with empty strings in the feedback text.

D Ignore cleaning and handle issues in report filters.

💡 Hint

Think about removing both non-printable characters and extra spaces.

CLEAN removes non-printable characters, and TRIM removes extra spaces. Using both ensures clean text for filtering. SUBSTITUTE removing spaces breaks words. Ignoring cleaning causes persistent issues.

🔧 Formula Fix

advanced

Debugging Unexpected Spaces in Text Output

A measure uses this DAX: CleanName = TRIM(CLEAN('Customers'[Name])) but the report still shows extra spaces inside names like 'John Doe'. What is the cause?

Power BI

CleanName = TRIM(CLEAN('Customers'[Name]))

A The column 'Name' contains tabs that CLEAN cannot remove.

B CLEAN does not remove spaces, so extra spaces remain inside the text.

C TRIM only removes leading and trailing spaces, not multiple spaces inside the text.

D The measure syntax is incorrect and causes errors.

💡 Hint

Consider what TRIM does and does not do.

TRIM removes spaces only at the start and end of text, not multiple spaces between words. CLEAN removes non-printable characters but not extra spaces. The syntax is correct. Tabs are removed by CLEAN.

🧠 Conceptual

expert

Best Practice for Cleaning Text in Large Datasets

In a large Power BI dataset, which approach is best to efficiently clean text columns by removing non-printable characters and trimming spaces without slowing report performance?

A Perform text cleaning in the data source or Power Query before loading data into the model.

B Use calculated columns with CLEAN and TRIM in the data model for all text columns.

C Apply CLEAN and TRIM in every measure that uses text columns dynamically.

D Ignore cleaning and rely on report users to handle text inconsistencies.

💡 Hint

Think about where cleaning is most efficient: before or after loading data.

Cleaning text before loading reduces model size and improves performance. Calculated columns and dynamic cleaning in measures increase model complexity and slow reports. Ignoring cleaning causes user confusion.