# REST syncing & loading local Data

<figure><img src="/files/itsQ2reoZ2w3v7MHjhI0" alt="" width="563"><figcaption></figcaption></figure>

**Key:**

1. **Sync data from the cloud** Use a `sync-entities` action to fetch data from the cloud and store it in the local SQLite database. Use the `onLoad`, `onFocus`, `onRefresh`, or any other event where actions are defined.
2. **Load data from SQLite to use on a jig** Use the `DATA_PROVIDER_LOCAL` in the datasource defined in the jig or a global datasource to execute an SQLite query.
3. **Save data to SQLite ONLY** To save data locally only and not sync to the cloud, use an `execute-entity` action with the `DATA_PROVIDER_LOCAL`.
4. **Save data to SQLite and sync data to the cloud** Update the local SQLite and sync to the cloud in a single action to ensure high-performing user experiences without lag. Use `execute-entity` or `execute-entities` actions with `DATA_PROVIDER_REST`. Specify the function to make on the REST server, the local entity/table to update, and the method to perform on the local table. If the method is an update, delete, or save, specify the record's ID.
5. **Save data to the cloud ONLY** Use `execute-entity` or `execute-entities` actions with `DATA_PROVIDER_REST`. Set the method to the `functionCall` and specify the function to be called. The local tables will not be updated; you must sync the data from the cloud before it is available to display on a jig.

## Using sync-entities action

1. Use the `sync-entities` action to sync data from the REST data store to the local SQLite data provider. Syncing data locally results in high performance with minimal lag and ensures all data is available in the app when the device is offline.
2. Best practice is to configure a global action, the `sync-entities` action, with the REST data provider, allowing reuse throughout the solution.
3. Add the global sync action to the `onFocus` and `onLoad` events in the index.jigx file ensures data is synced to the local data provider as soon as the app loads or is focused on the device.
4. Add the global sync action to the `onRefresh` or `onFocus` events in a jig when data is changed, for example, on the list of customers, this ensures that when a new customer is created, the list is updated immediately when navigating to it or refreshing the list with a downward swipe.

## Using Execute-entity/entities action

There are two options when using the `execute-entity` and `execute-entities` actions with remote data such as REST.

1. **To update BOTH the local SQLite table and the remote data store (REST and SQL)**. To update the local table, specify CREATE, UPDATE, or DELETE methods in the `method` property of the data provider, then specify the function to use in the `function` property, and under `parameters` specify the exact data to be updated in the remote REST service. Under `data` specify the exact data to be updated in the local SQLite table.. After execution, a tempId is created, and then it is synced to the local table.

<figure><img src="/files/wuCVSREIPPaRAPdxEcBy" alt="Update local and REST providers"><figcaption><p>Update local and REST providers</p></figcaption></figure>

1. **To ONLY update the REST data store**. To update the remote data store specify `functionCall` in the method property. Then specify the function to be called in the `function` property and under `parameters` specify the exact data to be updated. Note that the data will not be visible on the jig until a `sync-entities` action is executed.

<figure><img src="/files/fdqrjX2iYBgKorWVQcrK" alt="Only update REST Service"><figcaption><p>Only update REST Service</p></figcaption></figure>

### Consideration

* Using the `save` method in `execute-entity/entities` actions will perform an upsert in the local SQLite table.
* Dealing with offline remote data is fundamental to ensuring data synchronization and consistency between the mobile app and the remote data source, allowing users to continue using the app and performing actions without interruption. [Offline remote data handling](/building-apps-with-jigx/data/offline-remote-data-handling.md) explains how to configure solutions to deal with data when the device is offline.

## Using local data provider in a jig's datasources

1. Once the data has been synced using the `sync-entities` action the data is available in the local data provider.
2. Reference the local data provider in the jig's `datasource` property to define the data required in the jig.
3. Write a SQLite query to define the exact data required.
4. Use Intellisence and expressions to reference the specific datasource values to use in each component, such as `data: =@ctx.datasources.customers`

<figure><img src="/files/RXPIwc1CZmrcjnTqoNda" alt="Local data provider"><figcaption><p>Local data provider</p></figcaption></figure>

## Example

See the [REST](https://docs.jigx.com/examples/readme/data-providers/rest) code examples that show how to use remote data store with local data provider.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.jigx.com/building-apps-with-jigx/data/data-providers/rest/rest-syncing-_-loading-local-data.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.