Support for custom date hierarchy for year-month-week hierarchy

[TrutzS]

Hi all,

I have created a custom date hierarchy to always allocate full weeks to a month (basically the week goes to the month into which the 4+ days fall, similar to ISOWeek for the start of the year).

Is there an option to adapt the timeline slicer for that?

The current implementation of the timeline slicer doesn't work with custom hierarchies. As an alternative one could use the standard hierarchical slicer, but it works vertical instead of horizontal like the timeline slicer and doesn't provide the same ease of multi-select.

Example: Week 14 is not correctly allocated

Example: Week 53 doesn't exist in 2019

[helen508light]

@TrutzS
Timeline doesn't provide this ability now.
We will add it to visual's backlog

[quickaid-fr]

Urgent for 2021 => timeline slicer gives a wrong week number => W2 instead for W1 !
Can you urgently patch it so that 1st week of the year is the one with at least 4 days of the year in it ?
Thanks !

[TrutzS]

I second the remark of @quickaid-fr
For those working with ISO weeks, it is currently producing questions when looking at data not aligned to the correct week.

[IIonaSimakova]

Hello @quickaid-fr,
Could you send us a sample of your report to reproduce the bug?

[TrutzS]

Hi @IIonaSimakova,
Please find attached a sample for the issue that @quickaid-fr was referring to.

ISOWeek_Sample.zip

[Manikumar34]

I am getting 53rd week on the slicer but I don't have any data for 53rd week. I'm getting this on every year. Any help here please.

[Manikumar34]

@TrutzS , What should I change now to have 52 weeks on the slicer labels as well? I want to have ISOWeek format instated US week labels.
Please help. Thanks in Advance.

[ora-gh]

@uve
I urgently need this bug fixed. Could you please let me know how I can help, and what is the current progress? Please see my description in the following thread: https://community.powerbi.com/t5/Custom-Visuals-Development/Timeline-slicer-ISO-week/m-p/1606108/highlight/true#M3523

My interpretation is that this issue occurs for all years where january 1st is a friday, saturday or sunday, since the week numbering rules are then different. I.e. 3/7 (43%) of all years are displayed incorrectly for us in this slicer.

I suggest providing an option for the slicer where we can choose between using US week numbers or ISO week numbers, based on the functionality of WEEKNUM([Date]) and WEEKNUM([Date],21)
"You can also use the value 21 as second parameter, and guess what – it now returns weeknumbers according to ISO 8601. As many DAX-functions are derived from Excel (including WEEKNUM()-function), this also works with DAX’s WEEKNUM()-function!"
https://blog.gbrueckl.at/2012/04/iso-8601-week-in-dax/

[TrutzS]

@Manikumar34 the slicer operates currently only with US weeks. So we need to wait for an update to support at least the ISO week format. Apart from that, the slicer always displays all possible time slots between minimum date and maximum date of the date field you supplied to the visual. This is regardless of the fact if there is data in your dataset for a given timeslot or not.

[Manikumar34]

@TrutzS , thanks for the info.
@uve, could you please help with my query on 53rd week. I need only 52 weeks on slicer and for every 5 to 6 years 53rd week will be included.

Thanks.

[EugeneElkin]

Thanks for the samples.
We are fixing the issue.
ETA is early February