Qlik Community

Qlik Sense App Development

Discussion board where members can learn more about Qlik Sense App Development and Usage.

laurischarf
Contributor II

Ignore selection with set analysis and autocalendar fields

My Sense app allows the user to filter using a field that is auto-created during the load: [ObservationDate.autoCalendar.Year].


I am surprised to find that I cannot use set analysis to ignore the user selection in a KPI.


My KPI: Count({$<[ObservationDate.autoCalendar.Year]= >} distinct PatientID)

I also tried Count({$<[ObservationDate.autoCalendar.Year]={*} >} distinct PatientID)


Both set analyses have no effect; if the user selects any [ObservationDate.autoCalendar.Year] values, the KPI value is changed.


But using the underlying field, [ObservationDate], in both the filter pane and the KPI yields "normal" behavior (i.e., the KPI ignores user selections).


In conclusion, is it necessary to create a field like Year([ObservationDate]) during the load to get "normal" behavior?

Tags (1)
1 Solution

Accepted Solutions

Re: Ignore selection with set analysis and autocalendar fields

I think the reason is that the autocalendar didn't creates real fields else it are derived measures and therefore I assume they won't work it cases where real fields are needed like set analysis, aggr, total <Field> and so on. I think there are further reasons why an own ceated master-calendar is not outdated ...

- Marcus

7 Replies

Re: Ignore selection with set analysis and autocalendar fields

There seems to be an issue with the fields created with derived calendar.... its unfortunate that it doesn't work... but may be someone at Qlik side might look into it.

Re: Ignore selection with set analysis and autocalendar fields

I think the reason is that the autocalendar didn't creates real fields else it are derived measures and therefore I assume they won't work it cases where real fields are needed like set analysis, aggr, total <Field> and so on. I think there are further reasons why an own ceated master-calendar is not outdated ...

- Marcus

laurischarf
Contributor II

Re: Ignore selection with set analysis and autocalendar fields

Thanks, Sunny and Marcus, for contributing.

In addition to what I described before, today I am also seeing it with a chart dimension that is simply date(ObservationDate).

Do you think I should log this is a bug?

Re: Ignore selection with set analysis and autocalendar fields

Until now I don't do much with Sense and when I don't use the autocalendar else a classical master-calendar. Therefore I have no own experience with this feature and couldn't say if there is a bug or if it behaved like designed but I would try it just with ObservationDate without date() because it is already a date and if it shouldn't be displayed in a different format it isn't necessary.

- Marcus

brunobertels
Valued Contributor

Re: Ignore selection with set analysis and autocalendar fields

Hi

May be try

Count({1<[ObservationDate.autoCalendar.Year]= >} distinct PatientID)

laurischarf
Contributor II

Re: Ignore selection with set analysis and autocalendar fields

My hunch is that Marcus is most on target, that the autocalendar dates are not "real" dimensions, so they don't work everywhere. You are right, removing the date() function lets it work; I had it there because the dimension was showing as numeric.

egodinho
New Contributor II

Re: Ignore selection with set analysis and autocalendar fields

Hi,

I solved the issue by creating a master item dimension that I used throughout the dashboard.


Dimension = [Data.Calendar.YearMonth]


Then I use it on all objects.

In the set analysis I put [Data.Calendar.YearMonth].


Best regards,


Élio Godinho

Community Browser