Filter the dimension value similar to explicit selection in a filter

[punitpopli]

Hi All,

I am working on an issue where the dimension value had been moved from one category to another which work as expected when I select a filter explicitly. But have used a inline load to pass the filter value in an expression and the dimension value is not getting filtered out, details on the aforementioned scenario in below -

Dim1 has a value India, England, America.

Dim 2 has A, B ,C

I have a year selector (as a Inline load ) which had multiple values 

Dim1 and Dim 2  are used in a Pivot table with expressions where am getting year as a filter (using inline load).

When I select Year = 2022 A was suppose to display only in India and when I select Year = 2021 "A" was suppose to display only in England.

But when am selecting 2022 using inline Year selector A is coming under both India and England. Am unable to filter value A explicitly for selected year value

Any help on this is really appreciated 

Thank you in advance

-Punit 

[punitpopli]

Adding few folks for their expert suggestion

@tresesco , @jagan @marcus_sommer , @swuehl , @Clever_Anjos 

[tresesco]

Hi Punit,

It seems that your year field is in an island. And in that case, qlik would produce a cross-result for this field values when taken together with other table fields in front-end.  However, what I understand is that - even in that case, you should not  see A under England. So for me, I guess there is something else that is causing the issue. Try to create a sample demonstrative app and share for investigation.

[marcus_sommer]

Your description sound more to a missing/wrong association between your Dim1 and Dim2 - in general or maybe more specific in regard to your year-selection. If this is the case it needs to be addressed within the data-model and not with any bypass workaround in the UI.

- Marcus

[punitpopli]

thank you for your response.

but I cannot share the application as an attachment 

[punitpopli]

thank you for your response.

the association in the backend is correct. But its not working as expected with the year (from island table) selected as am using the year as a filter in an expression.

When I select the year field (i.e. not from an island table) the data is getting filtered as expected, as the year selection is enforcing the data to get associate.

I cannot change anything in the data model as this might have a huge impact, hence was looking for a tactical solution to fix this. 

[marcus_sommer]

How are both year-fields connected within the UI? I use in similar cases often a set analysis with something like this:

sum({< YEAR = p(IslandYEAR)>} VALUE)

and usually it worked well.

- Marcus

[punitpopli]

Yes, this is how have used it too

[marcus_sommer]

Maybe you could extend the logic with something like:

sum({< YEAR *= p(IslandYEAR)>} VALUE)

sum({< YEAR = p({< ... >} IslandYEAR)>} VALUE)

- Marcus

[punitpopli]

have already tried using P() but this is not working, meaning the selection is not getting enforced