Show TOC

Offline OData Refreshes and UpdatesLocate this document in the navigation structure

Offline OData applications use a local, offline store (on-device copy of the enterprise data) to ensure that data is always accessible, even when the mobile device is offline.

  • Updating the offline store

    Applications can make changes to data when the mobile device is offline. Those changes are made to the local offline store, then stored in a request queue. Updates that are queued but have not yet been sent to the back end are reflected in the local offline store. The application developer must ensure that the offline store is periodically updated from the back end when the mobile device is online. This periodic update is called a refresh.

  • Updating the back-end

    When the mobile device is online, a request queue flush can be performed. Flushing the request queue sends up changes that have been made to the offline store but have not yet been made to the back end. Once a request is successfully received by the back end, the request is deleted from the queue, the change is made to the back end, and a new version of that object is sent to the offline store the next time the application performs a refresh.

    Note Refreshes and request queue flushes are not performed automatically. The offline application must explicitly call the relevant Harmonized API methods to perform a refresh or request queue flush.
  • Schema upgrades

    A schema upgrade of the offline store is performed whenever a new version of the OData service is provided.