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
Anonymous
Not applicable

How to exclude one field from summarize columns but still include it in the query

Hi, 

 

I had to introduce the field [PlannedMigrationDay] in my query for the paginated report for the sole purpose of filtering the paginated report. 

 

This is the query: 

 

 

/* START QUERY BUILDER */
EVALUATE
SUMMARIZECOLUMNS(
    UserResponse[Batch],
    UserResponse[Response],
    UserResponse[PlannedMigrationDay],
    KEEPFILTERS( TREATAS( {"2"}, UserResponse[TenantID] )),
    KEEPFILTERS( TREATAS( {"4"}, UserResponse[QuestionID] )),
    "Responses", [Responses],
    "Responses %", [Responses %],
    "T-14", [T-14]
)
/* END QUERY BUILDER */

 

 

Now I have one problem: when I have two different migration dates, my results are summarized by the date of migration whereas before they were aggregated by distinct values.

 

Devices.png

I don't want my results to be aggregated by [PlannedMigrationDay]. How can I modify the query to avoid that, but still have that field in the dataset of my paginated report? 

 

Thanks in advance for the help! 

 

~Alienvolm

1 ACCEPTED SOLUTION

Hi @Anonymous ,

 

You don't want your value to be summarized by PlannedMigrationDay column , by you still want to show it in the output table, am I right?

 

You need also a aggregation function to your PlannedMigrationDay column like max or min, please try :

 

EVALUATE
ADDCOLUMNS(SUMMARIZECOLUMNS(
    UserResponse[Batch],
    UserResponse[Response],
    KEEPFILTERS( TREATAS( {"2"}, UserResponse[TenantID] )),
    KEEPFILTERS( TREATAS( {"4"}, UserResponse[QuestionID] )),
    "Responses", [Responses],
    "Responses %", [Responses %],
    "T-14", [T-14]
),"Date",CALCULATE(MAX(UserResponse[PlannedMigrationDay]),FILTER(UserResponse,UserResponse[Batch] = EARLIER(UserResponse[Batch])&&UserResponse[Response] = EARLIER(UserResponse[Response])))

 

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

 

Best Regards,

Dedmon Dai

View solution in original post

4 REPLIES 4
Fowmy
Super User
Super User

@Anonymous 

Use SELECTCOLUMNS table function to get only the columns that you need.

https://dax.guide/selectcolumns/


Did I answer your question? Mark my post as a solution! and hit thumbs up


Subscribe and learn Power BI from these videos

Website LinkedIn PBI User Group

Anonymous
Not applicable

Hi @Fowmy,

 

I can't figure outr for the life of me how to make SELECTCOLUMNS work together with SUMMARIZECOLUMNS. I tried all combinations and the query just doesn't work. 

 

With SELECTCOLUMNS only it works, but I see the single rows of the table, which is not what I need. I need all the fields summarized but not by UserResponse[PlannedMigrationDay]. 

 

I'm not an expert with DAX Queries, so any additional help would be really appreciated!

 

~Alienvolm

Hi @Anonymous ,

 

You don't want your value to be summarized by PlannedMigrationDay column , by you still want to show it in the output table, am I right?

 

You need also a aggregation function to your PlannedMigrationDay column like max or min, please try :

 

EVALUATE
ADDCOLUMNS(SUMMARIZECOLUMNS(
    UserResponse[Batch],
    UserResponse[Response],
    KEEPFILTERS( TREATAS( {"2"}, UserResponse[TenantID] )),
    KEEPFILTERS( TREATAS( {"4"}, UserResponse[QuestionID] )),
    "Responses", [Responses],
    "Responses %", [Responses %],
    "T-14", [T-14]
),"Date",CALCULATE(MAX(UserResponse[PlannedMigrationDay]),FILTER(UserResponse,UserResponse[Batch] = EARLIER(UserResponse[Batch])&&UserResponse[Response] = EARLIER(UserResponse[Response])))

 

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

 

Best Regards,

Dedmon Dai

Anonymous
Not applicable

Hi @v-deddai1-msft,

 

Thank you! 

 

That worked! 🙂

 

Alienvolm_0-1626451727918.png

~Alienvolm

 

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.