13.0p ResultSet cache for different operationBinding operationId issue

[Blama]

Hi @Isomorphic,

please see the testcase in #3 here.
The SelectItem and ListGrid both use DataSource filteredAggregation_orderItem.
The SelectItem uses operationId=“summary” and the ListGrid operationId=“fetch”. This can be seen in the requests in Developer Console’s RPC Tab.

Now if you click delete on a row in the ListGrid, this row also disappears in the SelectItem. This is a bit unexpected as you stated here:

Reading it is fine, just bear in mind, when two components are using separate operationIds they are assumed to have distinct caches: updates performed with one operationId will not affect the cache obtained via another operationId.

Also the ResultSet docs say:

Regarding operationIds and how they affect caching, take into account that cache sync is based on the fetch used - any add or update operation uses a fetch to retrieve updated data, and the operationId of that fetch can be set via cacheSyncOperation. If the operationId of the cache is different from the operationId of the cache update data, it won’t be used to update the cache, since the fields included and other aspects of the data are allowed to be different across different operationIds. This allows to maintain distinct caches on a per component basis, so when two components are using separate operationIds they are assumed to have distinct caches, because updates performed with one operationId will not affect the cache obtained via another operationId.

The operationId of the remove-response is not set, so I’d expect it to affect the ListGrid (because this fired the request and has a default operationId of “fetch”), but not the SelectItem.

Am I missing somthing here?

Thank you & Best regards
Blama

[Blama]

This thread is related.