Pending Operation

You can manage the pending state.

You can group multiple operations into a single transaction for improved performance:

// load the customer MBO with customer ID 100
Customer customer = Customer.FindByPrimaryKey(100);
        
// Change phone number of that customer
customer.Phone = "8005551212";
        
// use one transaction to do save and submitPending
Sybase.Persistence.LocalTransaction tx = SUP101DB.BeginTransaction();
try
{
  customer.Save();
  customer.SubmitPending();
  tx.Commit();
}
catch (Exception e)
{
  tx.Rollback();
}

SubmitPending – submits the operation so that it can be replayed on the Unwired Server. A request is sent to the Unwired Server during a synchronization.
CancelPending – cancels the previous create, update, or delete operations on the MBO. It cannot cancel submitted operations.
SubmitPendingOperations – submits all the pending records for the entity to the Unwired Server. This method internally invokes the SubmitPending method on each of the pending records.
CancelPendingOperations – cancels all the pending records for the entity. This method internally invokes the CancelPending method on each of the pending records.
Note: Use the SubmitPendingOperations and CancelPendingOperations methods only when there are multiple pending entities on the same MBO type. Otherwise, use the MBO instance’s SubmitPending or CancelPending methods, which are more efficient if the MBO instance is already available in memory.

Customer customer = Customer.FindByPrimaryKey(101);
if(errorHappened) 
{
  Customer.CancelPending();
}
else 
{
  customer.SubmitPending();
}