topic Re: Issues Migrating Existing Dashboard to On-Premises Version (January 2026) in Report Server

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

F_Reh — Tue, 10 Mar 2026 15:46:59 GMT

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, January 2026).

I have a couple of issues already:

1) One of the Tables is a Dates Table - I have copied exactly the correct formula in, but I am getting a error "a circular dependency was detected".

2) Model View - its only showing one table which ironically is the error-giving Dates Table, while none of the other Tables (which are actually all fine) are not showing at all:

Kindly advise.

Regards

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

v-echaithra — Wed, 11 Mar 2026 05:39:45 GMT

Hi 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.

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

F_Reh — Thu, 12 Mar 2026 11:38:46 GMT

@Model View showing only one table:

I simply Zoomed out, and found the other tables (in spite of the Circular Dependency error still showing):

The Dates Table formula is as follows – and is exactly the same as is used in my other dashboards (where it works fine without any Circular Dependency issue). Actually, I am unable to see any foreign columns from other tables that could be causing the issue:

DatesTable =

ADDCOLUMNS (

CALENDAR (DATE(2019,4,1),TODAY()),

"DateAsInteger" ,FORMAT ( [Date], "YYYYMMDD" ),

"Year" ,YEAR ( [Date] ),

"Monthnumber", FORMAT ( [Date], "MM" ),

"YearMonthnumber", FORMAT ( [Date], "YYYY/MM" ),

"YearMonthShort", FORMAT ( [Date], "YYYY/mmm" ),

"MonthNameShort", FORMAT ( [Date], "mmm" ),

"MonthNameLong", FORMAT ( [Date], "mmmm" ),

"DayOfWeekNumber", WEEKDAY ( [Date] ),

"DayOfWeek", FORMAT ( [Date], "dddd" ),

"DayOfWeekShort", FORMAT ( [Date], "ddd" ),

"Quarter", "Q" & FORMAT ( [Date], "Q" ),

"YearQuarter", FORMAT ( [Date], "YYYY" ) & "/Q" & FORMAT ( [Date], "Q" ),

"FiscalMonthNumber",IF ( MONTH([Date]) > 3, MONTH([Date]), MONTH([Date])+12 ),

"ContractYear", IF ( MONTH([Date]) <= 3,

FORMAT([Date],"YYYY")-1 &"-"& FORMAT([Date],"YYYY"),

FORMAT([Date],"YYYY") &"-"& FORMAT([DATE],"YYYY")+1

"IsCurrentMonth", IF(YEAR([Date]) = YEAR(TODAY())

&& MONTH ( [Date]) = MONTH (TODAY())

,"Yes"

,"No"

"FiscalYear" , SWITCH(

TRUE(),

YEAR([Date]) = YEAR(TODAY())

&& MONTH ([Date]) <= 3,0,

YEAR([Date]) = YEAR(TODAY()) - 1

&& MONTH ([Date]) > 3,0,

YEAR([Date]) = YEAR(TODAY())

&& MONTH ([Date]) > 3,1,

YEAR([Date]) = YEAR(TODAY()) +1

&& MONTH ([Date]) <= 3,1

"Current Month" , FORMAT(TODAY() , "mmmm"),

"Week Start Date",[Date] - WEEKDAY([Date],1)+1,

"Week End Date",[Date] - WEEKDAY([Date],2)+7,

"MonthYearShort", FORMAT ( [Date], "mmm-YY" ))

I assume [Date] is "supposed" to be created by CALENDAR (DATE(2019,4,1),TODAY()).

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

v-echaithra — Thu, 12 Mar 2026 12:25:41 GMT

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.

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

F_Reh — Thu, 12 Mar 2026 13:15:50 GMT

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 !)..