<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=612681139262614&amp;ev=PageView&amp;noscript=1">
Skip to content

Need help? Talk to an expert: phone(904) 638-5743

Avoiding Unwanted Outcomes using Date Columns

Avoiding Unwanted Outcomes using Date Columns

Date Columns Using Dax

Many people have dates as part of their data sets.  Dates are great to allow us to view our data aggregations in smaller buckets in order to get extra details about our situation.  Sometimes though we are faced with having multiple date columns in one table. The more date columns the better, right?  

Well, this can usually lead to two outcomes.  1) Frustration that you can’t view the data based on your 2nd date column 2) Not realizing the data you are looking at is in fact NOT accurate. 

I will show you in the video both of these unwanted scenarios.  More importantly, however, I will show you how you can use some fairly simple DAX and modeling relationship techniques to resolve the issue.

 Let me set up the scenario in this video for you.  I’ve made a very basic Excel file that tracks sales by what state they occurred in, when the sale occurred, and when the sale shipped out.  So if I want my team to see the number of actual sales that have occurred I would use the sale date column.  If, however, I need my shipping department to be made aware of how much money we have fully processed in terms of shipping I need to express my sales by the ship date.

Follow along with me in this video as we will show how to accomplish this using DAX.  

Some extra tidbits I’ll be throwing in at the beginning of this video are how to make your own Date Table when one isn’t given to you in your original data model.  For a more in-depth look at how the date table is made check out Devin Knight’s blog.


Sign-up now and get instant access

Leave a comment

Free Trial

On-demand learning

Most Recent

private training

Hackathons, enterprise training, virtual monitoring