Issues with slicer not correctly applying across appended data

[samw5]

I'm fetching data from Azure in several queries. 
That data is getting appended into 2 single queries, and am able to see it while browsing the raw table.

The 2 queries are linked and both contain a field for a tenantID.

I created a custom query/table that contains the tenantID and matching tenantName.

I am trying to have a slicer to be able to select the tenantName and filter out the correct tenantID from the main imported and appended queries.

This seems to be working fine on the main data (from the initial query) but anything that's appended doesn't get correctly filtered.

The second relationship is currently set to Many to Many, Single (Tenant filters Windows Updates). 
I've tried playing around with the options but somehow cannot get it to work.

This is what the table view looks like.

[richbenmintz]

Hi @samw5 ,

It looks like you need to relate the tenant dimension to you two fact tables and remove the relationship between the 'Missing KBs' and 'Windows Updates' tables. the relationship between the two facts will be materialized through the shared relationship to the tenants dimension. 

Make Sense?

Hope this Helps,
Richard
Did I answer your question? Mark my post as a solution!
Did my answers help arrive at a solution? Give it a kudos by clicking the Thumbs Up!

[samw5]

Tried that... filters work however I'm missing the information with computer data from the missing KBs table.

[richbenmintz]

Hi @samw5,

Why not create a computer dimension and join that to the two facts

Hope this Helps,
Richard
Did I answer your question? Mark my post as a solution!
Did my answers help arrive at a solution? Give it a kudos by clicking the Thumbs Up!

[samw5]

That computerID is fetched directly from my Azure reports rather than my tenant table that I recreated.

[richbenmintz]

Hi @samw5 ,

you can create a calculated table that represents the unique computer ids, or create the table in Power Query using append and grouping.

Hope that makes sense
Richard
Did I answer your question? Mark my post as a solution!
Did my answers help arrive at a solution? Give it a kudos by clicking the Thumbs Up!

[lbendlin]

In the Tenant table is the TenantID not unique?  Why not?

Generally you want 1:* relationships from the dimension table to the facts table

[samw5]

Yes the TenantID in the Tenant table is unique to each clientName.

If I select One to Many or Many to One for cardinality, it receive a message saying that "The cardinality you selected isn't valid for this relationship".

I do have a few rows with empty TenantIDs, so technically these are blanks but they are not referred to in the other tables (and I tried removing them with the same issue, not being able to set the 1-many relationship).

[richbenmintz]

Hi @samw5 ,

Are you able to provide a pbix file with sample data, and desired outcomes? Really helps to troubleshoot these issues and come up with solutions.

Thanks,