From f747ad76346c200f2aa289aa6470fe1ad424f2c1 Mon Sep 17 00:00:00 2001 From: Jonathan Diehl <1334574+jdiehl@users.noreply.github.com> Date: Fri, 29 May 2026 09:50:45 +0200 Subject: [PATCH] Clarify that file uploads during sync are not incremental --- .../offlinefirst-data/synchronization.md | 2 +- .../offlinefirst-data/synchronization.md | 2 +- .../offlinefirst-data/synchronization.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/content/en/docs/refguide/mobile/building-efficient-mobile-apps/offlinefirst-data/synchronization.md b/content/en/docs/refguide/mobile/building-efficient-mobile-apps/offlinefirst-data/synchronization.md index 0b7534d925a..0458895be76 100644 --- a/content/en/docs/refguide/mobile/building-efficient-mobile-apps/offlinefirst-data/synchronization.md +++ b/content/en/docs/refguide/mobile/building-efficient-mobile-apps/offlinefirst-data/synchronization.md @@ -64,7 +64,7 @@ The upload phase executes the following operations: 1. As the local database can be modified only by committing or deleting an object, such an object can be either a new object created while offline or an existing object previously synced from the server. The upload phase detects which objects have been committed to the local database since the last sync. The detection logic differs per sync type. For **Synchronize all**, all committed objects in the local database are checked. For **Synchronize objects**, all committed objects from the list of selected objects are checked. 2. There might be objects deleted from the device database since the last sync. The upload phase checks which objects have been deleted. -3. If there are any changed or new file objects their content is uploaded to the server and stored there temporarily. Each file is uploaded in a separate network request. If a file upload fails, the whole sync is aborted without causing any changes to the server or device database. +3. If there are any changed or new file objects their content is uploaded to the server and stored there temporarily. Each file is uploaded in a separate network request. Unlike the download phase, file uploads are not incremental — the full file content is uploaded whenever a file object has been modified in the local database, regardless of whether the file content itself has changed. If a file upload fails, the whole sync is aborted without causing any changes to the server or device database. 4. All the changed and new objects are sent to the server, and the content of the files is linked to the objects. The server performs referential integrity validation of the objects (for more information, see the [Dangling References](#dangling-references) section below). The objects are committed to the server database. Information about deleted objects is also sent to the server so the server can delete them from its database too. This step is performed in a single network request. 5. Any configured before- or after-commit or before- or after-delete event handlers on these objects will run on the server as usual: after the data has been uploaded and before the device database is updated. This means that any further changes you make to the synced objects in the event handlers will be applied to the device database during the download phase. There is one exception to this rule: changing the contents of a file entity is not applied when you attempt to change them in the event handlers. diff --git a/content/en/docs/refguide10/mobile/building-efficient-mobile-apps/offlinefirst-data/synchronization.md b/content/en/docs/refguide10/mobile/building-efficient-mobile-apps/offlinefirst-data/synchronization.md index e48d7a0a8ba..c89c03c2d92 100644 --- a/content/en/docs/refguide10/mobile/building-efficient-mobile-apps/offlinefirst-data/synchronization.md +++ b/content/en/docs/refguide10/mobile/building-efficient-mobile-apps/offlinefirst-data/synchronization.md @@ -64,7 +64,7 @@ The upload phase executes the following operations: 1. As the local database can be modified only by committing or deleting an object, such an object can be either a new object created while offline or an existing object previously synced from the server. The upload phase detects which objects have been committed to the local database since the last sync. The detection logic differs per sync type. For **Synchronize all**, all committed objects in the local database are checked. For **Synchronize objects**, all committed objects from the list of selected objects are checked. 2. There might be objects deleted from the device database since the last sync. The upload phase checks which objects have been deleted. -3. If there are any changed or new file objects their content is uploaded to the server and stored there temporarily. Each file is uploaded in a separate network request. If a file upload fails, the whole sync is aborted without causing any changes to the server or device database. +3. If there are any changed or new file objects their content is uploaded to the server and stored there temporarily. Each file is uploaded in a separate network request. Unlike the download phase, file uploads are not incremental — the full file content is uploaded whenever a file object has been modified in the local database, regardless of whether the file content itself has changed. If a file upload fails, the whole sync is aborted without causing any changes to the server or device database. 4. All the changed and new objects are sent to the server, and the content of the files is linked to the objects. The server performs referential integrity validation of the objects (for more information, see the [Dangling References](#dangling-references) section below). The objects are committed to the server database. Information about deleted objects is also sent to the server so the server can delete them from its database too. This step is performed in a single network request. 5. Any configured before- or after-commit or before- or after-delete event handlers on these objects will run on the server as usual: after the data has been uploaded and before the device database is updated. This means that any further changes you make to the synced objects in the event handlers will be applied to the device database during the download phase. There is one exception to this rule: changing the contents of a file entity is not applied when you attempt to change them in the event handlers. diff --git a/content/en/docs/refguide9/mobile/building-efficient-mobile-apps/offlinefirst-data/synchronization.md b/content/en/docs/refguide9/mobile/building-efficient-mobile-apps/offlinefirst-data/synchronization.md index 03728252560..9c3d32f6368 100644 --- a/content/en/docs/refguide9/mobile/building-efficient-mobile-apps/offlinefirst-data/synchronization.md +++ b/content/en/docs/refguide9/mobile/building-efficient-mobile-apps/offlinefirst-data/synchronization.md @@ -67,7 +67,7 @@ The upload phase executes the following operations: {{% alert color="warning" %}}Deleting an object from the device database is only supported in Studio Pro 9.7 and higher.{{% /alert %}} -3. If there are any changed or new file objects their content is uploaded to the server and stored there temporarily. Each file is uploaded in a separate network request. If a file upload fails, the whole sync is aborted without causing any changes to the server or device database. +3. If there are any changed or new file objects their content is uploaded to the server and stored there temporarily. Each file is uploaded in a separate network request. Unlike the download phase, file uploads are not incremental — the full file content is uploaded whenever a file object has been modified in the local database, regardless of whether the file content itself has changed. If a file upload fails, the whole sync is aborted without causing any changes to the server or device database. 4. All the changed and new objects are sent to the server, and the content of the files is linked to the objects. The server performs referential integrity validation of the objects (for more information, see the [Dangling References](#dangling-references) section below). The objects are committed to the server database. Information about deleted objects is also sent to the server so the server can delete them from its database too. This step is performed in a single network request. 5. Any configured before- or after-commit or before- or after-delete event handlers on these objects will run on the server as usual: after the data has been uploaded and before the device database is updated. This means that any further changes you make to the synced objects in the event handlers will be applied to the device database during the download phase. There is one exception to this rule: changing the contents of a file entity is not applied when you attempt to change them in the event handlers.