Dissociating/Isolating Screen Selections in different Display Tabs

[#1]

I have 1 unique application with 2 data model subdivisions corresponding to separate display tabs, representing respectively International Sales and Contests. Client and Company Dimensions are in common between the 2 sets of tables.

I would like the Contest Year selection not to affect the Sales Tab data;Sales year and Contest year are different and I do not link the contest year to the Calendar.

Still  when I choose the Contest Year it modifies the Sales Data.

I think this is because it associates to a subset of the Client Dimension, the Company ID of which connects directly to the Fact table where the Sales metrics are.

Is there a technical trick to isolate the Sales part of the Data Model from the Contest Year Selection? 

Thanks

[rajeshvaswani77]

This would break QlikView functionality. However you can achieve this by both the International Sales and Contests not having any common fields that make them link.

thanks,

Rajesh Vaswani

[#3]

I sort of understand that selections are sort of like a giant query of the data model with all its connections, as viewed with Table Viewer. So logically the behaviour I describe is what QV does.

I was thinking of a trick to solve my problem, for example some particularity of set analysis that I could implement in the Contest Tab with the year list being just a pseudo to an island table or something like that.