Overview I would like to propose an enhancement for Ontology Manager (OMA): introducing the ability to explicitly order Object Properties. The goal is to establish a deterministic, globally applied column and property order across all downstream Ontology applications in both developer and user modes (e.g., Object Explorer, Quiver/Insight, Workshop, and various property selectors). (See also my previous request in 2024: https://community.palantir.com/t/set-default-columns-order-in-ontology-editor/1974)
Current Behavior Currently, there is a lack of synchronization regarding how properties are ordered across the platform. The column order in the backing dataset, the properties displayed within OMA, the default column order in Insight tables, and the layout in property selectors often appear in completely different sequences. (See the attached picture for an example of this misalignment).
Proposed Solution Allow ontology builders to define and lock a primary, default sequence for properties directly within OMA. This configuration should automatically propagate to:
-
Insight / Quiver default table views
-
Workshop widgets and property selectors
-
Any other downstream application consuming the Object Type
Key Benefits & Business Value
-
Developer Efficiency: Saves significant time by ensuring a consistent property order across all applications out-of-the-box, eliminating the need to manually reorder columns in individual widgets or views.
-
Improved User Adoption: End-users utilizing tools like Insight will immediately benefit from a well-configured Object. Developers can pre-align properties to fit specific business workflows—for instance, ensuring that logically related properties (e.g., ‘Start Date’ and ‘End Date’, or ‘Currency’ and ‘Amount’) are naturally positioned side-by-side on the field.
