OK, but ignore the multiple combos, then.
In 4.1 I could use the same store on multiple combos just fine.

The error is there with just one combo.
The problem, really, is that when the combo adds the filter to the store the store is loaded, even though the store is autoLoad:false if the store has remoteFilter:true.

Why does the combo add a filter to the store? The filter data only contains a property, not a value. The value is not sent to the server as a part of the filter, it is sent as a query parameter.

The later is "ok" although i would prefer if "test" was a value property in the filter to allow it to use the same filtering logic as all other store filters.

Is this really the intended behavior?
It triggers to many problematic request for the backend. The server does not currently accept "filter" with only property and no "value". Also sending "all data" for every combo using the same data on opening the application is simply to slow. In my application the user will always search, and the store always gets additional filters before they are loaded.

Thanks.. Initial testing of the override seems to do the trick - Also working fine (afaik) with using the same store on multiple combos (In my case they should always display the same data, even if it is filtered etc)