Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
I have an issue with several applications with Qlik Sense outter set analysis.
Indeed, I have a set analysis expression.
In order to be more efficient, I create a master measure Amount_N which already filters data based on the year (N) I selected.
Then I created other measures using outter set analysis to filter specific account.
For instance, I will have {<Account = {'4350','4620'}>} Amount_N
This works fine, AS LONG AS the account mentioned in the outer set analysis exists.
However, it becomes a problem when the stated account do not exist, and, instead of showing null or 0, Qlik Sense simply ignores the outter set analysis. The results of my measure is then completely wrong
Thanks for you help
I tried to replicate this on my end and did not see the issue you're describing. Perhaps this is specific to certain versions, requires additional conditions, or the master measure being referenced has its own set analysis that does not provide the expected results when merged with the outer set?
This is a known issue. A very interesting solution has been posted here:
https://www.next-decision.fr/wiki/qlik-sense-et-loperateur-secret-des-set-analysis
-Rob
http://www.easyqlik.com
http://masterssummit.com
http://qlikviewcookbook.com
Thanks for sharing that interesting explanation
HI,
I have tried the solution but unfortunately, it did not work.
Here is my first master measure:
#Appels = Count([CALL.CallId]
Then I create another one:
#Abandons = ({<[CALL.Abandon]={'Oui'}>} #Appels)
Then, I use variables:
vAnneeN = (at the moment) 2025
vAnneeN_1 = 2024
vAnneeN_2 = 2023
I have then 3 master measures and no data for 2023.
{<[Année] = {'$(=vAnneeN)'}>} #Abandons = 6536
{<[Année] = {'$(=vAnneeN_1)'}>} #Abandons= 30302
The same for vAnneeN_2 should = 0 but here is my actual result
{<[Année] = {'$(=vAnneeN_2)'}>} #Abandons = 36838
And if I try the suggested solution:
{&<[Année] = {'$(=vAnneeN_2)'}>} #Abandons = 36838
Thus, we can see that it doesn't work. It should = 0 😞
Can anyone help?
Thanks
😶🤔 is there some qlik help document about this ?
Is this Qlik on-prem or Cloud?
-Rob
On premise
L'opérateur '&' a été introduit en version Novembre 2024 😉
Bug report: Outer set expression is not inherited ... - Page 3 - Qlik Community - 2447979
My client runs the may 2024 version but an update in may 2025 is planed very soon, I will check as soon as the update is complete.
Thanks for this information