Forum Discussion
Measure not calculating all rows on a table
- 4 years ago
I got it to work correctly by changing the relationship between the two tables to a One to Many (the slicer date calendar being the one).
Now that I've copied the technique to the actual project I'm working on, it yields mixed results - as you can see from the below screenshot, some rows that should have 1s have 0s, even when they have the identical start/end dates as rows with 1s. Do you have any idea what's causing this?
Thanks
The Start and End dates are the time frames for the projects, they aren't calculated and don't follow a pattern, they're human input.
I know. But still you can add them as Measures using SELECTEDVALUE
- JB4 years ago
Helper II
I got it to work correctly by changing the relationship between the two tables to a One to Many (the slicer date calendar being the one).
Now that I've copied the technique to the actual project I'm working on, it yields mixed results - as you can see from the below screenshot, some rows that should have 1s have 0s, even when they have the identical start/end dates as rows with 1s. Do you have any idea what's causing this?
Thanks
- JB4 years ago
Helper II
Sorry, I thought SELECTEDVALUE only worked on fields that were incorporated into a Slicer.
I tried this though and it returned all 0s unfortunately.
- tamerj14 years ago
Community Champion
The problem with the bi-directional relationship. Now try to CROSSFILTER The relationship to NONE
CLACULATE(your expression, CROSSFILTER ( coulmn name table1, coumn name table2, NONE))
- JB4 years ago
Helper II
Like this? It still isn't working, sorry.
- tamerj14 years ago
Community Champion
Don't use variables. Ise the measures directly inside calculate and remove ALL
- JB4 years ago
Helper II
Still no success 😞