Qlik Community

QlikView Creating Analytics

Discussion Board for collaboration related to Creating Analytics for QlikView.

stevelord
Valued Contributor

Make a listbox ignore other listboxes, but not alternate state?

Hi, I have some text objects and tables with count(Distinct {<field1, field2>}, if(field3>0, UserId)) type expressions to let them focus on getting the final answer for the relevant selection and disregard the others.  I was aiming for people to be able to select in field1, field2, field3 then read final answers from the charts and boxes without further ado.

Then I realized the listboxes themselves could constrain possible selections in each other and therefore possible selections feeding the charts and objects.

Is there a way for me to have the listboxes ignore each other and just use them for feeding the charts and tables? Or should I kick them off and revamp around variable input boxes instead?

For variable input boxes, my expressions would shift to something like count(Distinct if vField3>0, UserId) which looks like a simpler best practice aside from the fact I'd have to redo almost everything on my sheet.  Hoping for an 'ignore the other listboxes' checkbox somewhere instead.

Thanks!

3 Replies
stevelord
Valued Contributor

Re: Make a listbox ignore other listboxes, but not alternate state?

not seeing the edit button here... I wanted to correct the expressions to make them technically accurate (remove the excess comma in the one and put the missing paranthesis in the other), but they illustrate the gist of my approaches.

Re: Make a listbox ignore other listboxes, but not alternate state?

May I ask why you wish to avoid Alternate States ?

stevelord
Valued Contributor

Re: Make a listbox ignore other listboxes, but not alternate state?

Trying to make it a 0 skill, one set of selections, single qlikview sheet process for the end user.  That said, two items in the list of items have me thinking of alternate states and multi-state expressions now.  End user will know the following:

Alternate states might be like

date range for activity 1 (listbox, alt state 1)

date range for activity 2 (listbox, alt state 2)

1-3 source values for activity 2 (listbox, alt state 2)

season value for activity 3 (listbox, alt state 3)

1-X values for activity 3 shortnames (listbox, alt state 3)

Clients have pretty much the same questions and report format (who did 1, who did 2, who did 3, who did only 1, who did only 2, who did 1 and 2, who did 1 and 2 and 3, who did X of 3, who did ALL of 3), but completely different values for all of the above..

The end users are smart people and don't necessarily need me to build for 0-skill, but there's a fair managerial/strategic demand for me to produce things my 7 year old could operate without risk of error.   I have a lot of things down to where people click the client name, export from the correct table, and call it done, but this one is like combining... everything.

Supposing I'll go dig up papers for syntax to reference multiple states in single formulas, but feel free to throw me a line.

Community Browser