master calendar script not retaining missing dates

[Raju_6952]

Hi all,

I am using master calendar to generate the missing dates between the min and max date range but due to section access those dummy dates are filtered out, is there a way to retain those missing dates as well with section access included.

Currently date field from dimension table is used to generate the master calendar.

Any suggestions would be highly appreciated,

Regards,

Raju

[HeshamKhja1]

Hi @Raju_6952 , check this article it had the same issue and is resolved. Not sure of the quality of the solution though https://community.qlik.com/t5/App-Development/Master-Calendar-and-Section-Access/td-p/1728170

[anat]

you have to generate dummy / empty records  for the missing dates based on the field which you are using for section access

[marcus_sommer]

I assume that your challenge isn't the section access else that those dates are missing within the facts. To create them within the calendar respectively a dimension-table won't be sufficient within the most scenarios - because your measures will probably come from the facts and then they miss the right connection to the dimension.

The usually most pragmatic way to solve such challenges is to create these missing records within the facts.

[Nagaraju_KCS]

It's a known limitation when combining the Master Calendar and Section Access. SA filters the entire data model, which inadvertently filters out the Master Calendar's dummy dates. To fix this, you need to isolate the Calendar table from the SA reduction process.

[Lech_Miszkiewicz]

Seconding on Marcus suggestion - that is the usual practice for us as well.

You may just need to concatenate to your fact table combinations of missing dates and section access keys. Usually in those scenarios we first create a working composite field made of the section access key and date, then we create all possible combinations of dates and section access key and we concatenate those which dont exists in fact.

That method still allows you to use your calendar normally as well as it performs much better than detached calendars suggested by others (depending on data volume of course) and simplifies expressions used in the app as well as allows for full association of facts with calendar (the usual green, grey, white...)

cheers