SetFilter limitation and how it works

Hello Experts,

I am using setFilter function in my design studio 1.5 application on HANA as backend. If we want filter the data set using a key, which is not there in the data set, it returns all data, considering the key value as "ALL_Members". By I want no data to be returned for that scenario.

Seem, like this is how setFiler functionality works, and we do not have any option there.

One alternative could be using setVariableValue, but wanted to check what would be the performance impact.

In other wards, if I do a setfilter does it go back to the backend and execute the query there like setVariableValue or it only does the filtering at design studio end? If setFilter goes back to the backend, I do not see think there would be any difference on performance on using setVariableVal instead of setFilter.

Note -- I am not using any merged prompt for my application, so using setVariableValue not going to initiate execution of any other backend Model.

Thanks,

Supriya Das