Recently active topics

Today it is possible to specify the unit of a property of a View, enabling unit conversion on consumption (via the API). However, the CDF UI is currently not showing this unit. It means that we either have to create a dedicated “property_UOM”, or we have to add the unit into the @name in the View description. It would be preferable if the UI could show the unit, and also support the unit conversion. 

Today an Atlas AI agent (and Flow app) uses my personal access rights when accessing CDF. However, we see the need for being able to further restrict this. One example is: I have write access, but I do not want my Agent to have the same write access. This issue is currently not solvable by using a separate service principal for the Agent, since different users will have different read access, so I cannot have one Agent with a fixed set of access rights. What would work is to be able to grant the agent certain (maximum) access rights, and then the final access rights are the minimum of the agents and mine access rights.This becomes increasingly important when the capabilities of the (reasoning) agents are growing. We need to be able to provide additional (and strict) guardrails

We need the ability to download all items to a csv in search.  In the downloaded CSV there should be a column for a hyperlink back to the item, as if you clicked the open button in search. Additionally, if the items is a file create a download hyperlink.  

The Smart KPI Tracking System is a data-driven performance management platform designed to enable real-time monitoring, analysis, and predictive insights across critical business and operational KPIs. The project aims to move organizations from traditional static reporting to a proactive, intelligent, and automated decision-support system.This solution integrates data from multiple enterprise systems (e.g., SAP PM, asset management tools, scheduling platforms, and financial systems) to provide a unified and dynamic view of performance across projects, maintenance operations, and asset reliability.

As described in the referenced link（Cognite Hub）, we create a Canvas once a month to monitor long-term trends of key operational parameters.Since this activity is performed monthly, we are facing challenges in how to properly store and manage these Canvases over time.Currently, Canvases can be organized by site. However, if further granularity were available—such as hierarchical folder structures—it would significantly improve:Management of the latest Canvas Searchability of past Canvases Overall organization and maintainabilityAt present, we are supplementing this limitation by using a custom application built with Streamlit, as shown in the attached example. This allows us to further classify Canvases beyond site level, down to individual units. Ideally, we would like to have this functionality natively available in Canvas.Although this request is not highly urgent, we would appreciate your awareness and consideration for future improvements.

We create a Canvas like the attached example once a month to monitor long-term trends of key operational parameters.Previously, this work was done using Excel, but we have recently migrated to Charts and Canvas.As we move toward full-scale operational use, we would appreciate your support in resolving the following two challenges.These improvements are critical for reducing operational workload and enabling sustainable use of Canvas for monthly monitoring.Request ①We previously requested a permission transfer feature for Charts. However, it is currently difficult to locate individual Charts from within Canvas.Cognite HubTherefore, we would like to request the following enhancement:Ability to select Charts directly within Canvas and transfer their ownership/permissions in bulkWithout this capability, when the responsible person changes, users must first locate all relevant Charts individually and then manually duplicate them one by one. This process is time-consuming and creates a signi

I would like to submit a product idea regarding Charts calculations.Currently, calculations in Charts are performed only within the time range that is visible on the screen. We would like to request an enhancement that allows users to define a specific calculation period (i.e., start and end points) directly within the calculation formula.For example, when using the “sample average” operator, the result is calculated only based on the data currently displayed. As a result, the calculated value changes when the user scrolls or shifts the visible time range.We would like to be able to calculate metrics such as average values over a fixed, explicitly defined time range, including data outside of the current view. This would ensure that the result remains consistent and is not affected by scrolling or changes in the displayed window.We believe this functionality would significantly improve usability and enable more stable and meaningful analysis.Thank you for your consideration.

As part of driving internal platform adoption, we are requesting the ability to add custom "Help and resources" links through the Admin --> Project Settings options. This would be a new admin option to create new links to both internal/external URLs where we would like to route our users.For instance, we have an internal ticket/incident form, a custom Cognite portal, etc. where we would like to provide users the ability to find/link to from the Cognite platform.

Currently when plotting Work orders and Permit to work on Charts is difficult to see the difference. The colors are too close. It would be great to have different colors there to choose from or at least make more contrast on the default ones.

Add option for setting dark mode in the InField application. Both for desktop and handheld units.

In our company, area codes (Which signifies which area an asset/functional location is placed in) is a central property that users want to see immediately when opening tag detail view. Area codes are available in the properties section but users want to have this visible in the header, to not have to scroll down. This is more helpful on the handheld unit as less information is visible upon opening the screen and the user needs to scroll further down to see the relevant information. Example of where to add location code is shown below. To make it more generetic, users could be able to add relevant info in the header themselves as maybe other companies/user groups have different interest in what they want to show in the header.

When creating calculations in CHARTS it would be VERY useful to have logic functions (AND, OR, NOT, XOR) which allow multiple (>6 for AND and OR) boolean inputs (TRUE/FALSE) and a single output.This would be really useful for tracking events which may be dependent on multiple conditions being active (or not active). 

Problem StatementThe Cognite DB Extractor currently requires space to be a static, query-level configuration parameter, forcing users to create multiple identical extraction queries when distributing data across spaces based on hierarchical entity relationships.When working with hierarchical data structures, each distinct parent entity requires a separate extraction query, even if the source data and transformations are identical.Asset hierarchy:L1: Assets  L2: Area L3: Field (defines CDF space) L4: Installation L5: WellCurrently, if there are 10 distinct fields across multiple assets, the DB Extractor requires 10 separate extraction queries to distribute timeseries data across 10 spaces - one query per field, even though they all read from the same source table with identical transformations. With multiple assets, areas, and fields, this results in hundreds of extraction queries for a single source table. This creates:Configuration Bloat: Hundreds of nearly identical YAML configuratio

In Canvas, it is possible to configure rules for objects, but as far as I understand, the current setup allows only one trigger per rule (1 rule = 1 trigger).However, in practical use cases, there are often situations where we would like to define a rule using multiple trigger conditions (AND conditions). For example, when producing multiple product types on the same production line, the normal operating ranges for parameters such as temperature and flow rate may vary depending on the product.In such cases, we would like to configure rules like the following:When producing product A, it is considered abnormal if temperature or flow rate exceeds threshold α.When producing product B, it is considered abnormal if temperature or flow rate exceeds threshold β.To support these kinds of scenarios, it would be very helpful if we could configure multiple triggers within a single rule.Alternatively, if there is an existing way to achieve this functionality using current features, I would greatly

Would it be possible to provide a way to visualize trending content that is frequently viewed and utilized among those created using Charts, Canvas, and Streamlit?At present, even if someone creates an excellent Canvas or similar content, it does not easily spread to other users. However, if there were something like a trending ranking, high-quality content could naturally gain visibility and adoption. It could also serve as a helpful source of ideas for practical use cases.

Observed behaviorWhen a CDF Transformation produces rows with duplicate externalId values , the behavior depends on how CDF partitions the data across workers:Duplicates within the same API request (same batch) → the API raises an error → the transformation fails visibly ✅ Duplicates split across multiple API requests (different CDF partitions/workers) → each request succeeds individually → the transformation completes with status "success", but which version of the node was actually written to the knowledge graph is unknown and non-deterministic ❌ProblemThe second case is the dangerous one:Silent and invisible — the run reports success, no alert is triggered, no engineer investigates. The data in the knowledge graph may be incomplete or wrong with no trace. Non-deterministic — which duplicate "wins" depends entirely on which CDF worker flushes first. Two identical runs on the same input can produce different results. No user control — there is no way to express intent: "fail if duplic