I seem to be having some trouble getting access to the entity schema I created.
About 7 years ago, I created an app that reads & writes a schema to the project info element. A year later I created another app that only reads this schema. Now I am updating the second app and I find with Revit 2019 it can no longer read the schema. I keep getting the error "Schema not available to this application" but in the schema builder the read\write access is set to vendor. The name, guid and vendor id are set the same in both apps. I can still get the schema with the latest version of the app that created it, it's just the second app that can't.
Is this a bug in the most recent API's?
Solved! Go to Solution.
Can you possibly provide a minimal reproducible case for us to pass on to the development team for analysis?
https://thebuildingcoder.typepad.com/blog/about-the-author.html#1b
Never mind. I figured it out.
I had loaded my app through the wonderful add-in manager you created. So the schema thought it was the add-in Manager that was trying to access my schema. Everything works properly if I load my app with the manifest file without ever having loaded the app through the manager.
Good to hear you got it sorted! Well done. Thank you for letting us know. What a relief 🙂
You can try to change the vendor/addin identification in the AddInManager .addin file to yours. I do this with Revit Lookup to snoop my extensible storage.
That's a very simple and very cool idea! Thank you!
Can't find what you're looking for? Ask the community or share your knowledge.