Data in extensible storage schema is cleared after upgrading model to Revit 2025

[ptranU2KHX]

Hello everyone,

I encountered an issue where the data stored in the extensible storage schema disappeared after upgrading a model from Revit 2024 to Revit 2025. More specifically, only extensible storage schema of view plan disappeared.

Have any of you faced a similar problem? How can this be prevented? Your assistance is greatly appreciated. Thank you in advance.

[jeremy_tammik]

That sounds unexpected. Can you provide a complete minimal reproducible case? For this issue, it sounds as if a sample RVT saved in Revit 2024 will suffice.

• https://thebuildingcoder.typepad.com/blog/about-the-author.html#1b

I asked the development team whether they are aware of this for you.

[jeremy_tammik]

If the model contsains two schemata with same GUID but different fields, one of them will be deleted when upgrading to 2025. For instance, one in model and other one on a loaded family. To test if there is a conflict in Revit 2024, you can open the model with audit. If you see the Schema conflict dialog, it means that there is a conflict. In this case, it’s working as expected. If not, please provide your model so we can take a look to see what’s happening.

[pphamTTMHH]

Hi Jeremy,

I am a teammate of ptranU2KHX.

In project 2024, we had a schema named 'SolveView,' but after upgrading to Revit 2025, the 'SolveView' schema has been deleted.

The image below shows me using the 'Revit Database Explorer' tool to check the schema, and it's clear that the 'SolveView' schema has been cleared after the upgrade to Revit 2025.

I noticed that the ListFields of the 'SolveView' schema is currently zero. Could this be the reason for the issue?

I have attached a sample project from Revit 2024.

[jeremy_tammik]

Thank you for the sample model. I passed it on to the development team.

[jeremy_tammik]

Yes, indeed, your assumption is correct. Schema with Guid {6CB8573E-800F-4F02-9A6D-28728EF52290} "SolveView" is corrupt and is automatically removed during the upgrade process.

[pphamTTMHH]

Thank you for the confirmation.

Now that we know the "SolveView" schema is corrupt and was removed during the upgrade process, what would be the best approach to restore or recreate it? Is there any documentation or guidance you can provide to help us re-establish the schema in Revit 2025?

[jeremy_tammik]

Afaik, modifying or fixing a schema is not possible. Once created, it is immutable. You have to create a new one, and transfer any existing old data from the old to the new. Of course, if the old one is corrupted, such transfer will not be possible. I assume that data is lost. Sorry for the bad news.

[pphamTTMHH]

Although the ListFields of the 'SolveView' schema is currently zero, our application doesn't rely on the values in ListFields. We only need to check for the existence of the schema, so we believe the 'SolveView' schema is not actually corrupt.
It seems our best course of action is to create a new 'SolveView' schema with a new GUID and then add a default element to ListFields.

If you have any further guidance on how to prevent this issue during future upgrades or any other considerations, please let us know.

Thanks again for your assistance.