Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now

Reply
jdogcisco
Resolver I
Resolver I

CALENDARAUTO displays dates from 1899 with refresh table that only uses dateTime.LocalNow()

Hi Awesome People,

 

I'm using CALENDARAUTO to create a Calendar table and this works well in creating dates that align with my data.

 

Now, however, I added a 'data refresh' table so I can display the last refresh date of the dashboard. *Note, I did try changing the DateTime column from 'any' to DateTime and I get the same results. I've also changed it to Date and I get the same results.

jdogcisco_0-1622733768071.png

 

After adding this table, CALENDARAUTO now thinks dates go back to 1899...

jdogcisco_1-1622733851520.png

 

Why does this happen when there is only one entry in the Data Refresh table?  I could switch to CALENDAR and use min max on my data's dates, but that would mean updating A LOT of visuals that is already using the Calendar table....and that doesn't really address the issue, just supresses it.

Any thoughts?

 

1 ACCEPTED SOLUTION
AlexisOlson
Super User
Super User

I don't like to rely on CALENDARAUTO for this sort of reason. If you change the definition to CALENDAR, you shouldn't need to update any visuals since they'd be using the same column (it's just defined differently).

 

My guess is that it's interpreting the Time column as DateTime for some reason. Maybe try converting that column to decimal just to see if that's indeed what's going wrong.

View solution in original post

4 REPLIES 4
ArT101
Helper I
Helper I

you could also change the data type to TEXT and that works as well

Teo1967
New Member

This happens because you must have some time column in one of the tables.

The alternatives are:

1) Delete the time column or
2) Create the Calendar table by Power Query (which I recommend)

AlexisOlson
Super User
Super User

I don't like to rely on CALENDARAUTO for this sort of reason. If you change the definition to CALENDAR, you shouldn't need to update any visuals since they'd be using the same column (it's just defined differently).

 

My guess is that it's interpreting the Time column as DateTime for some reason. Maybe try converting that column to decimal just to see if that's indeed what's going wrong.

Huh, go figure. That (switching Time column to decimal) fixed the problem.  Thank you!

 

jdogcisco_0-1622738743218.png

 

jdogcisco_1-1622738766955.png

 

Helpful resources

Announcements
November Power BI Update Carousel

Power BI Monthly Update - November 2025

Check out the November 2025 Power BI update to learn about new features.

Fabric Data Days Carousel

Fabric Data Days

Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Solution Authors