Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Sign up nowGet Fabric certified for FREE! Don't miss your chance! Learn more
Hi,
I am trying to run a query where the I can see all the orders from table 1 that exist in table 2 where the order status does not match. Please see example of tables
Table 1
| Order No | Order Status |
| 1234 | Resolved |
| 1235 | Pending |
| 1236 | Open |
| 1237 | Resolved |
Table 2
| Order No | Order Status |
| 1234 | Open |
| 1235 | Resolved |
| 1236 | Pending |
| 1237 | Resolved |
@PowerBI please can someone help? I have tried doing a merge ant left query but this gives me only the records in the first table that do not exisit in the second table.
Solved! Go to Solution.
Hi @Anonymous ,
Select the Order No column of the two tables to merge.
Then select the required field and expand it.
Finally add a conditional column
Best Regards,
Stephen Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @Anonymous ,
Select the Order No column of the two tables to merge.
Then select the required field and expand it.
Finally add a conditional column
Best Regards,
Stephen Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thanks - also do I need to use order no and order status as both the keys to join?
No, use only order no as key to join the two tables.
| 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! |
Thanks. how do I see the different order status values from both tables? Do I need to expand th query to show status prefixed ?
And I need to count of all the mismatch records so would this be the correct way Total Mismatch Orders:=COUNTROWS(table1)
Table1 ( left outer join ) Table2
instead of 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! |
If you love stickers, then you will definitely want to check out our Community Sticker Challenge!
Check out the January 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 13 | |
| 11 | |
| 11 | |
| 8 | |
| 6 |