Logical OR Selections

[haymarketpaul]

I have a tablebox of data and a multibox of various regional areas (Country, Town, County, Postcode)

The user has a requirement to be able to select for example users in Manchester or within the TW postcode range.

If they select Manchester and then select teh TW postcode range it unselects Manchester and vice versa

Is there a certain way of going about allowing this sort of selecting?

I know the user could use the Advanced Search on an ID column and then use Wildmatch within that but it's not very user friendly.

Any pointers much appreciated

[giakoum]

So what you are saying is that you want to select Manchester and post codes that do not belong to Manchester? One way would be o select Manchester, select all postcodes that correspond to Manchester and then keep selecting postcodes with Cntrl pressed so that even more postcodes are added to the selection.

This will unselect Manchester, but you do not care as its postcodes are selected

[prashantbaste]

Hi Paul

In this scenario it seems that user is selecting data which is not related; what I mean is when user selects country and then next Postcode there might be postcode which does not belongs to selected country, that's why earlier selection gets removed.

Qlikview has very good feature of associativity, which indicates/highlights associated fields of selection.

In your case, once user selects Country, it will show postcodes activated  which belongs to selected country, rest of postcodes will be colored as 'Gray' which means they are inactive for current selections.

Give a clear idea of how this works to user.

I hope this will be helpful for you.

[richard_pearce6]

My blog Selections and Logical Inference | qlikcentral talks through how associations are made in QlikView when a user makes selections.

Richard

[awhitfield]

Hi Paul,

any chance you can upload your qvw as I'm sat in M15?

Andy

[Gabriel]

Hi,

By nature QlikView will associate where possible and as mentioned above 1 selection will give us green, gray and white.

If users requirement is to be able to make PostCode (gray) selection outside of the associate logic of QlikView then I will suggest break the associative of both tables. i.e. having 1 of the table as Island.

And if they are coming from same table move one of the field out into a new table and have it as Island.

[haymarketpaul]

Thanks for replies all.

Yes Ioannis has got the idea.

So what you are saying is that you want to select Manchester and post codes that do not belong to Manchester?

Currently i've got all the regional fields in one table so perhaps as Gabriel suggests separating them out might help.

We're constantly asked for these sort of data pots based on a combination of 'odd' regional selections.

It's GP data so hard to post an example i'm afraid.

[giakoum]

I guess what they want to see is fixed, so you could maybe create bookmarks based on postcodes

[haymarketpaul]

Would be nice but i fear there are too many weird and whacky scenarios - they can get quite specific sometimes.

[swuehl]

Maybe like attached?