Skip to main content

QlikView App Dev

Discussion Board for collaboration related to QlikView App Development.

Skip the ticket, Chat with Qlik Support instead for instant assistance.
Showing results for 
Search instead for 
Did you mean: 
Contributor III
Contributor III

Year End Calendar - Week Issue

Hello, I’m looking for some assistance please with the Calendar that is used on QlikView. It’s the Master Calendar that affects all our production QVDs so I’m afraid to make too many changes to it.

My colleague who looked after the calendar at Year End has left the company and I’m still relatively new in the role and feeling some pressure to resolve 😊

What is happening is that Fiscal Week 1 2021 is showing as Fiscal Week 53 2021.

I need to split out the weeks, however, they are currently showing as below:

  • Fiscal Week 52 2020 –> 19/12/2020 – 25/12/2020
  • Fiscal Week 53 2020 -> 26/12/2020 – 29/12/2020 (Year End 29/12/2020)
  • Fiscal Week 53 2021 -> 30/12/2020 – 01/01/2021 (This needs to be Fiscal Week 1 2021)
  • Fiscal Week 2 2021 -> 02/01/2021 – 08/01/2021

This is the way the calendar is showing at the moment for Jan 2021:


Fiscal Week 2021-53 is showing the below dates:


Fiscal Week 1 is showing from 02/01/2021 to 08/01/2021 – so essentially looking to remove the Fiscal Week 2021-53 and have it as Fiscal Week 1 and the current Fiscal Week 1 becomes Fiscal Week 2.

I’ve attached the calendar script (with some data removed) we currently have so any guidance or assistance would be appreciated.

Labels (3)
4 Replies

You can try setting system variable BrokenWeeks to 0 (zero) or pass the parameter for that argument in WeekName().

Contributor III
Contributor III

Thanks @tresesco . I've added the BrokenWeeks parameter, however, I still have the 2021-53 Fiscal Week in my calendar after the change. Any other suggestion of what to amend in the script?



I am encountering the same "2021-53" issue as well.


Did you ever find a resolution to this? 

Creator II
Creator II

The BrokenWeeks parameter is already there and it should solve the problem by changin it to 0

See the screenshot below



Best Regards
Yassine Mhadhbi