Skip to content

Commit 04e1b48

Browse files
committed
Updates for improved implementation
1 parent 444e196 commit 04e1b48

File tree

2 files changed

+16
-8
lines changed

2 files changed

+16
-8
lines changed

powerapps-docs/maker/canvas-apps/functions/function-savedata-loaddata.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,9 +22,13 @@ The **SaveData** function stores a collection for later use under a name.
2222

2323
The **LoadData** function re-loads a collection by name that was previously saved with **SaveData**. You can't use this function to load a collection from another source.
2424

25-
**LoadData** doesn't create the collection; the function only fills an existing collection. You must first create the collection with the correct [columns](../working-with-tables.md#columns) by using **[Collect](function-clear-collect-clearcollect.md)**.
25+
**LoadData** doesn't create the collection; the function only fills an existing collection. You must first create the collection with the correct [columns](../working-with-tables.md#columns) by using **[Collect](function-clear-collect-clearcollect.md)**. The loaded data will be appended to the end of the collection; use the **[Clear](function-clear-collect-clearcollect.md)** function first if you would like to start with a clean slate.
2626

27-
Storage is encrypted and in a private ___location on the local device, isolated from other users and other apps.
27+
Storage is encrypted and in a private ___location on the local device, isolated from other users and other apps.
28+
29+
These functions cannot be used inside a browser either when authoring the app in the Studio or running the app in the Web Player. Use a native player on a device to test your app during development.
30+
31+
These functions are limited by the amount of available app memory as they operate on an in-memory collection. Available memory can vary depending on the device and operating system, the memory used by the PowerApps player, and the complexity of the app in terms of screens and controls. if you store more than a few megabytes of data, test your app with expected scenarios on the devices you expect to be used.
2832

2933
## Syntax
3034
**SaveData**( *Collection*, *Name* )<br>**LoadData**( *Collection*, *Name* [, *IgnoreNonexistentFile* ])

powerapps-docs/maker/canvas-apps/offline-apps.md

Lines changed: 10 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -21,13 +21,17 @@ One of the most common scenarios you face as a mobile-app developer is enabling
2121
* Launch PowerApps Mobile when offline.
2222
* Run apps that you develop when offline.
2323
* Determine when an app is offline, online, or in a metered connection by using the [Connection](../canvas-apps/functions/signals.md#connection) signal object.
24-
* Use [collections](../canvas-apps/create-update-collection.md) and leverage functions such as [LoadData and SaveData](../canvas-apps/functions/function-savedata-loaddata.md) for basic data storage when offline.
24+
* Use [collections](../canvas-apps/create-update-collection.md) and leverage functions such as [LoadData and SaveData](../canvas-apps/functions/function-savedata-loaddata.md) for basic data storage when offline.
25+
26+
## Limitations
2527

26-
> [!NOTE]
27-
> This feature area is still under development and isn't optimized for every scenario today. The functions
28-
to SaveData() to a local device and LoadData() from that device work best in their current implementation over relatively small quantities of data (for example, dozens of text records in a table) that generally don't exceed 2MB. This is useful for some basic “offline” scenarios, as well as to increase the startup performance of canvas apps by caching data locally. However, using this feature to save large amounts of data (for example, saving thousands of rows in a table or caching large images or videos) may cause errors or unexpected behavior with the current implementation and should be avoided. Also, the functions don't automatically resolve merge conflicts when a device returns to connectivity from offline – configuration on what data is saved and how to handle reconnection is up to the maker when writing expressions.
29-
>
30-
> We are working to expand the capabilities of offline apps, to increase stability and size limits, and (in the future) to automatically handle decisions about what to save and how to handle conflicts. Stay tuned here and on the [PowerApps blog](https://powerapps.microsoft.com/blog/) for updates when they become available.
28+
LoadData and SaveData are a simple mechanism to store small amounts of data on a local device. Using these function you can add simple offline capabilities to your app.
29+
30+
These functions are limited by the amount of available app memory as they operate on an in-memory collection. Available memory can vary depending on the device and operating system, the memory used by the PowerApps player, and the complexity of the app in terms of screens and controls. if you store more than a few megabytes of data, test your app with expected scenarios on the devices you expect to be used.
31+
32+
The functions also don't automatically resolve merge conflicts when a device returns to connectivity from offline – configuration on what data is saved and how to handle reconnection is up to the maker when writing expressions.
33+
34+
We are working to expand the capabilities for offline scenarios. Stay tuned here and on the [PowerApps blog](https://powerapps.microsoft.com/blog/) for updates when they become available.
3135

3236
## How to build offline capable apps
3337

0 commit comments

Comments
 (0)