Forum Discussion

Likhitha's avatar
Likhitha
Helper IV
6 years ago
Solved

Doubt regarding CALENDARAUTO() function

Hello All, I created a callendar function using CALENDARAUTO() DAX .But I'm getting year range from 1899 in newly created table and relationship exists between OrderDate and Calendar Table.
Need Help
Show and Tell
Tips and Tricks
  • az38's avatar
    az38
    6 years ago

    Hello @Likhitha

    according to https://docs.microsoft.com/en-us/dax/calendarauto-function-dax

    The earliest date in the model which is not in a calculated column or calculated table is taken as the MinDate.

    of my experience, its 1899 appears in the calendar table as at least one (at least) of its date columns in the data model has the value BLANK, so DAX defines it as a possible first date to calculate

az38's avatar
az38
Community Champion
6 years ago

Hello @Likhitha

according to https://docs.microsoft.com/en-us/dax/calendarauto-function-dax

The earliest date in the model which is not in a calculated column or calculated table is taken as the MinDate.

of my experience, its 1899 appears in the calendar table as at least one (at least) of its date columns in the data model has the value BLANK, so DAX defines it as a possible first date to calculate

  • dedelman_clng's avatar
    dedelman_clng
    Community Champion
    6 years ago

    I had the same issue. I figured out that because I had extracted the Time from a data column and added a "Time Only" column in "Transform Data", CALENDARAUTO() took that as a blank date and behaved as az38 said.

     

    The workaround would be to create the calculated column in the model itself, but this sounds like a bug in CALENDARAUTO(), does it not?

     

    Hope this helps.

    David

    • az38's avatar
      az38
      Community Champion
      6 years ago

      dedelman_clng 

      it's not a bug. for more predictable calendar you can use CALENDAR() or even GENERATESERIES() functions