Forum Discussion

F_Reh's avatar
F_Reh
Icon for Post Patron rankPost Patron
6 months ago
Solved

Issues Migrating Existing Dashboard to On-Premises Version (January 2026)

Good Afternoon,   I am creating a new version of an existing Dashboard (currently in Version: 2.145.1105.0 64-bit, July 2025) to the On-premises Remote Server one (Version: 2.150.1926.0 64-bit, Jan...
Help
Show and Tell
  • v-echaithra's avatar
    v-echaithra
    6 months ago

    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.

F_Reh's avatar
F_Reh
Icon for Post Patron rankPost Patron
6 months ago

v-echaithra- thanks for the insight ! So I compared the Model View of the Dashboard built in the previous version of Power BI versus the On-Premises version (under construction), and there were clear discrepances. So I deleted the questionable relationships (which do not exist in the previous version) and reinstated relationships (which did exist in the previous one but which were now omitted). Then magically all the columns for Dates Tables suddenly "popped up" in the Model View (of the On-Premises version currently under construction !)..