For some reason our versions are no longer committing, possibly as a result of duplicate links (relationships between zones and rooms for example) and versions in the database. We tried using the Consistency Check tool but it takes a long time to run (at least the links portion) and is not fixing the errors that it finds. This issue is impacting the publication of our quarterly space planning report.
It was discovered that a user was originally having problems with a floor plan, and to resolve it they copied the existing Facilities floor plan to clear it out and rebuild it. This likely created a new version that failed to commit because of that duplication. From there, all subsequent changes were visible to that one user but not to others nor the reporting system. This resulted in the user making the change seeing it as completed, while all others did not because the Activate flag for the new entry was not enabled (required to complete the operation). The Consistency Checker tool was not able to pick up the duplicate entries/different versions so had no effect even though it appeared to do so.
While copying the existing Facilities floor plan in this manner may be technically possible, it is not recommended since it can lead to two files "owning" the same spaces/assets. See this wiki for more information about the concepts used by Facilities products to properly handle areas, assets, etc..
In order to resolve this issue, after backing up the database a Bentley Professional Services team member created a custom SQL script to delete these duplicate entries. The query essentially forced the invalid versions to become active, allowing the duplicate records to be removed by deleting entries with a lower version number. However, since this data exists in a large number of interconnected tables it is not something that is considered user accessible, even for a DBA. If for any reason you find yourself in a similar scenario, please contact Bentley Systems so that our Professional Services Team can assess your situation.