Following on this thread: Can I create an Object Type in an Ontology, with a backing dataset in the non-corresponding namespace? - Ask the Community - Palantir Developer Community
**Feature Request:**
When creating an object type with a dataset in a specific space, the system should automatically align the private ontology of that space, rather than defaulting to the most recently select ontology in the Ontology Manager.
I understand, backing dataset namespace location does not restrict the choice of Ontology within which one can create an Object Type. Nonetheless, the default behavior can cause object types to be created under an unintended ontology, requiring manual migration to the correct one or deletion. This behavior is error-prone, unintuitive for users, and often only detected when attempting to bundle DevOps products for the marketplace — where failures occur and the provided errorInstanceID offers little diagnostic value.
Proposed Enhancement:
Update the Object Type Creation Wizard so that:
-
The ontology is determined based on the dataset and space context in which the object type is being created,
or
-
The wizard prompts the user to choose the ontology explicitly during creation.
This change would help ensure object types are correctly placed from the start and remove the need for manual ontology reassignment.