Mark, I ended up changing both the language column names by adding a prefix and changing the id input parameter to row_id as soon as the execution enters the server code.  This pretty much guaranteed there will not be any surprises such as the one you mention :).

Thanks again for the responses guys.

George

Your beforeSubmit handler can delete the postdata.id field, and add postdata.row_id.

You need to be careful handling the "add" case (rather than edit), because the grid differentiates the two by checking whether postdata.id == "_empty".

You can solve that by /not/ deleting the "id" field (in which case the server will see both id, and row_id), or by adding it back in your afterSubmit function.

Mark

Hello,

Thank you for this. This is one thing that should be corrected. For now we put the id hard. We plan to change this in a way that the user will set it in a way what they want. Maybe will be available in the next release.

Best Regards

Tony

George

I have run into relatevely small problem but nonetheless worthy to mention.  There seems to be a name class between the internal id name for identifying rows and the Indonesian language code, which is also id.  The problem is shown when such language codes are set as column names.  I tried renaming the id to row_id using the jsonReader option with no effect.  So the only way I can think of fixing this is to add a prefix to such language codes when used as columns.

If you have run into this problem or similar problems and you have a better (less intrusive solution) please let me know.

TIA,

George