Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Really strange issue which I'm at wits end trying to figure out. When I apply a filter to a field called "Source" for anything (e.g. "Electronic"), my set analysis measures ignore the filter. Example when filter is applied:
Sum({<Source={"Paper"}>}jobs) = 593k
Sum(jobs) = 0
Among other things I've tried deleting the source tables and re-adding with different field names and tried using a different field which creates the same problem. If I create a second field in the table with the exact same values (e.g. "Source2") with exact same values then filter on in the sheet instead, it will evaluate correctly (Sum({<Source={"Paper"}>}jobs) = 0)
Any ideas at what might be causing this and how I can avoid it?
Change your expression to this
Sum({<Source *= {"Paper"}>} jobs)
Added * before the equal sign. which just means that honor the selection in Source field and basically show the intersection between what is selected and Source = Paper. So, if Paper is not selected the expression should just show 0 now.
Some images to help show what is happening:
I don't understand what is causing the application to evaluate to not evaluate Paper Soruce = 0 when a different source is selected. This issue results in it evaluating the number of paper source jobs being greater than the number of all jobs:
Change your expression to this
Sum({<Source *= {"Paper"}>} jobs)
Added * before the equal sign. which just means that honor the selection in Source field and basically show the intersection between what is selected and Source = Paper. So, if Paper is not selected the expression should just show 0 now.
Thanks Sunny - never realised * was required for honoring the intersection. Works perfectly!
Cheers