[deleted]
-
Last edited by apastel; 9 Nov 2017, 13:31. -
A likely cause for this is returning data in the DSResponse for the "add" operation that doesn't match the primary key value of the record that was saved.
By enabling the "ResultSet" logs and looking at the response data in the RPC tab of the Developer Console, you should be able to see logs of what's going on, and check for mismatches between the PK in the data being saved and response.
It may be a subtle typing issue such as returning a String for a field that should be an integer value, or something along those lines. Some fixes in the values comparison and search code for 6.1 might have revealed a pre-existing bug in your application code along these lines.
-
-
Did you look at the ResultSet logs? That was our first suggestion, and it should tell you exactly what is going on in the cache. That would actually be the starting point for any investigation of cache updates going awry.Comment
-
-
You've shared so little information about your code that it's hard to speculate. One possibility would be that you are repeatedly registering an event handler that only needs to be registered once, so your code ends up firing one extra time each time the event fires.
An easy way to get more information is to use SC.traceLogMessage() to get a stack trace for each of the update logs. That will show you the calling code.
Also, are you hand-creating ResultSets via "new ResultSet()"? And are you using DataSource.updateCaches()?Comment
Comment