Using NOT EQUAL TO in List Box Selection

[nathanfurby]

Hello All - my very first post how exciting [:)] I am a complete QlikView newbie so please be patient.

I have inherited a small QlikView document in my new role and will try not to flood the forums over the coming weeks. The previous designer chose to utilise one large FactTable to contain two different sets of data (something I'm told by others is quite common).

I have been asked to create a button which will exclude/include records with a certain value. I have done this using a Toggle Select Action on a couple of buttons and 'Chart A' displays correctly. The problem is that the values occur on one side of the FactTable but not the other - so another 'Chart B' shows 'No data to display' because all the values in the field that I am evaluating are NULL.

Is there a way to use '<>' or 'NOT' in the Search String of the Toggle Select Action so that all the values I want displayed PLUS ALL THE NULLS will be included?

Please let me know if I am not being clear.

[nathanfurby]

Adding an example file to try and illustrate my problem a little better.

Thanks

[fernandotoledo]

I think you should improve your data cloud. All data you want to display should be somehow associated with the selected values. Try using a structure like a Link Table, unifying all combinations of keys between your facts, or join the fact tables into one big table.

[nathanfurby]

Thanks for your response Fernando. The data in my real world example shares only a couple of common fields with most of the data being unrelated as shown in the example.

Are you suggesting in this situation to seperate the data from the FactTable into two seperate tables and link the common fields via additional tables? This makes sense to me but I have more experience in relational databases and not QlikView so not sure if it is correct.

[nathanfurby · Accepted solution]

So the proper solution may be to amend the data model, but as I inherited this I will not be doing that just yet.

If anyone is interested - the solution I used was to force a value to be inserted at Data Load for the NULL column.

The equivalent in the example I posted would be to insert 'Banana' in Column A for the Vehicle 'dataset'. This is far from ideal but it fits what I want to do as I know the users always want to exclude on 'Orange' rather than 'Banana'.