Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!
I am not sure quite how to word this. This problem is showing up for every visual using this field, and measures as well, but this is the easiest way to see where something is wrong.
A basic table visual, showing results from two related tables. Sales, one order per row, and CustomerNo, one per order.
If my table consists of Order#, CustomerNo, I get exactly what I would expect. Each order number, and each CustomerNo that goes with that order number, one per line.
If I change CustomerNo to COUNT of CustomerNo, just using the visual's built in function, I get the total count for all CustomerNos on each and every line. There is only one per row in the dataset, but I am getting 194,000 per line.
Now my ultimate goal is not "Per order,", but based on a date range, Sales territory, etc . It doesn't matter, I get a count of ALL customers. However, the relationship is there., as the instance that displays without a count works just fine. Filters do not affect the total number. Build a measure to do the counting, same results.
Where should I be looking?
Phil
Solved! Go to Solution.
Hi @PhilSmith ,
It's hard to say without looking at your model, but to me this sounds like a relationship issue.
Try setting the crossfilter direction set on your relationship between the sales and customers tables to "Both" (it is probably at single by default).
Note that this is NOT a recommended practice long-term, but it can help us diagnose what's going on. If that fixes the issue, then you should set the filter direction back to "Single" and develop your COUNT measure using a CROSSFILTER calculate modifier to temporarily set the filter direction between those tables to BOTH.
The issue is that in your current scenario, you are effectively asking the "Sales" table to filter the "Customer" table, which it cannot do due to the filter direction.
Hi @PhilSmith ,
It's hard to say without looking at your model, but to me this sounds like a relationship issue.
Try setting the crossfilter direction set on your relationship between the sales and customers tables to "Both" (it is probably at single by default).
Note that this is NOT a recommended practice long-term, but it can help us diagnose what's going on. If that fixes the issue, then you should set the filter direction back to "Single" and develop your COUNT measure using a CROSSFILTER calculate modifier to temporarily set the filter direction between those tables to BOTH.
The issue is that in your current scenario, you are effectively asking the "Sales" table to filter the "Customer" table, which it cannot do due to the filter direction.
User | Count |
---|---|
141 | |
113 | |
104 | |
78 | |
64 |
User | Count |
---|---|
136 | |
125 | |
107 | |
70 | |
61 |