topic Re: Filters valued but not chosen in App Development

Filters valued but not chosen

danosoft — Thu, 16 Sep 2021 13:50:32 GMT

If I do certain filters (for example if I choose my DES_REFERENT field) I notice that in the object where the list of filters is displayed I learn a filter that I have never put, and I would not want it, on what does this behavior depend?

For example:

it has been inserted autonomously and I would not want it, because if I change the filter in DES_REFERENTE this previous CD_FORNITORE limits me the view of the rows (which should not have selected it)

Re: Filters valued but not chosen

rubenmarin — Sat, 18 Sep 2021 09:19:36 GMT

Hi, This behaviour can be caused beacuse of an Aggr() function, like Aggr(DES_REFERENT, CD_FORNITORE), this will show DES_REFERNT values but the selections will be done in CD_FORNITORE.

This value can also be set by triggers.

Re: Filters valued but not chosen

danosoft — Mon, 20 Sep 2021 07:30:37 GMT

do you mean that somewhere in some expression around there might be an AGGR function causing this behavior?

Re: Filters valued but not chosen

rubenmarin — Mon, 20 Sep 2021 09:22:18 GMT

If this is a filter that exists when the app is opened most propably it's because of a trigger, open configuration menu -> document properties ->triggers, there may be something that makes actions on start, it could be direct actions to select values or executing a macro that makes the selctions

Re: Filters valued but not chosen

danosoft — Mon, 20 Sep 2021 09:36:30 GMT

No, it is not a trigger and CD_FORNITORE is not set by anyone as a filter

Re: Filters valued but not chosen

danosoft — Mon, 20 Sep 2021 09:48:46 GMT

How can I find if there is an AGGR function in one of the expressions used (there are a lot of them)

Re: Filters valued but not chosen

rubenmarin — Mon, 20 Sep 2021 16:13:06 GMT

Is the value selected when you open the app?.

Aggr will only select values in another field when user selects a value, or by a trigger.

There is also the option that CD_FORNITORE field has the option to 'always one value selected' ebnabled, you can add a list with this field to check if it has the option enabled.

Re: Filters valued but not chosen

danosoft — Tue, 21 Sep 2021 08:25:25 GMT

Is the value selected when you open the app? NO

I DON'T have a filter that works on CD_FORNITORE, so I don't understand why it is selected if I select DES_REFERENT

so i think it may depend on an Aggr, as you said earlier, but how can i find where this Aggr expression is in the whole document?

Re: Filters valued but not chosen

rubenmarin — Tue, 21 Sep 2021 13:01:16 GMT

If it's done when you select DES_REFERENT you have to check the object where you are selecting the values to see if it's using an aggr.

This would be easier if you can upload a sample to check

Re: Filters valued but not chosen

danosoft — Tue, 21 Sep 2021 13:14:11 GMT

in the object i have this expression (the object is a listbox):

=aggr(Concat(DISTINCT {<DES_REFERENTE=P(DES_REFERENTE), DES_REFERENTE=>} DES_REFERENTE), DES_REFERENTE)

when i choose one.... it put in the selection CD_FORNITORE

Re: Filters valued but not chosen

danosoft — Tue, 21 Sep 2021 15:49:09 GMT

I noticed that CD_FORNITORE appears to me when you select DES_REFERENTE which have only one value in the table in CD_FORNITORE (in this case ECO), while for those DES_REFERENT I have more values, that filter CD_SUPPLIER is not selected .... I don't understand, however, why I automatically Qlik go to select that field ...

Re: Filters valued but not chosen

danosoft — Thu, 23 Sep 2021 09:30:13 GMT

I find the problem:

I have the trigger:

on each selection

this:

and in the expression i have this: =if(UPPER(OSUSER())='THISTHISTHIS','VALUE',CD_FORNITORE)