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!Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes! Register now.
I know in some cases you have to expand the columns when doing a left outer join/merge but when doing a left anti join/merge I don't think expanding is required. Is this the best practice to follow? As when I did a left anti join i delete the table column instead of expanding it and the number of rows returned were as I expected.
Solved! Go to Solution.
Of coz the deletion of the merged column does the trick since there is nothing but nulls in the merged column from a left anti-join.
Thanks to the great efforts by MS engineers to simplify syntax of DAX! Most beginners are SUCCESSFULLY MISLED to think that they could easily master DAX; but it turns out that the intricacy of the most frequently used RANKX() is still way beyond their comprehension! |
DAX is simple, but NOT EASY! |
Of coz the deletion of the merged column does the trick since there is nothing but nulls in the merged column from a left anti-join.
Thanks to the great efforts by MS engineers to simplify syntax of DAX! Most beginners are SUCCESSFULLY MISLED to think that they could easily master DAX; but it turns out that the intricacy of the most frequently used RANKX() is still way beyond their comprehension! |
DAX is simple, but NOT EASY! |