"Then, upon save, you could perform your custom logic that would apply the changes to all future occurrences if that option has been selected."
I am using a server side data source with the transport-submit function for handling the create, update and delete requests, see code snippet:
submit: function (e) {
const data = e.data;
//data.created
//data.updated
//data.destroyed
}
Where in the process/flow is it best to apply the custom logic that defines the "dirty" data so that the state of data.created, data.updated and data.destroyed looks how I want it to?
Is it in the save event? Or is there another place where it is better?