- This popup is not an error but a warning related to a Revit API limitation. Revit sees the keynote file as a single element for worksharing purposes, and reloading the file checks out the element. This means that when one user reloads the keynote file (either manually or through KM automatic reload) they get worksharing control over the keynote table. When the next users KM sees that the file is changed and tries to reload it into Revit it can’t because the first user still has control and that’s when it gives this popup message. In order to successfully reload the file the first user will need to save to central and relinquish control and the second user will have to reload from central (the same as resolving a worksharing conflict over any other element).
- Note that this does NOT affect KM reloading in its own interface and does NOT cause any risk of overwriting someone else’s changes. The KM interface will always remain up to date with other users changes when you are in multi-user mode, you just won’t see the new keynotes or changes in the Revit model until the above sync/reload happens.
- Workaround – One way to deal with this is to turn off the Keynote Watcher function. Keynote Watcher is responsible for reloading the keynotes into Revit when a change happens so turning this off will stop the automatic reload. This means that users will not be checking out the keynote table by editing keynotes so you will not get the worksharing conflict issue. However it also means that your keynotes will not be automatically reloaded in Revit; in order to see the changes in the Revit model you will need to manually reload (at which point you will be checking out the keynote table and other users will not be able to reload until you relinquish).
