How to utilise USERELATIONSHIP for multiple dates in multiple tables from a Date table?

[Anonymous]

Hello there, I have three different dates each in different tables that I am currently trying to use. I have created a Date table and I want the date table to use the Created Time dates from the Deals, Purchase Orders and Invoices tables (columns needed are marked red in the image below):

However, due to how many tables and relationships I have, I can only have one relationship activated for the Date table. However, I know that inactive relationships can be utilised with the USERELATIONSHIP() function. 

How would I be able to use this function for a date slicer that filters all these three dates through the date table simultaneously? (Slicer example shown below): 

So when I click on any of the buttons it will show me the relevant date for Invoices, Purchase Orders and Deals all at the same time (that's what I'm trying to achieve through USERELATIONSHIP). Any help would be appreciated. 

[amitchandak]

@Anonymous , these join are inactive because of other bi-directional joins. Each table you can have one active join.

Make all 1-M join from dimension to fact -> single direction.

And then try to activate these joins

[Anonymous]

@amitchandak I do understand that, but I can't do that in this case because I need to filter in multiple directions in my dashboard and I have 10 tables that are all linked together. I've tried making them all 1-M and one-directional but then I can't use any of the filter options that I want to use. 

It's quite complex to explain. But this is why I was hoping I could use USERELATIONSHIP to solve this problem. 

[amitchandak]

@Anonymous , USERELATIONSHIP activate alternate join, so I doubt that is the case here. It inactive because there are two paths.

You can selectively disable bi-directional

To filter a slicer you can use measure from one or more facts and check for nonblank in the visual level filter

countrows(Fact)

or

countrows(Fact) + countrows(fact2)

[Anonymous]

@amitchandak I'm not sure I understand what you're saying about slicers? 

To explain, I have a Customer slicer (a search box) and once a Customer is selected, that filters other slicers such as Deals, so relevant Deals show up for that Customer. And in Deals and Customers there are invoices, purchase orders and other stuff that are filtered through it. 

I need to have bi-directional relationships because of this, otherwise, I can only filter one way and there is limitations. For example, if I make everything single direction, if I search the Customer slicer, no Deals will show up because the relationship is lost between them, since they have to go through multiple tables first.