Forum Discussion
Measure breaks join
I have two very simple tables that I am using to check this issue: a table of orders with value and sign (credit or debit) and a table of invoices with the ref order number and the sale value
I join them on order number
I created a Table visual with Order number from the Order Table and IORDNO from the Invoice table and sum the value in the Order Table.
Then I filter to exclude entries where the order number from the order table is blank (i.e. invoices that do not match any of the orders).
Which behaves as expected.
Then I create a measure: Measure = SUMX(orders,[Value] * [Sign])
and add this as a column in the table and the relationships is broken.
How can I have non matching order numbers in the Table when there is a join on this field and why does the measure cause this?
Hi RobertSlattery, if you change the "cross filter direction" from Single to Both, it should fix the problem.
4 Replies
- DAX0110Resolver V
Hi RobertSlattery, if you change the "cross filter direction" from Single to Both, it should fix the problem.
- RobertSlatteryResponsive Resident
Thanks, I thought I tried that permutation, apparently not.
Admittedly, I had the direction running from invoices to orders (the columns were running from order to invoice), but even if I reverse the direction, the same behaviour persists.
Why? Why does it behave differently if I include a Measure?
What is the logic behind this behaviour? It doesn't make any sense to me...
- DAX0110Resolver V
Hi RobertSlattery, this is one of those meaning-of-life things isn't it? I thought I understood it but everytime I come across this problem I have to spend some time thinking about it.
If you want to delve into the real reason, you can begin with this blog post :
https://powerpivotpro.com/2017/08/autoexist-cross-table-filtering/