I am having an issue understanding how to get out of a circular dependency in 4 simple tables. Currently I get the error saying that I cant make a particular relationship active because it would introduce ambuguity. I think this is because if you look at the small model I have, enabling the highlighted relationship would make the whole thing circular.
My issue is essentially that I have an Employee table and I want to be able to associate those employees with various things, specifically Support Tickets, Feedback, Qualifications and so on. So employee needs a relationship to all of those tables. However I also want to be able limit the analysis of these tables by a common date table, so that I can say "# Ticket, Qualifications, Feedback received in the past 90 days" etc. So I am trying to link the Date table to all these things as well. As soon as I try to do that I get my "ambiguity" problem
Given that what I'm doing is fairly straightforrward there must be a simple way that this is avoided or I am misunderstanding how to use relationships properly.
In case it helps you can see roughly what I'm after. The employee has various aggregate values calculated but at the moment they are not being managed by a common date. So the Reopen Rate column for example is showing the reopen rate for all time, not say the past 30/90/180 days.