topic Re: why we use $ in QlikView? in QlikView

why we use $ in QlikView?

Anonymous — Wed, 25 Nov 2020 16:16:04 GMT

Hello,

I have one ready made dashboard and I can see some color code on it. When I clicked on any particular color say ORANGE whole dashboard's graph turn into orange. I can see some "environment variable" are also set.

For ex:

How can you achieved this change?

Environment variable which are used mostly are "vi_Blue = RGB(255,128,0)" and "vi_Grey= $(vi_Blu)". what is mean by "$(vi_Blu)"?

Re: why we use $ in QlikView?

oknotsen — Thu, 26 May 2016 11:22:14 GMT

Here you can find more information about "dollar sign expansion":

http://help.qlik.com/en-US/qlikview/12.0/Subsystems/Client/Content/Scripting/dollar-sign-expansions.htm

Re: why we use $ in QlikView?

Anonymous — Thu, 26 May 2016 11:24:08 GMT

$ means that the expression is evaluated in the new var or in the objetc.

Thanks

Re: why we use $ in QlikView?

oscar_ortiz — Thu, 26 May 2016 15:29:29 GMT

You use the $() Dollar sign expansion as a replacement value. The content of your variable will be used as your replacement value in your visualizations.

Not only variables can be used you can also include the results of a function $(=Max(Year)).

Re: why we use $ in QlikView?

Peter_Cammaert — Thu, 26 May 2016 16:10:32 GMT

$ doesn't do anything in QlikView. It's just a character that can be used in all sorts of names.

The $(varname) construct on the other hand is an entirely different story. This specification will replace $(varname) with the current content of variable varname (text), as a number (use $(#varname) ) or as an expression to be evaluated before replacing the $() part (.e.g something like $(=Max(OrderDate) in a set expression text value).

You also have a special case that again does something particularly powerful.

$(Include=UnquotedPathToAFile) will replace the whole $(...) shebang with the content of the text file specified by PathToAFile. This is the basic tool to include external script files in other scripts. $(Must_Include=...) will do the same but now forcibly.

Best,

Peter