Forum Discussion
Join Assistance
I have 4 tables for our in-house project tracking app. We track info at different levels of detail between our estimate and planned, which I think is causing the issue, but not sure.
TABLES - there is more, non-pertiennt info in each table
- Estimate
- TaskID
- ProjectID
- Contractor
- Discipline
- Period
- PeriodID
- Start Date
- End Date
- Percent Complete
- TaskID
- PeriodID
- *Info*
- Plan
- ProjectID
- PeriodID
- Contractor
- Discipline
- Contractor and Discipline are the same as in the esimate table but are not FK b/c those values are not unique
In Power BI Desktop
Estimate is related to Percent Complete via TaskID
Period is related to Percent Complet via PeriodID
Period is related to Planned via PeriodID
Estimate is related to Planned via a concatenated field of ProjectID + Team + Discipline via an intermediary b/c on their own it is a many to many relationship
The problem occurs when I try to connect Period to Planned via PeriodID and it says I am introducing ambiguity, I am assuming through the Estimate to Percent Complete to Period relationship
I'm sure you'll need additional info, please let me know what else I can provide to get past this one...thanks!
A good first tip is to make sure you don't have any Bi-directional relationships unless you know you need them for sure.
So make sure this setting is set to Single and not Both on all your links.
You can tell which ones are set to both by looking at the arrows on the link (2 vs 1 direction). Try that and report back :)
h
2 Replies
A good first tip is to make sure you don't have any Bi-directional relationships unless you know you need them for sure.
So make sure this setting is set to Single and not Both on all your links.
You can tell which ones are set to both by looking at the arrows on the link (2 vs 1 direction). Try that and report back :)
h
Thanks, trying now and will report back
