Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.
I am a bit confused by this.
It said when you use direct query it will optimize the TSQL generated if you add a calculated column in PowerBI on the table?
https://msdn.microsoft.com/en-us/query-bi/dax/combinevalues-function-dax
So , if I have a Table that needs to join on multiple columns /composite key (instead of one single column key) then using COMBINEVALUES will help PBI optimize the TSQL it generates when doing a join?
How do you do that if you are using Direct Query with OUT importing the data?
Where do you add this calculated column at?
If we have data like this: EventRoomSchedule table contains
Then have another table [EventSpeakersTimeAssigned] that shows the Even Speaker (speaker's name) and then Room# and Time to join them back to that table.
How do you handle that in DAX with COMBINEVALUES?
If I have a direct query (not import) I selected those tables in my data model... then what?
Solved! Go to Solution.
Hi @OneWithQuestion,
Just add a new column and establish the relationship. Do you any special requirements?
Best Regards,
Dale
Hi @OneWithQuestion,
Just add a new column and establish the relationship. Do you any special requirements?
Best Regards,
Dale
OH!
Well I feel foolish!
In my mind I thought it was not possible to just add a calculated DAX column to a table like that when using direct query.
That makes sense though, so the query engine will see that DAX column and use it accordingly when it you make queries against the tables?
Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!
Check out the October 2025 Power BI update to learn about new features.