Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Join us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.

Reply
ElevonTeam
New Member

Filter in calculated column in direct query mode

I have a calculated column which filter data on the basis of other column. the calculation is working fine in import mode of source but failing in direct query mode.

 

Can anyone please suggest a workaround?

1 ACCEPTED SOLUTION
Anonymous
Not applicable

Hi @ElevonTeam,

 

>> the calculation is working fine in import mode of source but failing in direct query mode.

Current there are a few limitations to use calculation in directquery mode, so you can't use calculated column to achieve your requirement.

 

Reference link:

Using DirectQuery in Power BI

 

  • Limitations in calculated columns: Calculated columns are limited to being intra-row, as in, they can only refer to values of other columns of the same table, without the use of any aggregate functions. Additionally, the DAX scalar functions (such as LEFT()) that are allowed will be limited to those which can simply be pushed to the underlying source, hence will vary depending upon the exact capabilities of the source. Functions that are not supported will not be listed in autocomplete when authoring the DAX for a calculated column, and would result in an error if used.

 

>>Can anyone please suggest a workaround?

In my opinion, I'd like to suggest you use measure to instead.

 

Regards,

Xiaxoin Sheng

View solution in original post

3 REPLIES 3
Anonymous
Not applicable

Hi @ElevonTeam,

 

>> the calculation is working fine in import mode of source but failing in direct query mode.

Current there are a few limitations to use calculation in directquery mode, so you can't use calculated column to achieve your requirement.

 

Reference link:

Using DirectQuery in Power BI

 

  • Limitations in calculated columns: Calculated columns are limited to being intra-row, as in, they can only refer to values of other columns of the same table, without the use of any aggregate functions. Additionally, the DAX scalar functions (such as LEFT()) that are allowed will be limited to those which can simply be pushed to the underlying source, hence will vary depending upon the exact capabilities of the source. Functions that are not supported will not be listed in autocomplete when authoring the DAX for a calculated column, and would result in an error if used.

 

>>Can anyone please suggest a workaround?

In my opinion, I'd like to suggest you use measure to instead.

 

Regards,

Xiaxoin Sheng

v-caliao-msft
Microsoft Employee
Microsoft Employee

@ElevonTeam,

 

I have create a sample Power BI report which connect to SQL Server database by using DirectQuery mode, and then create a calculate column. I can use this column in Slicer and use it to filter data without any questions.

 

So could you please provide us more detail information, so that we can make further analysis. You can upload a pbix file to Onedrive or any web storage and share the link. Do mask sensitive data before uploading.

 

Regards,

Charlie Liao

Try recreating the the complete table brought through by direct mode using dax...

Create new table

XTable = SUMMARIZE(Table,Header a, Heade B,...

)

Then add a calclated column to it what you need.

The calculated column on a Direct query table becomes a measure rather than a calculated column

Helpful resources

Announcements
Join our Fabric User Panel

Join our Fabric User Panel

This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.

June 2025 Power BI Update Carousel

Power BI Monthly Update - June 2025

Check out the June 2025 Power BI update to learn about new features.

June 2025 community update carousel

Fabric Community Update - June 2025

Find out what's new and trending in the Fabric community.