topic Conditionally Show/Hide Data on a table in QlikView

Conditionally Show/Hide Data on a table

alwayslearning — Wed, 25 Nov 2020 16:16:04 GMT

I have created a customised 'Listbox' using :

=If(Match($Field, 'Description', 'Product Description''), $Field)

And on the table of data I only want the specific listbox selection to appear, so I have written this in the expression of each column>

Description

SubstringCount(concat( distinct $Field,'Listbox') , 'Description')>0

Product Description

SubstringCount(concat( distinct $Field,'Listbox') , 'Product Description')>0

I have several over columns and they all work fine, however the above two. When I select 'Product Description' on the listbox, it brings back both Description & product description columns, when I select Description it works fine and displays the description column. I believe that is because of the word Description?

Can anyone assist me here, so when I select Product Description on the listbox, I will only have that column appear.

Thank

Re: Conditionally Show/Hide Data on a table

sunny_talwar — Thu, 13 Oct 2016 15:06:19 GMT

Try this:

SubstringCount(concat(DISTINCT '|' & $Field & '|','Listbox') , '|Description|') > 0

SubstringCount(concat(DISTINCT '|' & $Field & '|','Listbox') , '|Product Description|') > 0

Re: Conditionally Show/Hide Data on a table

sunny_talwar — Thu, 13 Oct 2016 15:07:43 GMT

Remember to add | (pipes) around all expression just because its more robust way to do this to avoid issues like you just had with Description and Product Description

Re: Conditionally Show/Hide Data on a table

alwayslearning — Thu, 13 Oct 2016 16:10:47 GMT

Thanks, that worked

Re: Conditionally Show/Hide Data on a table

alwayslearning — Thu, 13 Oct 2016 16:12:12 GMT

Hi Sunny,

Can you clarify what are | (pipes) effectively for in Qlikview? And when can use you use them.

As I'm still learning my way around.

Thanks

Re: Conditionally Show/Hide Data on a table

sunny_talwar — Thu, 13 Oct 2016 17:20:06 GMT

| is something unique which won't be available in your field values. That is why i used them, but you can anything else also such as @ or # which you think won't be in your field values. Nothing special about pipe |

Does this make sense?