You want to display sales data grouped by Region, then by Country, and finally by City. Which visual layout is best suited for this hierarchical display?
Think about which visual allows expanding and collapsing hierarchical levels.
A Matrix visual supports hierarchical rows and allows users to drill down or expand levels, making it ideal for showing Region > Country > City.
Given a sales table with columns: SalesAmount, ProductCategory, and Date, which DAX measure returns total sales ignoring any filter on ProductCategory but respects other filters?
Total Sales Ignore Category = CALCULATE(SUM(Sales[SalesAmount]), ALL(Sales[ProductCategory]))
Use a function that removes filters only on ProductCategory.
ALL(Sales[ProductCategory]) removes filters on ProductCategory only, so the measure sums all sales ignoring that filter but respects others.
You have a matrix visual showing monthly sales for 50 products over 3 years. The visual is slow to load. What is the best way to improve performance?
Measures are generally more efficient than calculated columns for aggregations.
Using measures leverages DAX engine optimizations and reduces data model size, improving matrix visual performance.
A matrix visual shows sales by Region and Product. The subtotal for Region shows zero instead of the sum. Which DAX measure causes this issue?
Sales Amount = IF(HASONEVALUE(Product[ProductName]), SUM(Sales[Amount]), 0)
Sales Amount = IF(HASONEVALUE(Product[ProductName]), SUM(Sales[Amount]), 0)Check what HASONEVALUE returns when multiple products are in context.
HASONEVALUE returns false for subtotal rows with multiple products, so the measure returns 0 instead of sum, causing zero subtotal.
Which practice improves accessibility for users navigating a matrix visual with keyboard and screen readers?
Think about how screen readers identify table structure.
Descriptive headers and ARIA labels help screen readers understand the matrix layout, improving accessibility.