Top-Level Parent File Considerations
When a file is shared (for example the Parent), then all document changes made in that file are attributed to one of the users, not the user that actually made the change. There is presently no way to know which user actually modified the file.
When multiple users work in the same synchronized file (including the top-level parent), all document changes made in that file are attributed to the user that made the change.
Although changes to a file are attributed to the user that made the change, regardless if they are working from the same file, we recommend that multiple users do not work in the top-level parent file when in a SmartSync session.
To avoid this situation have:
- Users create their own local sync copy.
- Users work online to ensure they see real-time updates from their peers.
Top-level parent files need to be opened to process the events in the sync log except when they are hosted on a SmartSync Server. Opening the parent file ensures that it is up-to-date. The top-level parent file should be opened at least weekly while an engagement is active and should be opened before creating sync copies in order to ensure that the copies are current.
