Forum Discussion
Post PatronIssues Migrating Existing Dashboard to On-Premises Version (January 2026)
Hi F_Reh ,
The DAX formula itself looks valid and Date is correctly generated by the CALENDAR() function.
A circular dependency usually occurs when another table references a calculated column from the Date table and that column is used in a relationship back to the Date table.
Please review the model relationships and check whether any relationships use calculated columns such as DateAsInteger, YearMonthNumber, or similar. If so, try changing the relationship to use the base DatesTable[Date] column instead.
Additionally, I noticed a small typo in the ContractYear calculation (FORMAT([DATE],"YYYY") should be FORMAT([Date],"YYYY")). While this may not be the root cause, correcting it would be recommended.
If the issue persists, please share a screenshot of the model relationships or confirm whether any calculated columns in other tables reference the DatesTable.
Best Regards,
Chaithra E.
Community SupportHi F_Reh ,
Thank you for reaching out to Microsoft Community.
Regarding the circular dependency error on the Date table, this typically occurs when the Date table formula references columns or tables that also depend on the Date table. I recommend recreating the Date table without referencing other tables initially (for example using CALENDARAUTO() or a fixed date range), then re-applying relationships afterward.
For the Model View showing only one table, this can happen when the model encounters an error during load. After resolving the Date table issue, please try selecting Close & Apply in Power Query and reopen the Model View. In most cases the remaining tables will appear once the model refresh completes successfully.
Check Power Query > Enable Load.
If disabled, right click Query > Enable Load
If the issue persists, please share the DAX formula used for the Date table, and we will be happy to review it further.
Kind regards.