my client requested a change in using a date filter so that they can have the choice to choose the start date and end date.
With the help of the community, I created two independent date tables and added a filter to the measures to get the date from like:
I am trying to get the cumulative count using the new date filters where there are two independent date tables one for start date and another for an end date.
If I understand your requirement properly, you don’t need to do any of this – you can just use a single date table connected to the fact table, use the measure you already have for cumulative count, and then just add a date slider to choose and filter the start and end dates.
Thank you @BrianJ
The requirement is to have two dates filters. so I am trying to achieve the same result of the cumulative count but using two dates filters.
So basically I am trying to understand how can we get the cumulative count if we have two independents date tables one for the start of the month and there other for the end of the month.
Having two dates…wouldn’t it take up a lot extra data space and processing timing to refreshing your reports. I can also see administration night mare of keeping both date table up to date too. If you have an issues you wouldn’t know which date table is giving you issues.
If you have slicer your user still be able see the dates they choose.
I was wondering how you not show the second date in the “start date slicer” and not show the first date in the “ending date slicer”. I downloaded the file and i was trying to find it but couldn’t find it.
LOL. I just threw a borderless blank button over the top of each of them – the Power BI equivalent of sticking a piece of black electrical tape on your dashboard to cover up the check engine light…
My question here, what is the purpose of using the Monthnyear column that ends with 00?
And what were the steps to create it?
I count apply the solution yet.
I always use @Melissa’s awesome Extended Date Table as the date table in my models, and Monthnyear is just the column she includes as the numeric equivalent of the Month & Year column. I’m honestly not sure why she includes the two trailing zeroes - perhaps just to maintain consistency with the DateInt field. Your calculated column version of that field without the zeroes should work equally well.
You’re spot on @BrianJ, it’s to mantain a fixed pattern and results in equal string length for these type of fields, although the trailing zero’s could be considered redundant, it doesn’t affect cardinality.