Forum Discussion
Phantom ambiguous paths between tables causing issues
- 1 year ago
Consider this user error. We had two dates going to two different dates on the same table. The original model didn't have an issue as one of those relationships was many-to-many and the other a one-to-many, so the latter got prioritised and prevented the ambiguity error. Once we built identical types of relationships, the ambiguity came into effect.
Hi SevsBo
Did you use DAX to generate either calendar table? For example CalendarAuto?
There was a bug a few versions ago that causes the built in Calendar tables to clash with CalendarAuto.
If you are using CalendarAuto try using Calendar instead so Calendar(StartDate, LastDate). If that fixes the issue we know that was causing it!
- SevsBo1 year agoResponsive Resident
Hi SamWiseOwl
We are already using CALENDAR, unfortunately.Worth mentioning that Date Conversion and most of the rest of this model comes from a direct link to a Semantic Model, but Ultimate Calendar, FTE Numbers and Months exist only in this report.
That said, Months is created entirely within this report, not from any external file.