You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Details
When dynamic data is stored, a full row of data is stored locally which can contain a lot of information. This full row is then synced to the server as part of user backup/sync operations, resulting in large payloads (see related #2809)
Recommendations
See sub-issues
Further considerations
Profile restore actions will need to be handled carefully if partial states stored, as the data on the server could represent either minimal write layer as updated onto existing data, or a full row that was created by dynamic data service insert
Additional Information
See example of large sync snapshot below:
Details
When dynamic data is stored, a full row of data is stored locally which can contain a lot of information. This full row is then synced to the server as part of user backup/sync operations, resulting in large payloads (see related #2809)
Recommendations
See sub-issues
Further considerations
Profile restore actions will need to be handled carefully if partial states stored, as the data on the server could represent either minimal write layer as updated onto existing data, or a full row that was created by dynamic data service insert
Additional Information
See example of large sync snapshot below:
example-synced-data.json
The text was updated successfully, but these errors were encountered: