[Solved] Trigger submit on client side and event on "Cancel Changes"

[IT]

I'm building a grid into a form and I'm looking for a solution to two issues:-

The first is that I have InCell editing in the grid, which is working fine, however I have controls outside the grid that add records using getJSON and then call ajaxRequest() to refresh the grid. If the user has made changes in the grid, but not yet clicked "Save Changes", then the changes are lost when ajaxRequest() is called. I would like to somehow force the grid to save before calling ajaxRequest(), however I cannot see a client side method to do this.

I also couldn't find a property that told me if the grid had unsaved changes... in the interim, I have added a "dirty" flag that gets set to true whenever OnSave fires, and is cleared whenever OnSubmitChanges fires... which is fine, however the user might click "Cancel Changes", and I would like to clear the "dirty" flag, however I can't see an event that fires when "Cancel Changes" is clicked, as with "Save Changes"

In summary:-

- Is there a client side method to "submit" the grid when InCell editing is used?
- Is there a client side property that can tell me if there are unsubmitted/outstanding changes in a grid when using InCell editing?
- Is there a client side event for "Cancel Changes" like OnSubmitChanges is for "Save Changes"

Many thanks in advance

[Atanas Korchev]

Hi Aleks,

 You can use the hasChanges() client-side method to check for any pending changes. The submitChanges() method will send the data to the server. Unfortunately there is no event for cancelling changes. However you can probably subscribe to the click event of the cancel button:

$(".t-grid-cancel-changes").click(function() {
    
});

Regards,
Atanas Korchev
the Telerik team

[IT]

Those work...many thanks.

Can you suggest to whoever manages the documentation that these should be included in the help files for the next version? hasChanges() and submitChanges() aren't in the docs for MVC Q2 2011

[Atanas Korchev]

Hello Aleks,

 We will make sure to update the documentation for the next help update.

Regards,
Atanas Korchev
the Telerik team