Schema Conflicts in Revit 2024

Issue:

Some Naviate users reported that Schema Conflicts are encountered after upgrading to Revit 2024. Seems like this is related to issues in Revit 2024 and how they manage Schema ID.

This is impacting all companies developing add-ins on top of Revit. See article on Autodesk https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/Schema-Conflicts-with-DatasmithRevitExportSettings-and-DataStorageUniqueId-in-Revit-2024-1.html

Schema Conflict when Loading a File

The file being loaded is causing a conflict with existing data in the model. What do you want to do? The file contains data of schema "<Schema Name>" (from ""), which has the same ID as a different schema already in memory. If the file is loaded, the existing data will be erased from the model.  

Note: Depending on the schemas involved, selecting the option to continue loading the file could lead to the deletion of model elements.

Solution:

2024.1.1

• Update: The Revit 2024.1.1 update should prevent element deletion or crashes caused by schema conflicts for newly created models or models upgraded from versions prior to 2024. 

Ensure everyone is updated to 2024.1.1.

• Old Data: The update will not resolve conflicts introduced in Revit 2024.0 / 2024.0.1 / 2024.0.2 / 2024.1.
• New Conflicts : If a schema conflict shows up for models upgraded/created with 2024.1.1, click the ‘Continue loading the file’ option to move forward.  

Model Modified before 2024.1.1

If the model was upgraded / modified in a 2024 version before 2024.1.1, and encountering the schema conflict, use one of the following options to get the model into a good state:

• Re-upgrade model: If the model was recently upgraded from a prior version, re-upgrade the model from the prior version (for example 2023, 2022...) to the 2024.1.1 (or later) version.
• Recover backup: If the conflict shows up after working/saving for a period of time in 2024.0 / 2024.0.1 / 2024.0.2 / 2024.1 versions of Revit, go through the following steps to see if there is a good backup that can be used:

1. To get a good copy of the model schemas, upgrade an old version of model (prior to 2024) to 2024.1.1 or later version and save a copy of model for this process. This step is important as the conflict relates to two schemas, and this gives a good copy for Revit to compare against when opening backups.
2. With the newly upgraded model open check if a backup copy of the model can be found/opened without the conflict.

Check Modified Versions: If you are not sure if the model was modified in a 2024 build of Revit before 2024.1.1, go through the following steps to check:

1. Close and re-open Revit.
2. Open the model in question.
3. Check the Revit journal for the section that starts with "Document save history -->"
4. Check the 2024 versions of Revit, the model has been saved with:

• 20230308_1635 - 2024.0
• 20230411_1515 - 2024.0.1
• 20230509_0315 - 2024.0.2
• 20230701_1515 - 2024.1