Community Discussions

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