Forum Discussion

Jmrc16's avatar
Jmrc16
Frequent Visitor
1 year ago
Solved

Mark Date Table after everything

Hello Everyone, I openned an old projet that was build since 5 years ago. I saw that "dimCalendar" wasn't marked as "Date Table", so I marked date table as date and assure that date column is ok w...
  • ajaybabuinturi's avatar
    1 year ago

    Hi Jmrc16, I believe you covered everything however I have few check points.

    1. Verify all time intelligence functions specially SAMEPERIODLASTYEAR DAX
    2. Review model relationships (1:* with Date)
    3. Remove legacy auto date tables if you have
    4. Format & optimize calendar columns
    5. Add hierarchies & sort orders 

    Thanks,
    If you found this solution helpful, please consider giving it a Like👍 and marking it as Accepted Solution✔. This helps improve visibility for others who may be encountering/facing same questions/issues.

  • rohit1991's avatar
    1 year ago

    Hi Jmrc16 

     

    Marking dimCalendar as a proper Date Table and disabling the auto date/time option that’s essential for a stable time intelligence setup.

     

    To make sure everything runs smoothly going forward, here are a few key checks:

     

    • Ensure your date table has a complete, continuous range without gaps (no missing dates).

    • Check that all time intelligence measures like SAMEPERIODLASTYEAR are using this custom table it's more sensitive to gaps or incorrect setup than others.

    • Verify there's a proper 1-to-many relationship from the date table to all fact tables.

    • Remove any auto-generated hierarchies still used in visuals and replace with your own.

    • Use Sort by Column (e.g., Month Name by Month Number) to keep visual order correct.

    • Format your calendar columns (like Month, Quarter) if needed for consistency.