Forum Discussion
One date slicer for multiple date columns
The fundamental issue is that you don't want to have multiple possible filtering paths from one table to another since this creates model ambiguity.
For example, if following relationship paths, Dates filters SentEmails and SentEmails filters EmailEvents, then having Dates directly filter EmailEvents via a relationship introduces ambiguity, which is why Power BI sets these relationships to be inactive.
There's no simple fix to create a good data model. The resolution is to structure your model to avoid bidirectional relationships when possible and avoid relationships directly between fact tables wherever possible.
Further reading:
https://www.sqlbi.com/articles/bidirectional-relationships-and-ambiguity-in-dax/
I'm curious on what the best approach would be for Service Management Data.
We have a table of Issues, which have a Created Date and a Resolved Date.
For a Monthly report of lets say, May,
We would need to filter one chart with all issues Created in May and anothe chart to show all issues Resolved in May,
Both showing issues per day of the month.
Thoughts and ideas?