Forum Discussion
Helper IISingle date slicer to filter multiple date tables
Shouldn't your slicer be based on the dates in a Date Table where the Date field is related to all of the relevant date fields in your other tables?
Helper IISorry, I meant to include this in my reply yesterday. Here is a screenshot of that part of my relationship diagram. You can see the succesful relationship between Calendar and FinalInspections on the left but the relationship between Calendar and RoughInspections failed.
Community ChampionWhat is the relationship between Job_info and RoughInspections?
There is some other relationship in your model that is causing the Calendar to RoughInspections to be inactive.
You can, of course, still use it. You just need to use the USERELATIONSHIPS() function in a filter, but that shouldn't be necessary in this case. usually it is when you have 2 or more relationships between 2 tables and you need to swich which realtionship. See this article for more info on that, but I'd still be interested to know what other relationships you have set up are causing the one you tried to go inactive.
Here is an article on how you can create ambiguous relationships that will cause a relationship to go inactive like that as well.
- jscottNRG
Here is the relationship between RoughInspections and Job_info. Thanks for the links with more info on correct relationship setup!
- edhans
I think the issue you are running into is you have multiple FACT tables (data tables, like sales data, or inspection data) and you are using bi-directional filtering on some of those tables. It will cause relationships to go inactive.
Not the end of the world. Either change the bi-directional crossfiltering settings to single direction and enable the relationship to the date table, or use the USERELATIONSHIP() filter function inside of a CALCULATE() when you need to use it. But I don't think you can do that for a slicer, as slicers depend on relationships and cannot use measures.So maybe turn all bi-directional into single, activate that date relationship, then look at all of your other data and see what broke. If you have some measures that aren't right because of the removeal of bi-directions, you can use the CROSSFILTER() filter function inside of a CALCULATE() function to force that measure to use bi-directional filtering without affecting the entire model's relationships.