Forum Discussion
Filter propagation when using composite model - Direct Query with Local tables.
Hi AkshayGothe ,
The composite models have limitations namely when refering to tables from different models being related that is why you are getting this type of errors, the models can work with this limited relationships but you can have a lot of issues.
Check this blog post with some addtional insights.
One alternative that I can see for working with this is to use the Advance Sync option on slicers, it can take a little bit more to setup in terms of reporting but will allow you to not have this type of relationship.
Using this feature you can setup two slicers based on two different columns to work in the same way, only thing that you need to have is the same type of data for both columns.
So in this case if you have the Department in all the models if you pick that dimension on all your models and have one Non Related table for the Department then you can sync your reports based on slicers.
Has I refer it's a reporting complex setting for the first time but overcomes some of the relationship issues.