The server stores the discarded changes in the System.SynchronizationFailure entity to prevent data loss. ![]() In this case the value of the variable in the nanoflow for that object becomes empty. If the selected object originated from the server (not created on the device), and no longer exists on the server (or is inaccessible due to the access rules), the local changes are not applied and the object is removed from the local database. This is useful in case the selected object has calculated attributes or has been modified in a before/after event handler microflow. The local database is updated from the server database. ![]() The server database is updated with the changes from local database.If the selected object has local changes, the following steps are performed: In the Selected object(s) mode, if the set of objects selected for synchronization contains any objects that have not been committed yet, those objects will be skipped and thus not synchronized. The settings in synchronization configuration are not applied for the Unsynchronized objects and Selected object(s) modes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |