topic Passing ListBox selections to another (different) ListBox in QlikView

Passing ListBox selections to another (different) ListBox

Tue, 20 Sep 2011 16:01:35 GMT

Hi all,

Let us suppose I have two different tables with the same content under different names (not linked to each other, and cannot be linked due to circular references), like:

Table A
- Cod1
- Desc1

Table B
- Cod2
- Desc2

Now let us suppose I only have a ListBox for Table A, and I can only select Desc1. The question here is, is it possible when one selects something in Desc1 it will automatically select under Desc2 (a full name match is present).

Sorry if this is somewhere available in documentation, but honestly I cannot find it.

Thanks

Passing ListBox selections to another (different) ListBox

Tue, 20 Sep 2011 18:12:50 GMT

Hi andrlopes,

you can set up an "on select"- field event trigger on field Cod1:

settings --> doc props --> trigger --> choose "Cod1" and add (edit) action: there you have to add a "Select in Field" - action with "Cod2" as Field and

= '(' & getfieldselections(Cod1,'|') & ')'

//='(A|B)'

as search mask to search (and find!) in Field Cod2 every time the same as in Cod1.

HtH

Roland

Re: Passing ListBox selections to another (different) ListBox

swuehl — Tue, 20 Sep 2011 18:14:00 GMT

Hi andrlopes,

yes I believe it is possible (If I understood you correctly).

There are some different approaches, some of them recently discussed here: http://community.qlik.com/message/149230#149230

, using Macros or actions to achieve a shadow copy of field selection.

I have attached my favorite, I use a document trigger (OnSelect trigger on field Desc 1) with an action Select in field with field [Desc 2] and search expression

='=sum({<[Desc 2]=[Desc 1]>} 1)'

Please see also attached sample. I added the listbox for Desc 2 to show the result of the copying though I believe you don't need it to get the selection in the field.

Hope this helps,

Stefan

Passing ListBox selections to another (different) ListBox

rwunderlich — Tue, 20 Sep 2011 18:46:44 GMT

That's a very cool approach using

='=sum({<[Desc 2]=[Desc 1]>} 1)'

I like it better than the concat() approach!

-Rob

Passing ListBox selections to another (different) ListBox

Tue, 20 Sep 2011 18:46:51 GMT

Hi Roland,

Thanks, it worked like a charm!

Regards,

André

Passing ListBox selections to another (different) ListBox

Tue, 20 Sep 2011 18:48:43 GMT

Hi Stefan,

Also helpfull!

Thanks,

André

Passing ListBox selections to another (different) ListBox

Wed, 21 Sep 2011 08:27:05 GMT

Hi,

Thanks for your help, but I've been wondering if it's possible to do another thing. Imagine that I have selected something on a TableC selection box and it limits the values of Cod1 (despite no selection has been made on Cod1) and they turn grey (excluded). Is it possible to pass this Cod1 excluded values to Cod2 selection box? The goal is to have the same possible selection values on both Cod1 and Cod2, despite no selection has been made!

Ahanks again!

André

Passing ListBox selections to another (different) ListBox

rwunderlich — Wed, 21 Sep 2011 13:55:36 GMT

You can shadow the change to Cod1 by addin the same action to the OnChange trigger for Cod1. The concat() technique works for this, but the sum() technique does not. I'm not sure why.

-Rob

Passing ListBox selections to another (different) ListBox

swuehl — Wed, 21 Sep 2011 21:17:19 GMT

Rob,

are you saying that you can explicitely set the selection state of field values to "possible" or "excluded" using that technique?

I tried with the concat method mentioned but didn't get it to work. It always resulted in a explicitely selected state of values (green), where I think Andre required it to be possibly selected (white).

If this (setting possible states) would be possible, wouldn't that break QV's logic easiliy, because you might set the possible selection state in a way which is not consistent?

Maybe I have misunderstood Andres request and the result of your solution is what is desired, or I have misunderstood what you suggested.

In my understanding one could only replicate the possible and excluded selection state in a duplicate table, if the duplicate, unlinked table is embedded in a data model which at least replicates the impacts to the original fields (i.e. Cod1 in this example) selection state in the original table (which might require to replicate the complete date model for the duplicate field (i.e. Cod2) in worst case?).

(Not sure if I make myself clear herewith...)

