Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Issue with Input Field/s and Boxes

Hi All,

I am a beginner at developing Qlikview Dashboards and I am looking for a way to approach a task, but can't workout myself how to do that. Basically, I want to have a table like the one below with months as columns and different products as rows showing the forecasted units to be sold of each part.

    Products (Units)JanFebMarAprMayJunJulAugSepOctNovDec
Part 11234689037803

Part 2

5678897980445
Part 3123456789876
Part 46543214678906
Part 5654790758009
Part 6646858958054
Part 72357907547907

What I want to achieve is a table like above with the option of input boxes where someone can populate the units they're forecasting and then see what number it ties out to (by multiplying the units by price as price is already loaded into Qlikview). The challenge is, I don't want the units to be blank by default but I want to show the prior forecasted units by default and then someone can change the units and play around with it. Is there a way to set an expression/variable or anything else in the input fields to bring back the units from prior forecast as default but give the option to alter those units and see the changes they make to the total revenue.

Can someone please guide me on this with the help of an example possibly. It would be great if someone can give a breif overview of input fields (as I haven't used those before) and then relate to what I want to have in the dashboard. Would be happy to answer any questions if more explanation needed.

Thanks

Zarar

1 Reply
giakoum
Partner - Master II
Partner - Master II

I believe Inputfields are more suitable for your case :

Inputfield

A field may be flagged as an input field by listing it in an inputfield statement before it is referenced in any load or select statements.

Input fields behave somewhat differently from regular fields. The most important difference is their ability to accept changes in field values, interactively or programmatically, without running the script. Field values must be loaded into the field via load or select statements. Each field value loaded in the script will create a placeholder for a field value replacement value. Only existing field values can thus be changed interactively or programmatically. The replacement value is user dependent, i.e. when an input field is used on a server, different users will see different sets of input field values

In input fields all field values will be treated as distinct, regardless if several have the same value.

The syntax is:

inputfield fieldlist

fieldlist is a comma separated list of the fields that should be flagged as input fields. The wildcard characters * and ? are allowed in field names. Quoting of field names may be necessary when wildcards are used.

Examples:

Inputfield B;

Inputfield A,B;

Inputfield B??x*;