Unintended breaking changes when removing object type proeprties in the ontology manager

I recently made some changes to an object type by removing a property. I migrated the schema by dropping the edits and everything and merged the changes in the ontology.

Unfortunately, this broke an action type referencing this object type and the removed property. This breaking change went unnoticed.

Therefore, I would like to have the option to “run all checks” or “run all tests” before merging. Fortunately, the ontology manager quickly finds the problem in the rules of the action type when opening the action. I think this should also be checked before merging/commiting the changes and if in doubt require a migration to ensure the stability of more complex ontologies without extensive e2e testing.

1 Like

Hi @Flackermann

Sorry, that you ran into this issue. We have just added a validation whenever you delete a property in the Ontology Manager to check whether the property is referenced in any action type, (This will unfortunately not include any potential function backed action types that may reference this property), and will block you from deleting the property until you’ve updated your action type as well. Hopefully this helps so you don’t run into this issue again!

1 Like