Hello!
Currently Object Types defined using Pipeline Builder are restricted in the Ontology Editor application, such that all edits must occur within the Builder app and some features are unavailable as a result.
How can I unlock these object types / migrate them somehow to be editable in the main application?
Thanks folks 
Steve
Hey Steve! We actually just GA-ed a bunch of Pipeline Builder <> ontology improvements, one of which will allow you to allow edits in pipeline builder and OMA (see screenshot where you can toggle the allow edits in PB)
If it’s not on your stack yet, and you need it ASAP, you can also disown the object (second screenshot)
We’ll be updating the docs this week to include all of the latest features so keep an eye out!
Does enabling “Allow edits to objects of this type” enable the addition of edit-only properties (in OMA) to an Ontology type created in Pipeline Builder? Or does that still require disowning the Ontology type output in PB?
I just tried enabling “Allow edits to objects of this type” on an Ontology type, but I’m still getting the error message “Properties backed exclusively by user edits are not supported for object types created by Pipeline Builder,” when I go to add the edit-only property to the Ontology type, in OMA.
“Allow edits to objects of this type” is the equivalent to this Allow edits toggle in the Ontology Manager.
Ontology Manager:
Pipeline Builder:
It won’t allow the addition of edit-only properties right now
Got it - to confirm, does that mean that disowning of types in PB, while already deprecated, will not be eliminated until there’s an alternative way to add edit-only properties to Ontology types created in PB?
Yes and we currently are not tracking a specific deprecation end date to that feature so you can expect this functionality to remain in the tool for the time being
