topic Re: Dollar Sign used at beginning of set expression {$< in App Development

Dollar Sign used at beginning of set expression {$<

QuestionAndAnswer — Tue, 19 Nov 2024 16:49:51 GMT

Hi everyone, apologies if this has been answered previously.

I joined a new project and am having trouble understanding what a dollar sign in between the first curly brace and carrot in the expression does. I understand what it means when used with a variable or formula, determines if the variable/formula is evaluated before the expression. But I'm not sure how that would work in this context. Here's an example:

num(
sum({$<Company={'Company A'},WeekEnding={'$(vMaxWeek)'}>}[Net Sales])
,'$#,##0)

What would be the difference between the above expression and this expression (removed the first $):

num(
sum({<Company={'Company A'},WeekEnding={'$(vMaxWeek)'}>}[Net Sales])
,'$#,##0)

Thanks

Re: Dollar Sign used at beginning of set expression {$<

sbaro_bd — Tue, 19 Nov 2024 17:11:28 GMT

Hi @QuestionAndAnswer ,

No difference, put a dollar sign or let it blank is the same. Dollar $ for a set analysis means "for the active selections" to refer to your filters. The opposite for dollar-sign is 1 that means "disconnect your expression from all active selections", the calculations are performed on whole data.

https://help.qlik.com/en-US/sense/May2024/Subsystems/Hub/Content/Sense_Hub/ChartFunctions/SetAnalysis/set-modifiers-dollar-sign-expansions.htm

Regards.

Re: Dollar Sign used at beginning of set expression {$<

QuestionAndAnswer — Tue, 19 Nov 2024 17:14:22 GMT

That's what it seemed like to me as well. I saw no difference from taking it out or leaving it in, which further added to my confusion haha. Thanks for clarifying!

Re: Dollar Sign used at beginning of set expression {$<

marcus_sommer — Tue, 19 Nov 2024 17:18:21 GMT

It has nothing to do with variables else it specified the default selection state. Within the most cases there is no difference between applying the {$< and without the $-sign but there are some very specific scenarios which would return different results. I'm not sure if it's covered within the following - but even if not it's a good starting point to the use of set analysis:

Set Analysis: syntaxes, examples - Qlik Community - 1491810