topic Qlikview - hide some rows based on a row value in App Development

Qlikview - hide some rows based on a row value

issamassi — Mon, 20 Dec 2021 15:18:05 GMT

hi everybody. The field value is computer thought an set analysis. The variable is called "vEpression" I have a Pivot table that represents a P&L with this shape:

ID P&LNature value
1 Quantities 342

6 Gross Sales 43543

11 Gross Margin std 45345

..

i would like to create three different levels activated by three buttons. For example, at level 3, I would like to visualise just the natures (ID) 1,6,11, 18. At level 2 1,5,6,7,11,12,18 and at level 3 i would like to visualise all the levels (1,....,20). Does anyone know how to do it?
I thought about:
-this table inner join with an array containing the index that i want to visualise but I don't know how to practically do it.
-I added another dimension (let's call it ID_remove) with has 1 or 0 depending on which button is clicked and suppressing those value. In this case it suppress even other rows that are 0 ( obviously) but I don't want this to happen, moreover the pivot table doesn't allow me to hide this new expression.

Re: Qlikview - hide some rows based on a row value

Or — Mon, 20 Dec 2021 15:13:26 GMT

Your first approach sounds like it would work and probably be the simplest option...

Load * INLINE [

Level, ID

3, 1

3,6

3,11

3,18

2,1

2,5

2,6

2,7

2,11

2,12

2,18

3,1

...

3,20

];

Re: Qlikview - hide some rows based on a row value

issamassi — Mon, 20 Dec 2021 15:19:59 GMT

ok, so basically I load this new table with the pair level - id. How can I activate and visualize the the different join in the same table? (I want only one table at the time)

Re: Qlikview - hide some rows based on a row value

Or — Mon, 20 Dec 2021 20:19:13 GMT

@issamassi wrote:

ok, so basically I load this new table with the pair level - id. How can I activate and visualize the the different join in the same table? (I want only one table at the time)

Sorry, I don't understand what you mean.

You would set this field as Always One Selected, probably, to avoid multiple values being selected (though I think it wouldn't be harmful if no / multiple vales were selected, it would just show the most detailed one).