Dynamically Format Date based on Slicer Selection

[Matt_Joers]

Greetings Team, I'm trying to figure out a way to dynamically format the date options in a Slicer based on another Slicer. In my example, here is how the dates should be formatted in the slicer:

- If a user selects "Daily" from the first slicer, the date options should display as "mmm dd yyyy".

- If a user selects "Prior Month" from the first slicer, the date options should display as "mm yyyy"

- If a user selects "Year To Date" from the first slicer, the date options should display as "mmm dd yyyy"

Below is a screenshot of the configuration currently - please let me know if anyone has any plausible ideas. 

[Kbandewar]

This works when we want to just showcase the consolidation in dates, for example, here we have used MAX(date).
Is there any way to present all the dates and not just the MAX or MIN of date ?
I want to use date column on Y axis.
and as a slicer I have Annual, Monthly, Daily,
So if Annual is selected, all the dates should be YYYY
if monthly selected then, MM/YYYY and so on

[lbendlin]

Abandon that idea and use a date column and zoom sliders.

[v-angzheng-msft · Accepted solution]

Hi, @Matt_Joers 

Try to create a measure like this:

Format = 
SWITCH(
    SELECTEDVALUE(Slicer[Processing Interval]),
    "Daily",FORMAT(MAX('Table'[Date]),"mmm dd yyyy"),
    "Prior Month",FORMAT(MAX('Table'[Date]),"mm yyyy"),
    "Year To Date",FORMAT(MAX('Table'[Date]),"mmm dd yyyy")
    )

 
Result:

If you only want to see the formatted date, you can change the column width of the service date column to 0.

Please refer to the attachment below for details. Hope this helps.

Best Regards,
Community Support Team _ Zeon Zheng

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[lbendlin]

Keep in mind that a slicer can only be populated by values from a column, not from a measure.

So what you would need to do is to have ALL of your formatting options pre-computed in that "Service Date" column, and then have another column that indicates which of the "Processing Interval" options the value corresponds to.  This also mandates single value selection on your "Processing Interval" slicer, but you already have that.