You can manage the pending state.
[customer submitPending];
[customer cancelPending];
(void)cancelPending cancels pending changes for a particular instance or instances (via (void)cancelPendingObjects from the database class). However, if (void)submitPending has already been invoked, only the pending state and original state (for update) are removed. The operation replay record generated by the (void)submitPending remains. This means that the operation replay record is uploaded to SAP Mobile Server upon synchronization. If the EIS honors the operation replay, the changes are propagated back to the device during the download. The Object API framework forgoes operation replay completion processing when it finds that there are no pending/original states for the instance. Hence, (void)cancelPending is not the inverse operation of submitPending.
[Customer submitPendingOperations];
[SMP101SMP101DB submitPendingOperations:@”default”];
[Customer cancelPendingOperations];
SMP101Customer *customer = [SMP101Customer find:101]; //Make some changes to the customer record. //Save the changes //If the user wishes to cancel the changes, a call to cancel pending will revert to the old values. [customer cancelPending]; // The user can submit the changes to the server as follows: [customer submitPending];