WiseOwl Training - Established 1992 Wise Owl Training

Established May 1992
30 years in business
Wise Owl Training
30 years in business
See 520 reviews for our classroom and online training
Ways to model different DAX calendar date situations
Part one of a six-part series of blogs

In the real world (or at least, the DAX version of it), calendars and dates aren't quite as simple as one would like. This blog shows how to solve a number of common scenarios, including where different tables have different levels of "granularity", coping with special days like bank holidays, handling non-standard finanical year-end dates and dealing with a table which contains more than one date column.

  1. Modelling techniques when working with calendars/dates (this blog)
  2. Dealing with varying date granularity using calendars
  3. Modelling bank holidays and other special days
  4. Modelling different financial year-ends
  5. Handling multiple date columns using multiple tables
  6. Handling multiple date fields using multiple relationships

This blog is part of our online SSAS Tabular tutorial; we also offer lots of other Analysis Services training resources.

Posted by Andy Brown on 22 January 2016

You need a minimum screen resolution of about 700 pixels width to see our blogs. This is because they contain diagrams and tables which would not be viewable easily on a mobile phone or small laptop. Please use a larger tablet, notebook or desktop computer, or change your screen resolution settings.

Modelling techniques when working with calendars/dates

The previous blog in this series showed how to create and use a basic calendar.  This blog shows how to cope with the following scenarios which can arise in "real life":

Scenario Notes
Varying date granularity How to cope when some data is at date level, some by month and some by quarter.
Bank holidays The best way to integrate special days like bank holidays into your calendar.
Financial years Coping with the common scenario that your financial year doesn't end at the same time as your calendar year.
Multiple date tables (1) Using multiple tables to cope with the situation where a single table contains two or more dates (for example, an order table might have an order, shipping and invoice date).
Multiple date tables (2) Using multiple relationships as a way to model the same thing, but this time including your calendar table only once.

Even if your interest in calendars is waning it's still worth reading this blog, as many of the techniques introduced have much wider application within SSAS Tabular.

This blog has 0 threads Add post