Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi All,
I have researched the community board and I thought I followed the docs and solutions that were posted however, I'm still running into an issue.
Problem Description: I'm using the Aggr() function as a measure in a line chart. It renders the data perfectly except that it does not execute the set Expression. Regardless if the set expression is inside the aggr or outside.
The data is in one table and is very similar to this sample data pasted below.
The measure that I'm using in the line chart is:
Aggr(avg(Score), Last_Updated_Date)
I get a chart like so (Note data in the chart is not the same as the sample data provided):
I then added the set expression at the Aggr level
=Aggr({<Score = {">=0"},Status = 'high'>}
avg(Score), Last_Updated_Date)
but no change occurs to the Chart. I even moved the expression inside the avg function and still not change
Lisa, you are right that Qlik was case sensitive and once I modified the expression to this:
Aggr({<Score = {">=0"},Status = {"low"}>} avg( Score),Last_Updated_Date)
Everything worked fine
Agigliotti: Dropping the Aggr surprisingly worked too but only after I fixed the above syntax.
I thought that I needed to aggregate the data first but looks like qlik does that for you in this particular scenario.
Qlik is case sensitive, and you are missing some brackets, so change your expression to:
=Aggr(avg({<Score = {">=0"}, Status = {High}>} Score), Last_Updated_Date)
Hi Lisa,
Still doesn't work. I checked the data and the values used.
I feel that it is being ignored or not executed at all
Hi @H-Zey ,
Maybe this:
Avg( {< Score = {">=0"}, Status = {'High'} >} Score ) as measure
and Last_Updated_Date as dimension.
I hope it can helps.
Best Regards
Lisa, you are right that Qlik was case sensitive and once I modified the expression to this:
Aggr({<Score = {">=0"},Status = {"low"}>} avg( Score),Last_Updated_Date)
Everything worked fine
Agigliotti: Dropping the Aggr surprisingly worked too but only after I fixed the above syntax.
I thought that I needed to aggregate the data first but looks like qlik does that for you in this particular scenario.