Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us to spark ideas for how to put the latest capabilities into action. Register here!
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Need help with input variable

S.noSubject1Subject2Class
15206175A
23151400B
3623445C
52545A
6225702B
736541512C
8400513350A
915753060B

need to create input showing the % of Subject 1 value. for eg      if i put 5 % in input box i shud get a chart/table showing the value of subject1 which is 5% of subject2.

6 Replies
Not applicable
Author

Hi qlikviewnext,

I would create a new field during the load instead of a variable. The new field has all values (ratios)  and can be used as a filter for ex. via a listbox. See attached app for more details.

HtH

Roland

Note:

The current selection was made using "<=30%" as searchstring of the listbox.

sujeetsingh
Master III
Master III

Roland,,

A nice reply... but why not to give a input box with a variable set up..

Not applicable
Author

Looking for input variable solution..I've 1 more field Completed%.  So i wud ve 2 variables 1 for x% of subject values and other for completed %.

fosuzuki
Partner - Specialist III
Partner - Specialist III

I'd use a part of Roland's solution, which is to create the ratios in the load script.

Then, in the interface, your expression could use set analysis like:

sum({<SubjectRatio={"<=0.30"}>} Value)     this would calculate the "Value" for the items where SubjectRatio is less than or equal 30%.

Hope this helps

Fernando

Not applicable
Author

Hi Son of Sardar,

thank you for compliments.

I prefer the use of a field instead of a variable because its calculation is done during loadtime. The calc of a variable (often even if you don't need it) is done during user onlinetime. This means not much in a smaller enviroment with a few users and small data. But it may slow down applications working on poor hardware and(or) hugh amounts of data.

Second reason is that it seems to me to be more flexible, ie in listboxes and in SET Analysis (like Fernando posted)

RR

fosuzuki
Partner - Specialist III
Partner - Specialist III

I agree with you Roland. Always when possible do the calculation in the script. It will avoid degradation in performance for the end user. Especially when you are dealing with millions of rows, this can make a huge difference.