Skip to content

Accessing ErrorArchive

ErrorArchive logs business logic errors and ETag mismatch errors. An offline application can access ErrorArchive and allow application users to view, delete or resolve errors within it.

ErrorArchive is exposed to the application as an OData entity set and is accessible through the OData API in the same way that the application accesses any other entity sets from the offline store.

Besides the dynamic API, a built-in proxy class named OfflineODataErrorArchiveEntity enables you to easily access ErrorArchive.

Last update: October 30, 2020