OK, we know you've asserted you're reading the documentation, but if so, how are you unaware of the ResultSet's role as a cache manager and it's role in cache synchronization? We've referred you to the ResultSet docs multiple times, which covers in this in depth. Even the QuickStart outlines its role and encourages you to read the ResultSet docs for more information. Even the listGrid.fetchData() docs point out the creation of a ResultSet and it's role in performing filtering and sorting on cached data.
We are spending a lot of effort here reiterating what's in the docs and repeating the same things over and over - we would welcome any suggestion on how to avoid this in the future.
About what an operationId is, see dsRequest.operationId.
As far as other properties on DBCs (DataBoundComponents) that influence the requests that will be sent by that DBC, some examples are autoFetchTextMatchStyle, dataPageSize and dataFetchMode. Each of these is appropriately linked from other docs, which tell you about them in the context where it makes sense; a central doc listing all DBC properties that can influence a request doesn't solve any question we've ever seen asked.
We are spending a lot of effort here reiterating what's in the docs and repeating the same things over and over - we would welcome any suggestion on how to avoid this in the future.
About what an operationId is, see dsRequest.operationId.
As far as other properties on DBCs (DataBoundComponents) that influence the requests that will be sent by that DBC, some examples are autoFetchTextMatchStyle, dataPageSize and dataFetchMode. Each of these is appropriately linked from other docs, which tell you about them in the context where it makes sense; a central doc listing all DBC properties that can influence a request doesn't solve any question we've ever seen asked.
Comment