Forum Discussion
Circular Dependancy when creating Relationship
To demo...
exactly the same model...
Hi Ben, yes I am using CalendarAuto as I have several tables with dates that I need to use and didn't know how to get to a min and max date across various tables. I thought CalendarAuto might be causing this issue but not sure how to correct. Any ideas? Thanks
It's worth trying the folowing. When you create the relationship drag from the fact table (many side) into the date table. I think you'll find it works! I know I've had that issue before but now trying in latest version of Power BI I can't recreate the problem at all and it works both ways round.
However I tend to avoid using CALENDARAUTO and go for this sort of approach...
Date =
VAR EarliestYear = YEAR ( MIN ( Purchases[Date] ) )
VAR LatestYear = YEAR ( MAX ( Purchases[Date] ) )
RETURN
ADDCOLUMNS (
CALENDAR (
DATE ( EarliestYear, 1, 1 ),
DATE ( LatestYear, 12, 31 )
),
"Month Year", DATE ( YEAR ( [Date] ), MONTH ( [Date] ), 1 ) //Format as mmm YYYY
)
To demo...
exactly the same model...
Thanks Ben - that done the trick. Why does it work when switching the direction in creating the relationship as the outcome is the same?
Why does this happen? I have the exact same problem, the tables are not related to each other but it gives me circular dependency
Hi Ben, that is the approach I tried before but with so many dates in tables - all of which are relevant and with some being previous to my main table (main date field), so using min/max on the date field meant my calendar didn't have those earlier dates when having to reference the data for that using calendar table.
