Is it possible to delete a replacing schema when you have also created inheriting schemas based on that schema? I've tried this, and it seems to turn the inheriting schemas into being read-only, showing the following message when trying to edit them:
Here is an example set up for this issue:
- Create a replacing schema of FileDetailV2 (called FileDetailV2, as it as to be)
- Create a schema inheriting from FileDetailV2 (any name)
- Delete the replacing schema created in step 1
Once these steps have been performed, it appears the inheriting schema created in step 2 is now read-only for some reason. My expectation would be that, because the OOTB FileDetailV2 still exists, there should be no issue. Does anyone know how to resolve this?