Skip to main content
Committed ⭐️⭐️⭐️
Anwar Ali Mohamed
Committed ⭐️⭐️⭐️
October 21, 2026
Question

Configuration Control for Object Sequence in CDF Search and Details View

Hi Cognite Community,

We have a requirement to provide configuration control over how data model objects are organized and presented in CDF Search and the Details view.

As our industrial knowledge graph grows, an asset or equipment can be connected to many different object types, such as:

Functional Location → Equipment → Time Series → Notifications → Work Orders → Maintenance Plans → Documents → Engineering Studies → MOC

CDF already allows users to search and navigate connected resources. Data explorer - Cognite Docs However, for a large enterprise data model, the sequence in which these related objects are presented becomes important for usability and business context.

We would like the ability for an administrator/data model owner to configure:

  1. Search pane object ordering
    Define which object types appear first and in what sequence.

  2. Details view tab ordering
    Configure the sequence of related-object tabs when a user opens an Asset, Equipment, Functional Location, or another object.

  3. Show/hide configuration
    Control which related object types should be visible in Search and Details views.

  4. Context-specific sequencing
    Allow the sequence to differ depending on the selected object type. For example, an Equipment view may prioritize Time Series, Notifications and Work Orders, while an Engineering Document may prioritize Assets, Equipment and related Documents.

  1. Model-driven configuration
    Ideally, this presentation configuration should be managed centrally as part of the CDF data model or application configuration rather than requiring custom UI development.

CDF Views already provide a logical abstraction over containers and allow applications to consume a curated representation of the knowledge graph. Views - Cognite Docs We would like to understand whether a similar configurable mechanism exists, or is planned, for controlling how those objects and relationships are presented to users in CDF Search and Details views.

This becomes particularly important as the knowledge graph expands to 60+ industrial datasets/object types. Without configurable sequencing, technically correct relationships may still result in a difficult user experience because the most relevant objects are not presented in a logical business sequence.

Is this level of Search and Details-view configuration currently supported in CDF? If not, is it on the product roadmap?

      1 reply

      Everton Colling
      Expert ⭐️⭐️⭐️⭐️
      Everton Colling
      Expert ⭐️⭐️⭐️⭐️
      October 23, 2026

      Hi ​@Anwar Ali Mohamed!

      Thanks for the detailed write-up. Your examples make the problem very clear.

      Here is what CDF Search supports today, mapped to your five points.

      1. Search pane object ordering is not configurable today. The category list follows the structure of your data models, with core types listed first. Admins cannot change the order in the UI.
      2. Details view ordering is configurable today. We are reworking the preview panel so related data shows as collapsible sections with counts. Letting admins set a default order for those sections is part of the direction for that work, but we don’t have a firm release date yet.
      3. Show/hide is partly supported.
        • Admins can hide and reorder properties, columns and filters per category under Admin > Project settings > Categories. See Manage search categories.
        • To control which object types appear in the category list, you can create a location that points to a curated data model with only the views you want users to start from. Related objects defined on those views still show up when users open an item. See Location filters.
        • Hiding a view from the category list while keeping it visible as related data is not supported yet.
      4. Context-specific sequencing. Column, filter and property settings are already per category, so an Equipment view and a Document view can show different properties. Ordering related object types differently per view is not supported.
      5. Model-driven configuration. The category settings are stored centrally per project, and you can manage them as code with the Cognite Toolkit SearchConfig resource. See the Toolkit YAML reference. The actual views themselves do not store any application or client specific metadata that can be used to configure how it should be presented to users.

      That being said, your request fits well where we want to take Search as knowledge graphs grow to dozens of object types.

      ​@Mithila Jayalath, could you convert this post into a Product Idea? That lets other customers vote and add their use cases, which helps us prioritise.

      In the meantime, while all these features are not yet in our short term roadmap, ​@Anwar Ali Mohamed it would help us a lot if you could share a bit more details around:

      • Which object types you want first in the category list, and which you would hide.
      • Which user roles use Search, and how their needs differ.
      • One or two examples of the related-object order you want for Equipment and for an Engineering Document.
      • Roughly how many views your data model has today.
      Terms & ConditionsAccessibility statement