Forum Discussion
Helper IIISlicer: Slice two tables with the same column values
Unfortunately the way you have done things is not the best one so please think of exploring the nature of the relations between tables before you implement your model. A many-to-many model is not a good design, it is rather a lazy and unthought design. Essentially you would be using it because you don't want to have to spend the time thinking about the true relationship between the two entities. There are a significant number of relationships between real-world entities that are always one-to-many. If you make all of your relationships many-to-many, this means the following downsides just off the top of my head:
- You are adding a number of unnecessary tables to your database to act as intersection entities.
- Querying data from your database will require more table JOIN operations, which will impact performance.
- Additional code/logic is required to maintain the intersection entities.
- In cases where the relationship between two entities *is* one-to-many, you have just created a potential error condition (i.e. a child mistakenly having two parents).
The proper answer is to spend due diligence during the design process. Please try doing so in the future!
Super UserUnfortunately the way you have done things is not the best one so please think of exploring the nature of the relations between tables before you implement your model. A many-to-many model is not a good design, it is rather a lazy and unthought design. Essentially you would be using it because you don't want to have to spend the time thinking about the true relationship between the two entities. There are a significant number of relationships between real-world entities that are always one-to-many. If you make all of your relationships many-to-many, this means the following downsides just off the top of my head:
- You are adding a number of unnecessary tables to your database to act as intersection entities.
- Querying data from your database will require more table JOIN operations, which will impact performance.
- Additional code/logic is required to maintain the intersection entities.
- In cases where the relationship between two entities *is* one-to-many, you have just created a potential error condition (i.e. a child mistakenly having two parents).
The proper answer is to spend due diligence during the design process. Please try doing so in the future!
Helper IIIAs you said, I tried this now:
But, still it doesn't work..
- v-easonf-msft
Community Support
Hi, tuncay
Have you edited the interactive behavior of visuals? What is the field used in your current slicer?
Try setting the cross-filter to a single direction of one-to-many and then apply the "ID" from the "unit&id" table to the slicer.
If it doesn't work ,please share a sample file for further research.
Best Regards,
Community Support Team _ Eason
