Client Side binding/inserting/deleting

[killyosaur]

I am having an issue getting the insert and delete to function correctly when working client side.  IF I bind the data client side, the insert works but the inline delete does not, if I bind server side the insert does not render correctly (until I refresh the page) but the delete works fine.  Please help.

Thanks,

Michael

[Daniel]

Hello Michael,

Please note that you have to attach OnCommand handler in order to implement the delete operation. You should manually perform the desired operation in this handler.

Other than this, I recommend that you examine the following demo if you use external buttons:
Client-side Insert/Update/Delete

Best regards,
Daniel
the Telerik team

[killyosaur]

actually that was the issue.  Apparently I didn't catch that in the demos for the client side delete, and thought it was an onrowdelete issue.  I also want to know, is there a way to persist the data added client side with out using session? Thanks!

[Daniel]

Hello Michael,

Can you please provide some more information? I'm not sure that I understand what do you mean.

Regards,
Daniel
the Telerik team

[killyosaur]

The way you handle the insert client side in your application demo utilizes the session in order to not use the database directly.  My application starts with no data and fills in the data in the grid client side, utilizing the session to know what was added to the dataset.  But if the session expires for what ever reason, I will lose my changes on that table.  Postback does not occur until after submission, and I need to pull the data from the session to store it in the database as the datasource of the rad grid doesn't seem to be holding onto the changes that were made client side.  I was curious what I need to do, to add items to an empty grid client side that can then be pulled upon submission without using the session or minimizing the session's impact.

Thanks,

Michael

[Daniel]

Hello Michael,

Thank you for the clarification. Indeed, the available options are not that much - if you prefer not to use the Session as demonstrated in the online demo, you can always fallback to the direct database access, completely ignoring the Session as a temporary storage.

Regards,
Daniel
the Telerik team