Forum Discussion
Measure creates cartesian
What are you trying to do here? Where are the dim IDs coming from - the ones placed on rows and columns? It looks like you have dim ID coming from both tables in this visual. Why are you doing that and what do you expect to achieve? The dim ID from your fact table will not filter your dimension table. That is why you have a cartesean join
The two IDs on the visual are to demonstrate that the dimension filter is not passing to fact. Even if I take the id's off, the cartesian effect stays there - without showing the id's the resultset is even more confusing.
The production version of this looks to MaxDate to see if the last date in filter context is in the future or not, and toggles the calculation returned, but comparing MaxDate to TODAY() causes the table to explode. Doesn't matter if it's table or matrix, doesn't matter if dimid's are actuall on the visual, the resultset in visual goes totally haywire and doesn't respect the filter from dim.DimId slicer.
Give it a try - those two tables and a handful of values are all you need to get weirdness. I wish this forum allowed me to upload an example file.