How To Use PowerApps Offline Apps When Your Users Are Disconnected From The Internet

How to Use PowerApps Offline When Users Are Disconnected

Power Apps supports offline use through the SaveData and LoadData functions, which cache data locally on the device. When connectivity returns, the app syncs changes back to the data source. This guide covers offline profile design, conflict resolution, and the patterns EPC Group uses for healthcare, manufacturing, and field service deployments.

Key facts

• Power Apps uses SaveData() to write data to local device storage and LoadData() to read it back when offline.
• Offline mode requires explicit design — it is not automatic. You must build the offline logic into your app.
• Filter offline data aggressively: only cache records assigned to the user, within the last 30–90 days, with active status.
• Sync at least once per day to minimize data loss risk and reduce conflict likelihood with other users' changes.
• EPC Group has built offline Power Apps for healthcare, manufacturing, field services, and logistics. 29 years of Microsoft consulting. Microsoft Solutions Partner.

How offline mode works in Power Apps

Power Apps canvas apps run in a browser or native mobile app. When online, they query the data source in real time. When offline, they need a local copy of the data.

Power Apps offline uses three core functions.

• Connection.Connected — returns true when the device has a network connection. Use this in an If() formula to switch between online and offline data sources.
• SaveData(collection, "filename") — writes a collection from memory to the device's local storage. Call this when online to cache data for offline use.
• LoadData(collection, "filename", true) — reads cached data from local storage into a collection. Call this when the app starts and the device is offline.

Step-by-step: build an offline-capable Power App

Step 1 — Design your data scope

Determine exactly what data the offline user needs. Do not cache everything. Cache too much and the app is slow; cache too little and the user cannot do their job.

EPC Group recommends these filters for offline profiles:

• Records assigned to the current user only.
• Records created or modified within the last 30–90 days.
• Records with Active status only (exclude closed, archived).

Step 2 — Load data when online

Add this logic to the app's OnStart event to load and cache fresh data whenever the device is connected.

If(
    Connection.Connected,
    ClearCollect(
        localWorkOrders,
        Filter(
            WorkOrders,
            AssignedTo = User().Email,
            Status = "Active",
            CreatedDate >= DateAdd(Today(), -90, Days)
        )
    );
    SaveData(localWorkOrders, "WorkOrders")
)

Step 3 — Load from local storage when offline

Add this to the same OnStart block to restore cached data if no connection is available.

If(
    !Connection.Connected,
    LoadData(localWorkOrders, "WorkOrders", true)
)

Step 4 — Handle user edits offline

When a user edits a record offline, write changes to a local "pending changes" collection instead of the data source.

// On save button press (offline)
If(
    !Connection.Connected,
    Collect(pendingChanges, {
        RecordID: thisRecord.ID,
        Field1: txtField1.Text,
        Modified: Now(),
        SyncStatus: "Pending"
    })
)

Step 5 — Sync when connection returns

Add a Sync button or an automatic sync trigger that detects when connectivity is restored.

// Sync pending changes
If(
    Connection.Connected,
    ForAll(
        pendingChanges,
        Patch(WorkOrders, LookUp(WorkOrders, ID = RecordID), {
            Field1: Field1
        })
    );
    Clear(pendingChanges);
    SaveData(pendingChanges, "PendingChanges")
)

Conflict resolution

Conflicts occur when two users edit the same record while offline. Define your conflict strategy before building.

• Last write wins — the most recent sync overwrites earlier changes. Simple to implement. Risk: a field worker's update gets overwritten by a manager's simultaneous change.
• First write wins — the first sync to reach the server wins. Reject subsequent conflicting changes. Requires version tracking on the server.
• Flag for review — when a conflict is detected, mark the record as "Conflict" and surface it to a supervisor for manual resolution. The safest approach for compliance-sensitive data.

For most field service and healthcare apps, EPC Group recommends flag-for-review with a dedicated conflict resolution screen visible to supervisors.

Use cases across industries

• Healthcare — clinical staff on hospital floors with poor Wi-Fi complete patient intake forms offline. Sync occurs when they return to the nurse station.
• Manufacturing — floor technicians complete equipment inspection checklists on tablets in areas with no Wi-Fi. Data syncs to SharePoint when they return to the break room.
• Field services — technicians complete work orders, capture photos, and collect signatures offline in remote locations. Sync occurs when they reach cellular coverage.
• Logistics — warehouse staff scan inventory offline in dead zones and sync when they return to the dock.

Frequently asked questions

Does Power Apps offline work on both iOS and Android?

Yes. The Power Apps mobile app for iOS and Android supports offline mode through the SaveData and LoadData functions. The desktop browser version also supports offline caching, but field scenarios typically use the mobile app.

How much data can SaveData store on the device?

SaveData stores data in the device's local app storage. The limit is approximately 2 GB on most iOS and Android devices. For very large datasets, pre-filter aggressively and consider using Azure offline data sync (via Azure API Management and a local SQLite connector) for higher volumes.

Can I use Dataverse (Common Data Service) offline?

Yes. Power Apps model-driven apps support offline mode through Dataverse Mobile Offline profiles — a different mechanism from SaveData/LoadData. Configure an offline profile in the Power Platform admin center to define which tables and filters cache to the device.

What happens if the user's device runs out of storage?

SaveData will fail silently if storage is full. Add error handling: check whether the saved collection reloads correctly after SaveData, and alert the user if it does not. Reduce the offline data volume by applying tighter filters in your offline profile.

How do I test offline mode in Power Apps Studio?

Put your test device or emulator in airplane mode. Open the app. Verify that it loads from local storage using LoadData. Make changes and check that they write to the pending changes collection rather than the live data source. Restore connectivity and verify that the sync function runs correctly.

Build your offline Power Apps solution

EPC Group has built offline-capable Power Apps for Fortune 500, healthcare, and field service organizations. Call (888) 381-9725 or request a 30-minute discovery call.