Forum Discussion
Slicer with Direct Query & Import (i.e., Composite Model)
HEY!
The easiest workaround I could come up with was adding the location value to the SQL table; I then used the location value from that table (as opposed to the location value in the (separate) lookup table) as the slicer. This works because I'm using the SQL data on one page of the report so there is no need to have the location value--used in the slicer--filter another table.
Thanks for replying.
Hi Anonymous
I cannot reproduce the same issue.I would suggest you re-create and check the relationship and test again.Some articles for your reference:
https://docs.microsoft.com/en-us/power-bi/desktop-composite-models
Regards,
HEY!
The easiest workaround I could come up with was adding the location value to the SQL table; I then used the location value from that table (as opposed to the location value in the (separate) lookup table) as the slicer. This works because I'm using the SQL data on one page of the report so there is no need to have the location value--used in the slicer--filter another table.
Thanks for replying.