Designing an Offline Application to Handle Conflicts and Errors

Design your offline OData application to handle any conflicts and errors. You can provide detailed information about errors via the ErrorArchive.

By default, an OData Offline Store does not encrypt the data it collects and stores on the device.

The ErrorArchive logs business logic errors and ETag mismatch errors. You can configure an offline application to access the ErrorArchive so that end users can read and delete logged errors.