Input box approach to different goal in each of 8 weeks?

[stevelord]

Hi Community, I recently setup an expression to count the number of weekly goals met over a period of time, but it hinges on a variable entered in an input box (the goal value to be met- say walk 49000 steps that week).

Is there an efficient approach to setting up inputs for as many as 8 different weekly goals?  So instead of vWeeklyGoal, it would be like vWeek1Goal, vWeek2Goal, vWeek3Goal, etcetera.

Now some challenges will still be fine with one input box if the goal is 49000 every week, and some will want gradually increasing amounts each week (not always the same increment).

Any good or best practice design approaches to managing so many variable inputs?

Thanks!

[Gysbert_Wassenaar]

You could create an excel file with the goals and load that as a table into Qlikview. Or perhaps you can create a table with an input field so users can change the goals themselves.

[stevelord]

Can you elaborate on 'table with an input field'?  How do I set that up?  (It sounds similar but not quite the same as my current setup,)

------------------------

My current setup:

I have a straight table with expressions that have >=vMinutesGoal and such.  User enters goal into a variable input box, and the affected fields return a 1 if the people met the goal and 0 if not.

Offhand future setup I can think of is a container object with as many as ten variable input boxes (one for a single overall goal, one for current week goal, and 8 for the goals related to each week.

[Gysbert_Wassenaar · Accepted solution]

See this video:

[stevelord]

Marking helpfuls at the moment.  I've been diverted and lack bandwidth to test/implement but will be back with correct answer credit for whichever I use.  (It's a bit subjective design-wise, and you're not lacking points, just saying.. )

[stevelord]

Since some clients have only 2 activities and some have 123, I went with a hybrid approach that incorporates the variable field.

So in my table, I have four columns that count the number of people who completed 1,2,3,or 4 of the activities (there's an if num(count(rangesum(aggr()))) something = number expression), then a variable field for the user to enter 5,11,a million or whatever.  I had thought about getting the table to 20 columns wide, but the expressions seemed demanding on the memory so I pulled back to a handful of columns and let the variable column handle the edge clients.

Thanks again Gysbert, you've been a rockstar the past couple years.  Venturing answers where others fear to tread.   (Plenty of other super people here, but not many who are consistently the lone respondent to whatever insane question I just asked. )