📈 Power BI DAX examples

SELECTCOLUMNS Examples in Power BI DAX

Create a table with selected/renamed columns. This page gives you the syntax, five practical business examples, common mistakes, and copy-ready DAX you can adapt for reports.

Updated 2026-06-125 business examplesCopy-ready DAX

💡 Ideas for You

Learning resources for Power BI measures, DAX patterns and reporting.

4 useful links

Some links in this section may be affiliate links. Choose only what is useful for your own work.

What SELECTCOLUMNS does

Create a table with selected/renamed columns. In Power BI, the key is not only the formula itself but how it behaves with slicers, relationships, visuals and totals.

Syntax or pattern

SELECTCOLUMNS(table, name, expression, ...)
✍️

5 practical business examples

1

SELECTCOLUMNS in a sales report

Create a table expression grouped by product.

Customer List = SELECTCOLUMNS(Customers, "ID", Customers[Customer ID], "Name", Customers[Customer Name])

Useful for calculated tables and advanced measures.

2

Add sales to customer list

Add a measure result to each customer row.

Customer List = SELECTCOLUMNS(Customers, "ID", Customers[Customer ID], "Name", Customers[Customer Name])

Good for analysis tables.

3

Select key columns

Create a narrow table for a calculation.

Customer List = SELECTCOLUMNS(Customers, "ID", Customers[Customer ID], "Name", Customers[Customer Name])

Use this to control table shape.

4

Top products table

Return only the highest selling products.

Customer List = SELECTCOLUMNS(Customers, "ID", Customers[Customer ID], "Name", Customers[Customer Name])

Useful in calculated tables and ranking patterns.

5

Compare missing products

Find products in one list but not another.

Customer List = SELECTCOLUMNS(Customers, "ID", Customers[Customer ID], "Name", Customers[Customer Name])

Useful for reconciliation checks.

Common mistakes to avoid

  • Using SELECTCOLUMNS before checking whether the data model has the right relationships and filter direction.
  • Writing one complex measure instead of creating simple base measures first.
  • Testing only at the total level and not checking row, category and date contexts.
  • Forgetting that slicers, visuals and relationships can all change the filter context.

FAQ

When should I use SELECTCOLUMNS in DAX?

Use SELECTCOLUMNS when the calculation pattern matches the business question and the result behaves correctly in the current filter context.

Why is my SELECTCOLUMNS measure returning the wrong total?

Most total issues come from row context, filter context, relationships, or using a column aggregation where an iterator or CALCULATE pattern is needed.

Can I use this SELECTCOLUMNS pattern in a calculated column?

Some patterns work in calculated columns, but most reporting calculations should be measures so they respond to slicers and report filters.