Regarding your last comment, I think you could maybe use the sum() technique in combination with p() function, I would try this

='=sum({<[Desc2] = p( [Desc1] ) >} 1)'

Best regards,

Stefan

Passing ListBox selections to another (different) ListBox

rwunderlich — Wed, 21 Sep 2011 21:40:45 GMT

Stefan,

I was not suggesting that you can set possibles through an Action. I understood Andre's query to mean that his trigger was not getting fired when possibles of Desc 1 change because of another selection. OnChange will detect that condition, but I'm still making a selection on Desc 2.

I tried the

='=sum({<[Desc2] = p( [Desc1] ) >} 1)'

suggestion and it did not work. But you may be on the right track.

-Rob

Re: Passing ListBox selections to another (different) ListBox

swuehl — Wed, 21 Sep 2011 22:01:51 GMT

Ok, misunderstood you previous post then.

I've attached a sample with sum() and p()-function like above, seems to work to me.

Regards,

Stefan

Passing ListBox selections to another (different) ListBox

Thu, 22 Sep 2011 08:35:22 GMT

Hi Stefan,

It's exactly this!

Thanks,

André

Passing ListBox selections to another (different) ListBox

Thu, 22 Sep 2011 09:03:14 GMT

Just one last question, if the contents of Desc1 doesn't have an 100% match with Desc2, is there any way of accomplishing the desired effect?

Regards,

André

Passing ListBox selections to another (different) ListBox

swuehl — Thu, 22 Sep 2011 12:49:39 GMT

André,

is there any rule concerning the differences between field values?

Passing ListBox selections to another (different) ListBox

Thu, 22 Sep 2011 13:00:57 GMT

Not really, the difference is because Desc2 table was built by joining several other tables, and the impossible combinations (for the intended purpose) are left out Desc2.

The problem is that I can only make few changes on the data model, or else I would change the inner joins to several left joins (this would be easier I presume) and like this Desc1 and Desc2 would be a perfect match, that's why I posted this extra question.

Passing ListBox selections to another (different) ListBox

rwunderlich — Thu, 22 Sep 2011 16:18:08 GMT

Stefan,

Works great! (I copy/pasted your prior example and didn't notice the misspelling of the field names).

Nice technique. I'll include in the next edition of the cookbook if you don't mind.

-Rob

http://robwunderlich.com

Passing ListBox selections to another (different) ListBox

swuehl — Fri, 23 Sep 2011 08:36:59 GMT

Rob,

sure I don't mind. BTW, I am fan of your compilation, great work!

If you are about to compile some samples of how to set states in list boxes, I think this might be also a nice example of using the set expression method

(and maybe an example for a problem where I think the method using concat / GetFieldSelections etc. reaches its limit anyway):

http://community.qlik.com/message/151017

Regards,

Stefan

Re: Passing ListBox selections to another (different) ListBox

phaneendra_kunc — Wed, 12 Oct 2011 00:11:57 GMT

Hi Stefan,

i have looked at this example of passing List box values from one to another. looks good.

i want one more additional feature as stated below.

i wants to acheive the 2nd point.

1.) if i select "aa" in Desc 1 then in Desc 2 list box same needs to be selected. (This functionality is already there)

2.) next if i clear all from or if i unselect "aa" from Desc 1 list box, then same thing should happen in Desc 2 list box too.
so it has to clear the Desc 2 listbox, if nothing was selected in Desc 1 listbox.

i have added again the exapmle of yours.

Thanks,

phani

Passing ListBox selections to another (different) ListBox

swuehl — Wed, 12 Oct 2011 12:40:04 GMT

Hi Phani221984,

the application as is should fulfill both of your requirements. I just checked on a machine with QV 10 SR2, it works.

Hm, checking more: On a version9 something (probably no SR, aaargh) I needed to remove the square brackets from the field name, i.e. just

Desc 2

instead of [Desc 2]

to make it work, but then also the clearing worked.

What version do you use?

Stefan

Passing ListBox selections to another (different) ListBox

phaneendra_kunc — Wed, 12 Oct 2011 15:43:12 GMT

Thanks Stefan,

you are right. Mine is QV10 SR1.

i have upgraded to QV10 SR3 and it is working fine.

Just to let you know it dint worked even after removeing the "Square brackets" from Desc 2.

That might be because of the Version10 SR1

Thanks

Phani