We create replicas using the CreateReplica endpoint of a feature server, specifying sqlite as the output type, so that we can work with data offline. We're not using a versioned geodatabase, so when we sync data back, the syncModel is "perLayer". When we sync back we first upload the delta .geodatabase file and use the SynchronizeReplica end point and specify "async:true" and specify the uploadid. This works fine, but I'd like to understand if the following is possible:
1. A delta contains valid edits to 10 features in a single layer, an attempt is made to sync these changes back, but something goes wrong. Is it possible for only some of the edits to have sync'd back, or is the sync treated as a transaction in the database, and either all edits make it back or no edits make it back?
2. Similar to the above, but the delta contains edits to multiple layers. Is it possible for edits to be sync'd back to some layers but not others?
I know there is an option on the SynchronizeReplica endpoint to "rollbackOnFailure", but this isn't valid with nonversioned geodatabases.
We are looking for answers to these questions so that the correct remedial action can be performed on the database if the sync fails.
