Forum Discussion
Helper IIITimeline Slicer - 2017 with 53 Weeks
Community ChampionYou can try. The issue here is that the visual is almost certainly using the WEEKNUM to calculate the number of the week and hence it's behavior.
Helper IIIIt is curious but in the options the only one that its not rigth is the week number all others work perfectly
- Greg_Deckler
Except, there ARE 53 weeks in 2017. 12/31/2017 falls on a Sunday, which is the start of the 53rd week.
- ratercero
This is another subject but there are NOT 53 weeks on 2017, because the week numbers are assigned to the year that has more days on that particular week, however do you know who else can I contact to address this inconsistency?
Best Regards
RT
- Greg_Deckler
I think the disconnect here is that may be how you assign weeks numbers within your organization, but that is not how the WEEKNUM function within Power BI works. You can understand the issue here. It would be difficult to account for how all organizations assign week numbers within their own calendar because I've seen some crazy ways in which companies do this, especially when working with a non-standard calendar like June-June or Feb-Feb, things like that. Bottom line here is that if your week numbers do not line up with the 2 options that WEEKNUM provides, you probably have a couple options:
- Contact the developer of the visual and see if you can get them to code in some kind of exception for your circumstance
- Create your own version of the visual that works the way you want it to work
- Create your own week num column and tie some kind of slicer to that
Bottom line is that this is not an inconsistency within Power BI, it just doesn't work the way you want to see the week numbers shake out.