If I understand your last response, the PagingMemoryProxy only works with array readers. I have reviewed the documentation trying to figure out how to make a JsonReader an ArrayReader. We are using a JsonStore and the root element is the array of data. I tried this and I do not get any error and the display is still wrong. Also I do not understand why all rows are displayed when I specify a limit of 25? I am using fire fox and tried to debug the problem. I set several break point in PagingMemoryProxy not of them were hit. I question whether or not I have set this up correctly. I down loaded the PagingMemoryProxy and added 2 folders, ux and data.

yes the array is in the jsonReader, jsonData.rows is thew data array. Going through the debugger, I can see jsonReader.jsonData.rows in the debugger, but when I try to reference it, I get not defined error. Not sure why perhaps this is private data?

PagingMemoryProxy and EditorGrids

Hey, thanks for the great addon. We're really getting a lot of use out of it.

So far, we've only used PMP on GridPanels, but now we're needing to use a PMP on an EditorGrid. All the data is being served up correctly, but we have a problem when update a record or add a new one.

When I add a new record, enter some values for it, then sort my grid, the new record is disappearing. The same thing occurs when I edit an existing record, except that the edits disappear (but the record stays).

I'm thinking that I may need to send the new record or edits back to the proxy (we're using remote sorting and remote filtering). Right now, when I add a new record, I do this (the insert is in red):

@mrollins -- Yes, ultimately you have to do the same thing you would with a real server. The PMP is, in essence, your server. Currently PMP is coded for read-only use, so you must update/append each row in the proxy.data array when you commit the store changes.