2024.1 Update causes new Schema errors

[GlynnisVP]

There's been a lot of chatter about the Schema error that was landing in a post about What's New in 2024.1 so I took the good suggestion from @RobDraw  to start a new thread here.

What is a Schema?

I welcome other people's input on this, but from my perspective, a schema can be best thought of as a blob of Revit metadata, held in Extensible Storage workset, that has a unique GUID. This blob of data is most often used by 3rd party developers but is also used by Autodesk (or companies acquired by Autodesk). The structure of that data, per each GUID, needs to be the same. If a developer alters the data structure, then a new GUID is needed to avoid the error.

What causes a Schema error?

In order to experience a Schema error, you need to have two files (or a file with a linked file) that have the same schema GUID but with a different data structure. Whichever file is opened first 'wins' within the active Revit session. This makes solving these problems REALLY hard because the file that displays the error is not necessarily the file with the 'problem' schema. It's also why this problem seems to be squashed sometimes and then resurface later. If you only ever open one Revit file at a time within a session of Revit, you'll never see the error.

What's the New Problem

The new problem seems to relate to Revit files that are upgraded to 2024/2024.1. The 11 July Revit 2024.1 release notes show that in there were changes made to the API to try and fix an outstanding schema condition. It feels like that change may have created some new conditions. We have an open case with Autodesk on this issue.

There are three new Autodesk solutions that suggest that to avoid the problem you need to upgrade your pre-2024 files one at a time to avoid a crashes, deleted data, or the error dialog prompt.

• https://help.autodesk.com/view/RVT/2024/ENU/?guid=GUID-38030A32-0460-4A2A-92D8-B698C0B01161
• https://help.autodesk.com/view/RVT/2024/ENU/?guid=GUID-40B0224D-9925-449B-84D0-8241EA15849A
• https://help.autodesk.com/view/RVT/2024/ENU/?guid=GUID-A8A5E4FD-8671-4B00-B3E6-CB4707D80744

I am hopeful that these are just interim workarounds to a problem that will be fixed. We have not changed our Ideate Software schemas and yet our customers are experiencing this issue.

[Sahay_R]

FYI pyRevit also has a Schema Cleanup tool (it’s under Wipe). Has anyone tested that yet? 

[robertas_suminskas2]

I tried it doesn’t work also I tried other tools as well. The problem is in Revit Code. They did changes what is causing conflicts.

I was trying to find out why schema should main driving thing in Revit? 

[josephsWYW3U]

Yes, we tried PyRevit’s Schema remover. The issue with PyRevit was that it was unable to “see” the particular schema we were trying to remove (enigma schema).