Product Ideas

ProblemSmart Factory is a Flows custom app that runs inside the CDF iframe with hideShell=true. In that mode users cannot open the Fusion account menu to sign out.HostAppAPI from connectToHostApp (@cognite/app-sdk) already exposes getAccessToken(), getProject(), getBaseUrl(), navigateExternal, and setHideShell (see Flows Auth API). It does not provide a way to end the Cognite Auth / Fusion session from the app:There is no logout() (or similar) on HostAppAPI. Cognite Auth RP-initiated logout (end_session_endpoint at https://auth.cognite.com/oauth2/sessions/logout) expects an id_token_hint. The host only exposes a CDF access token via getAccessToken(), not an ID token. Fusion’s own logout uses that end-session endpoint with id_token_hint and post_logout_redirect_uri. From the iframe we cannot obtain a valid id_token_hint.We also cannot use setHideShell(false) just to expose Cognite’s logout UI. Proposed solutionExtend HostAppAPI with one of:logout(options?) – the host clears the Cognite

SummaryLet Atlas create a Chart calculation from a natural-language request and plot the result as a time series chart.Today a user can build that calculation by hand in the Charts node editor (sources, constants, functions, and an output node), or ask Atlas to analyze stored time series. Atlas can embed a bar chart, KPI, table, or an existing Charts time series in a reply. It cannot turn a formula, for example a pressure difference, a unit conversion, or a scaled flow, into a calculation and show that calculated series on a line chart unless the result already exists as a time series in CDF. ProblemEngineers and operators compare derived signals as often as raw tags: pressure drop, API gravity, unit conversion, ratio of two flows, a moving average. Those series are usually not stored in CDF.The path today is manual: Find the source time series. Open Flows > Charts, create a chart, and add the series. Open Add data > Create calculation and wire sources, constants, and functio

The ability to define a CogniteUnit on a column in a container is very powerful. However, there are many situations where we are not able to define one common unit for an entire column.One example is LCI/Equipment data. Properties like length, volume, weight will have different units for a massive compressor vs a tiny bolt. We want to avoid doing unit conversion on ingestion since it introduces added complexity and risk (how to handle that a unit is not specified in the source), and it will also require the end user to do the unit conversion to get the number on the unit from the source system. One possible approach could be to have a column with the CogniteUnit instanceid, and then instead of defining the fixed CogniteUnit for a column we define the column with the unit.  

One of the more important properties for industrial data is the Engineering units of a value (unit of measure).Today we can add a CogniteUnit, both to a timeseries and to a column in a data model container, which will enable unit conversion on consumption.When we ingest the data from our source systems, we need to identify the unit as it is described in the source system, and then match it to the correct CogniteUnit. Many of our source systems do unfortunately not follow a standard for engineering units (leading to the need for the looooong alias list in the unit catalogue).But some of our systems specify the unit via a standard. For AkerBP it is mainly CFIHOS and OPC-UA (which really is UN/CEFACT unit codes)It would be very helpful to both being able to identify a unit via these standards when the unit is populated, but also when it is consumed.Eg: Temperature in Celsius isCFIHOS-60001435 CE/CEFACT/OPCUA unitID=4408652I can add the CFIHOS code to the alias list (we are doing this now)

Several Data model views contain large volumes of historical data, which can impact performance, scalability, and overall user experience. A potential improvement would be to implement a historical data archiving strategy by separating older records from active datasets.For example, records beyond a defined retention period could be moved to dedicated archive views, while primary views retain only the most recent and frequently accessed data. Another option would be to maintain a separate historical reporting layer specifically designed for long-term analysis and archival reporting.This approach would help improve query performance, reduce dataset sizes, and enhance usability for analytics and reporting tools. Users would benefit from faster data retrieval, shorter dashboard load times, and a more responsive self-service analytics experience, while also reducing processing overhead on the platform.

Hi, Is it possible to perhaps add a "warning" status to Extraction Pipelines? Sometimes it is nice to not just flag something as a failure but still something that should be flagged/raised.

I feel that when zooming in with the mouse wheel, the increment at which it zooms is too small.  For instance, when I zoom into a canvas with 5 drawings it takes 15 mouse wheel up’s to get to the zoom level that I am able to read any one of those drawings. Then when zooming back out it takes 15 to see the whole canvas again.

RequestProvide the ability to change bounding box colors based on the status or metadata of the associated document, inspection data, or record.The goal is to make important status information visible directly within the working view, allowing users to recognize items that may require attention without opening each item individually.Problem / opportunityWhen reviewing documents or records together, users need a clear way to distinguish their status. For example, they may need to know whether a document is managed, whether it represents the latest revision, or whether an associated inspection is overdue.Status-based bounding box indicators would bring that context into the visual review, rather than requiring a separate status check for every item.Use Case Examples1. Managed versus unmanaged documentsUse different bounding box colors to distinguish documents identified as managed from those identified as unmanaged.Example: A user reviewing several documents could immediately identify wh

Its a need to have the schedules tab available for all users using InField. As a technician it is beneficial to see all upcoming check lists in a schedule view just as the lead technician is able to today. This gives a much better overview of all lists coming up in the next week.The only downside is that the technicians don’t need to set a check list to “Ready” status. Its proposed to give technicians a display version of schedules, without the possibility of setting lists to “Ready”.  

Today there is no way to customize the way instances are ordered within hierarchy views. It would be beneficial with a method that could allow instances to be ordered to reflect the physical build of the monitoring system.  Granted the information order can be delivered from the source into CDF, we can re-use the information to create a hierarchy view that more closely represents reality and what users may already be familiar with. However, in our case, we may have a sub-hierarchy (e.g. S1 data for Yggdrasil - Yggdrasil being the root of the hierarchy) that has one way of defining the order, while a different sub-hierarchy (e.g. SAS data for Yggdrasil) may not have exposed this information. 

BackgroundWe want to build a new dashboard for our operations department in CDF Adaptive Experience. Our plan is to show existing time series, custom apps, and dashboards together as widgets in one place.While setting this up, we found the gaps below. We'd like to request the following features.1. Direct integration with CanvasCurrent: We can't create a direct link to a Canvas, and we can't embed a Canvas in the dashboard. Request: Allow Canvas content to be displayed on new dashboards in Adaptive Experience.2. Bulk import of edited charts or charts placed on a CanvasCurrent: Charts created on a Canvas (multiple charts) can't be embedded directly in the dashboard. The only options are to pull out each time series one by one, or to add a launcher through Flows. The launcher only opens a separate screen, which adds an extra step for users. Request: Let us paste edited charts into the dashboard. Ideally, a whole Canvas could be imported at once, with its charts registered automatically.3.

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 → MOCCDF 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: Search pane object ordering Define which object types appear first and in what sequence. Details view tab ordering Configure the sequence of related-object tabs when a user opens an Asset, Equipment, Functional Location, or another object. Sho

SummaryIntroduce a first-class NumericSeries object in Cognite CDF to natively represent depth-indexed data (measured depth, true vertical depth) and elapsed-time-indexed measurements (wireline elapsed time, drilling offsets in hours). Depth is a fundamental axis in upstream oil & gas, on par with time measurements. A NumericSeries would unlock more natural storage, querying, visualization, and analytics for a large portion of subsurface and drilling data.Why numeric indexes matter in Upstream Oil & GasNumeric indexes are the most widely used independent variables across the upstream domain: Drilling: MWD/LWD logs, drilling parameters vs. depth, trajectories, broomsticks, hole conditions Geology: lithology descriptions, stratigraphic tops, formations, facies vs. depth Petrophysics: wireline logs, core measurements, interpreted curves Reservoir & Completions: perforations, zones, intervals, properties vs. depth Elapsed time s/min/hr in addition to depth: wireline, we

Today, a Simulator Routine in CDF requires a default value for each input variable.Currently, when running the Routine, I can either:Use the Routine default: 21 bar (see picture / comment below) Provide a custom value: 30.2 barWe need a third option:Use Model Value: when the user neither do not confirm the default nor provide a custom value, then do not send this variable as an input and let the simulation use the value already configured in the Simulator Model, in this example 20.28 bar (see picture / comment below)The key requirement is that not providing an input should be different from providing the Routine default.This would allow a Routine to override only the variables explicitly selected by the user while leaving all other values unchanged in the Simulator Model.Could Cognite please enable this? For our simulator use cases, this is a very important feature and should be prioritized.

Hi,In the Personal Learning Profile, there are many certifications, badges, and completed courses available. Is there any functionality for exporting this information, such as generating a PDF report or transcript that shows completed certifications, badges, and courses?Thanks!

In our use case, we modeled several related data categories, but they all appear as a flat list in Cognite Search, mixed with unrelated categories.From a usability perspective, it would be valuable to organize these related views under a custom parent category, with an expandable dropdown, similar to the existing grouping available for CogniteCore views.This would make navigation more intuitive and reduce category clutter, especially for Data Models containing multiple related entities.The request is to extend the existing category grouping functionality to custom Data Models, without requiring their views to inherit from CogniteCore views.

When we place multiple Charts side by side on Cognite Canvas, the X-axis and Y-axis labels become very small and hard to read (see the attached screenshot).The same problem occurs when we export a chart as a PNG file and paste it into Excel. The axis labels are too small to read clearly.We would like to request the following improvements:The ability to change the font size of the X-axis and Y-axis labels for Charts placed on Canvas The ability to change the axis label font size when viewing a chart on its own in Charts, with the change also applied to PNG exportsI apologize for the many requests, and thank you very much for your consideration.Best regards, 

Simple Dashboard to display all the projects running in the organization - Project DashboardDetails of the projects when expanded 

Hello,Currently when we search for the information “XXX” the system syncchronize all views records by looking for “XXX” in all the metadata of the views. So this a text link in the metadata.Our end suers would like to limit the number of clicks and synchronize all views including also all the contextualized data.Here below is an illustration of how it could improve the search experience when end users know there tags/assets 

Currently, Charts and Canvas save changes automatically. We would also like to request a manual save function, such as a "Save" button.BackgroundWe have seen work being lost in both Charts and Canvas: Charts: the calculation source disappears As described in the related idea, Undo/Back Button for Calculation Editing, users sometimes find that their calculation source has suddenly disappeared while they are building complex formulas. When this happens, they have to start over from the beginning. Canvas: entered text is not saved As we reported in this community post, text entered on a Canvas sometimes disappears when we check it later. The change is also missing from the Canvas history, so we cannot keep a record. This has happened on several Canvases for some time. Unfortunately, these issues still occur. In some cases, the work does not seem to have been auto-saved at all, so everything is lost. This is very discouraging for users who have spent a lot of time and effort on their wor

If you perform the following actions in InField while status filters (“Ready,” “In Progress,” and “Done”) are set, I believe the status filters will automatically switch.① If you change the “Done” checklist to “In Progress,” only the “In Progress” filter will remain② If you change the “In Progress” checklist to “Done,” only the “Ready” filter will remain③ When you start reviewing a checklist marked as “Ready,” only the “In Progress” filter remainsRegarding point ③, I believe this is by design since it’s a natural flow considering the user’s workflow; however, we’ve received feedback from our users that points ① and ② are somewhat cumbersome to use.① ⇒ In our company, when an approver reviews the checklists Doned by an inspector, they sometimes review them all at once using the following workflow; however, this creates extra effort when instructing a re-inspection.Workflow OverviewConduct inspection (Inspector)⇒ Once the inspection is Done, change the checklist status to “Doned” (Inspec

Requirement: Improve Evaluation Tool CLI Report DetailsThe Cognite Atlas AI Evaluation Tool CLI should include timing information for each individual evaluation question, including:- Start Time — datetime when the test started.- End Time — datetime when the test finished.- Duration (chatDuration) — total execution time, using a consistent unit such as seconds or milliseconds.This information should also be included in the exported evaluation report to support Agent performance and latency analysis, comparison across Agents, models, skills, and evaluation runs, and overall production-readiness assessment.

When you hover your mouse over a chart in Charts, the tag names of the time-series data being plotted and the corresponding values are displayed. While this is a very useful feature, the information is displayed directly on top of the time-series data, which can sometimes obscure the data itself.Although this can be avoided by moving the mouse pointer away from the chart, it does make the experience slightly less user-friendly.Therefore, would it be possible to display the tag names in a way that minimizes overlap with the time-series data? We would appreciate it if you could look into this.

Currently the workflows invoke function runs up to the allowed limit and if we try to run other workflows during the same execution they start getting 429 with the error message: {code: 429, message: "The number of running workflows for this project has reached the limit of 50"}We want a mechanism to limit the number of function invocations while setting up the workflow and only for function instances that it would churn up.  cc: ​@Neerajkumar Bhatewara 

Add functionality to visualize mathematical formulas rather than the raw LaTeX formatting which Atlas AI currently outputs. If you take a look at the screenshot I think it’s clear that is not a very friendly format to show to our end users Example of preferred output format: Example prompt for replication:Hvordan regner jeg ut volum til 100% fylte endekapsler til en horisontal sylindrisk separator. må anta en endebunnfaktor k, hva betyr denne?Example of how the formulas should be visualized (the visualization of LaTeX, not the raw format)Markus PettersenAker BP - Data Platform Architect