Skip to main content

Product Ideas Pipeline

1170 Ideas

B
Committed
BeauSlaughterCommitted

Need description in time series data tile in Industrial CanvasNew

When adding time series data to industrial canvas, providing the name of the tag and the description field in the time series tile window would clarify what tag is being shown.   Submitted at the request of the Cognite project team. 

1
Andreea Oprea
Forum|Forum|4 months ago
B
Committed
BeauSlaughterCommitted

Need description field added to time series preview in Industrial CanvasPlanned for development

When adding time series data to industrial canvas, providing the name of the tag and the description field in the time series preview window would make selecting the correct reading more effective. Currently, there is often not enough info in the time series tag itself to know which data to select.  !--scriptorstartfragment-->  Submitted at the request of the Cognite project team. !--scriptorendfragment-->

2
Andreea Oprea
Forum|Forum|4 months ago
M
Active
MoeActive

3 Features requests on CanvasPlanned for development

Please confirm when we will know on timing to have each of the three features below available to our end users. This features are directly asked by Planners and are critical/important to get them using the Canvas for work package creation if the goal is them using the Canvas on a daily basis. These are seen as basic requirements to them: Feature Requests:1.      Additional Shapes on Canvas (Critical)o    Add Cloud Callout, Hexagon, and Triangle shapes to the canvas shapes menu2.      Markups (Critical)o    Enable connectors between annotations/files that lock to the objects and move with them (e.g., connecting a valve symbol to a photo and maintaining the link when either object is moved).3.      Improved Page Navigation for Large Job Packages (Important)Allow users to flip through pages one by one (e.g., with left/right swipe or arrow click), instead of relying on zooming in and out to find specific content. 

1
Andreea Oprea
Forum|Forum|4 months ago
Shun Takase
MVP
Shun TakaseMVP

I want to embed items in the table of Canvas.Planned for development

With the recent update, it is now possible to add tables to Canvas. Currently, I believe you can only input text into the tables,but is it possible to embed asset information, timelines, and files into the tables? If this becomes possible, it would allow for a more organized dashboard in Canvas, greatly expanding its usability.

4
Andreea Oprea
Forum|Forum|4 months ago
Mithila Jayalath
Seasoned Practitioner
Mithila JayalathSeasoned Practitioner

Inconsistent document search in CDF vs MaintainGathering Interest

A customer from Oxy reported this.Issue describedIt seems like when searching for a documentation on Maintain it only shows up documents when search through a unique system generated ID rather than the documentation name or drawing no. etcSo basically the user want the search to be searchable through document metadata which they find more meaningful and easier. This behavior is reproducible and seems to align with how search currently functions on Maintain. However, the customer would like the search experience on Maintain to match that of CDF.

1
Mithila Jayalath
Forum|Forum|4 months ago
Mithila Jayalath
Seasoned Practitioner
Mithila JayalathSeasoned Practitioner

Allow the 'Search' with special characters in Industrial CanvasPlanned for development

A customer from Oxy has highlighted the importance of search functionality when dealing with special characters in Industrial Canvas.Please see the use case below for further clarification:An asset named '4011-1 1/2'-G4J-014' exists in CDF, but when searching with the term '1 1/2'-G4J-014', the asset does not appear in the results. However, using 'G4J-014' as the search term correctly displays the asset as the top result.

1
Mithila Jayalath
Forum|Forum|4 months ago
Mithila Jayalath
Seasoned Practitioner
Mithila JayalathSeasoned Practitioner

Improve UI design - File preview from 3D searchPlanned for development

A customer from Oxy has reported that the UI in 'Browse 3D' should either open the selected file in a new tab or, upon clicking 'search results' in the top-left corner, navigate directly to the selected 3D preview without losing it, eliminating the need to restart the search.

1
Mithila Jayalath
Forum|Forum|4 months ago
akeelishak
Practitioner
akeelishakPractitioner

Ability to Incorporate Work Orders/Activities from Maintain to CDF Canvas (Assets)New

The customer (BBraun - @gary.goh@bbraun.com) has requested the enablement of the feature that allows Work Orders/Activities from Cognite Maintain to be added to CDF Industrial Canvas. Simply, for any/every annotated Asset on the CDF Canvas the customer would like to bring in the associated Work Order/Activity from Maintain. 

0
akeelishak
Forum|Forum|4 months ago
crgomez13
Committed
crgomez13Accenture

Cognite InField 2.0: Observations/Notes in Asset OverviewGathering Interest

On behalf of Celanese InField super users: The users have expressed interests in being able to see both observations and any comments/notes that have been linked to an asset on the asset overview page. This would make the data easily accessible rather than needing to open specific checklists.  @Kristoffer Knudsen 

6
M
Forum|Forum|4 months ago
M
Committed
Maryam Al-AnssariCommitted

Controlling P&ID Relation Line color in Canvas CDFPlanned for development

A t the moment, CDF Canvas lines for relations ( from P&ID to other document/ assets/ charts/ time series)are only displayed in purple.This is an issue when working on big P&ID, and doing RCAs, all lines are purple & become mixed & hard to track - adding complexity to something that is meant to simplify work.Clients are asking for simplification tools in displaying relation lines , such as:-The ability to change each line’s color/ thickness/ type, or it would be auto-changes for every new relationship added from P&ID-Legend tab where one could select what each color represents from relationship lines & is possible to toggle, if one wishes to hide only some relationship lines related to some assets/ time series.I am not sure if similar idea is published on the hub. but if not, kindly consider it .

1
M
Forum|Forum|4 months ago
K
Seasoned
Kristian NymoenSeasoned

Expand support for other time series aggregates in GrafanaParked

Hi. I’d like to see more aggregation functions on the grafana data source. Currently only average, interpolation and step_interpolation are allowed. Any chance to implement support for Sum, Count, etc.? Error: count is not one of the valid aggregates: AVERAGE, INTERPOLATION, STEP_INTERPOLATIONhttps://docs.cognite.com/cdf/dashboards/guides/grafana/timeseries

4
T
Forum|Forum|5 months ago
T
Committed
tddahnkeCommitted

File Previewer Pane Icon SpacingPlanned for development

Problem Statement: When the browser zoom is increased, the file preview pane icons (Last Page & Magnifier) overlap each other.  When the icons are overlapped, the magnifier icon overrides the last page icon not allowing the button to be used.  The work around is changing the browser zoom and or utilizing larger monitor sizes, however in the industrial setting remote/mobile applications these work arounds may not be available and can still cause user issues.Solution: Re-locate the icons so that the location doesn’t overlap or anchor the icons. 

1
Sofie Svartdal Berge
Forum|Forum|5 months ago
O
Committed
Oussama ALLALICommitted

Persistent Identification for Synthetic Time Series in CogniteGathering Interest

Problem Statement:Synthetic Time Series in CDF are dynamically calculated based on expressions, but lack persistent identifiers. This limits usability when users need:Persistent IDs for discovery and access. Simplified queries via API, SDK. Centralized definition of expressions as part of the data model, avoiding the need for each backend to redefine them.Suggested Approach:Introduce a Synthetic Time Series Definition object that:Allows defining synthetic series with a persistent external_id. Stores metadata like expressions, descriptions, and units. Enables dynamic evaluation without requiring data storage. Supports defining expressions as part of a model, enabling reuse across different systems without requiring redundant definitions in backends.Benefits:Usability: Persistent identifiers for easier access and queries. Consistency: Eliminates repetitive expression definitions. Scalability: Centralized expression definitions simplify updates and maintenance.

4
T
Forum|Forum|5 months ago
R
Seasoned
Richard BoothSeasoned

Synthetic timeseries in CDMClosed

This is closely related to existing suggestion (Cognite Hub) - details specific to our application were already discussed with ​@Jason Dressel In our data model, we already make use of synthetic expressions and have created a wrapper view for timeseries that can either refer to a regular timeseries instance or a synthetic expression.In adopting CDM, we cannot really represent the same thing using CogniteTimeseries, even if we extend the model, as this would lead to us creating an empty time series for every synthetic timeseries that we want to create. Suggestion is to extend the existing CogniteTimeseries in CDM to have some support for storing and accessing synthetic timeseries expressions.

1
T
Forum|Forum|5 months ago
T
Committed
tddahnkeCommitted

Monitoring/Alerting Functionality for Calculations in ChartsGathering Interest

Please consider adding monitoring / alerting functionality to calculations inside of charts.

9
E
Forum|Forum|5 months ago
Mithila Jayalath
Seasoned Practitioner
Mithila JayalathSeasoned Practitioner

Alternative way to work sort and first together of nested items when using edgesParked

This issue was reported by a user at SLB where they encountered an unexpected behavior when sorting the runHistory field in GraphQL. It appears that the sorting might not be applied as expected when using first: 1 in the query.type Workflow { runHistory: [WorkflowRun]}type WorkflowRun { endTime: Timestamp}query MyQuery { listWorkflow { items { runHistory(sort: {endTime: DESC}, first: 1) { items { endTime } } } }}By running the above query, he expects the first WorkflowRun in runHistory to be the most recent. If the user changes first: 1 in the query to first: 10 then he's able to see WorkflowRun in descending order.

2
Mithila Jayalath
Forum|Forum|5 months ago
Markus Pettersen
MVP
Markus PettersenMVP

Hosted extractors, missing and confusion UI elementsNew

We would very much like for a new column to be added to this view, “extractor type”. Currently there are no indicators as to what type of extractor it is. For the developers working on the extractor this is not an issue because they know, but for others that just want an overview this is somewhat more difficult as we would need to click in on every single one of them to find out. Sometimes we would like to just see all REST extractors, or all MQTT extractors and so on. Another point is the throughput: “0 datapoints p/hr”What does the “p” stand for, is it “0 datapoints per hour” because if so the p is redundant as the standard use of  “/” already signifies it. Also the SI unit for hour is h not hr. E.g.: km/h (km/t norwegian), m/s etc. 

1
Mithila Jayalath
Forum|Forum|5 months ago
T
Seasoned
Tanmay DeshpandeSeasoned

Is there any way to ODBC DNS for Snowflake Extractor instead of putting username and password in YAML?Parked

Hello, I have trying to use the ODBC extractor to pull data from Snowflake, I could do that by following instructions here https://docs.cognite.com/cdf/integration/guides/extraction/configuration/db/#-snowflake However, this requires me to put passwords in YAML config. Is there anyway to use DSN from ODBC instead? I see that connection-string parameter is not supported when I choose type as snowflake. Thanks!

8
Aditya Kotiyal
Forum|Forum|5 months ago
ibrahim.alsyed
Seasoned
ibrahim.alsyedSeasoned

CDF File Extractor for SharepointPlanned for development

Problem Description: Cognite File Extractor for Sharepoint is not able to recursively retrieve documents from a Sharepoint site where site and sub-sites, e.g. Document Control System Alternatives explored: Provide Sharepoint URL as mentioned in documentation for site (Sharepoint Online | Cognite Documentation) Results: no errors, however, no documents are loaded Evaluation: recursion does not occur from site-level down to the document or folder level where Sharepoint stores documents Provide document library and folder / sub-folder Results: working, however, sustainability not ideal Evaluation: will require potentially >100 URLs to be configured and kept up-to-date in case of new document libraries or folders created or deleted Recommended enhancement Recursion from root node (Sharepoint site). E.g. if site URL is provided recursion should go through each sub-site (if present) to document libraries and sub-folders to retrieve documents This should be treated as high-priority. Item 2B above can be seen as a work-around but maintaining Sharepoint URLs in config up-to-date will require coordination/sync with source – likely through custom

3
T
Forum|Forum|5 months ago
T
Seasoned Practitioner
Thomas SjolshagenLead Product Manager

Cognite Data Fusion: Missing values in a Time Series is reflected in Synthetic Time SeriesImplemented

Problem: If one or more of the source-time series are missing data-points they will also be missing in the synthetic time series output.Would it be possible to add an option to supply a default “not available” value for missing data-points which could then be used by the API to calculate a partial result?Source:  

10
T
Forum|Forum|5 months ago
H
Active
henrikhestnesActive

DatapointsSubscription: Expired cursorParked

I understand that updates older than 7 days may be discarded from the endpoint, which is perfectly fine. However, I’m wondering if it’s possible to determine when a cursor is older than the given limit, since updates older than 7 days are discarded. Based on my understanding of your Subscription API, it would simply continue iterating over the oldest available updates on the endpoint, which could result in missing important updates that occurred between the time of my cursor and the current oldest update. For the Subscription API to be fully functional, I believe it's essential to either receive a notification or an exception when using an expired cursor, be able to determine the age of a cursor, or somehow be assured that iterating from a cursor won't lead to lost data. Knowing the age of the cursor would be preferable, as it would allow us to gauge how much margin we have, but it should also be possible to receive a notification if an expired cursor is being used. Is this currently possible, or are there any plans to implement such a feature?

12
T
Forum|Forum|5 months ago
K
Seasoned
Kristian NymoenSeasoned

Flag inactive / deprecated time series - and only display active ones by defaultParked

Once in a while we make changes to our telemetry setup in such a way that certain time series get deprecated. This happens when we change control systems, or make changes in our telemetry pipeline, or even discontinue operations at a location. We want to have the “deprecated” time series available in CDF, but it would be useful for us if these would not by default appear in search, or in the asset hierarchy, or through grafana and other solutions. It would be useful if there was a way to mark a time series as deprecated or as only containing historical data - and that in order to have the time series returned in search or list operations, the user would have to make an active choice to include those time series. My suggestion is an “isDeprecated” property on each time series. There are other solutions to the problem, but these all seem to make it more difficult for the user than simply not showing deprecated time series by default:Metadata field - isDeprecated (boolean) Move deprecated time series to a different data set Separate data models for “active” and “non-active” time series

4
T
Forum|Forum|5 months ago
J
Seasoned
Jesse JenkenSeasoned

Hosted Event Hub Extractor Triage / Routing to Different DatasetsClosed

Posted for inquiry here: Cognite Hub but I don’t believe the feature exists currently. We need a way of routing time_series and datapoint items from within a Hosted Extractor configuration to different, or possibly multiple datasets. Question copied from referenced posting here, for product feature descriptiveness: Within our implementation we have an existing Hosted Extractor reading data from an IoT Hub that contains multiple sites worth of data. Our Hosted Extractor Mapping Template filters for events that have a particular deviceId on it, representative of the location these events are coming from. In effort of ingesting another site-location datafeed, I wanted to extend the template with an ELSE IF condition that has the mapping rules for the other location, which are almost identical to the first except for the target datasets, which I’ve come to realize is set in the Sink section of the Extractor Configuration. The net result here is needing to create redundant Hosted Extractor configurations that change only a filter, rather than having a cascading ELSE IF ruleset that applies to the full stream. For example, this pseudo-template for our existing hosted extractor configuration for one site: if (context.messageAnnotations.`iothub-connection-device-id` == "SITE_A") { input.map(record_unpack => { "type": "raw_row", "table": "tb_iot_test", "database": "db_iot_testing", "key": concat("TS_CO_", record_unpack.NAME), "deviceId": context.messageAnnotations.`iothub-connection-device-id`, "TAG":record_unpack.NAME, "IP_INPUT_VALUE":record_unpack.IP_INPUT_VALUE, "IP_INPUT_TIME":record_unpack.IP_INPUT_TIME, "IP_INPUT_QUALITY":record_unpack.IP_INPUT_QUALITY }).filter(item => item.IP_INPUT_QUALITY == "Good").flatmap( item => [ { "type": "time_series", "name": item.TAG, "externalId": item.key, "metadata": { "IP21_DEVICE_ID": item.deviceId }, "isString": false, "isStep": false }, { "type": "datapoint", "externalId": item.key, "value": try_float(trim_whitespace(item.IP_INPUT_VALUE), null), "timestamp": to_unix_timestamp(item.IP_INPUT_TIME,"%Y-%m-%dT%H:%M:%S.%6fZ"), } ] ) } else { [] } Ideally I want to add an ELSE IF condition where the only change to the outcome is the iothub-connection-device-id equals SITE_B in this case. While the record_unpack step is able to route different locations to different staging tables, I was unable to find a means to specify an alternative target to route the time_series and datapoint items in the outside of creating a whole new configuration and having a different Sink setting for this extractor.  We have multiple sites all sharing one IoT Hub. IoT Hub has a limit to the number of consumers that can be connected, in this case larger than our number of sites. We handle routing in the Consumer logic of this stream however Cognite appears not to provide us with this mechanism in the templating language, instead specifying it in the sink.  This presents a configuration-limit issue for us with respect to our source data, and the constraints presented by the Cognite Hosted Extractor with specifying the target.  Am I missing something and is there a way to achieve what we’re looking for, or will this require a secondary hosted extractor configuration to be implemented? If we must go down the path of redundant hosted extractors with modified logic and a different Sink, we’re going to hit an Azure IoT limit prior to our full scale out, and would like to understand if this is a feature that can be provided, or if we should be planning otherwise.

1
T
Forum|Forum|5 months ago
S
Active
Shinichi MaedaActive

Support for Double-Byte Characters in Property NamesGathering Interest

Hello,We have confirmed that there is a restriction in the data model View (Container) definition that prevents the use of Japanese (double-byte) characters in property names.This limitation also applies to the Records/Streams API. Currently, our database column names and CSV file headers include Japanese characters, which means we are unable to use the existing names directly when registering these datasets as Records.As a result, we are now required to define a mapping between the Japanese column names and alphanumeric property names, and to establish, standardize, and manage a naming convention. However, this process is labor-intensive and may lead to confusion and operational burden in data utilization.Therefore, we would like to kindly ask if you could consider supporting the use of Japanese (double-byte) characters in property names within the data model View definitions and the Records API.

3
U
Forum|Forum|5 months ago
T
Committed
tddahnkeCommitted

Charts Calculation Reversal IssueGathering Interest

Resolve the subtraction function issue in charts.  Currently the smaller value must be on top of the subtraction function to get a positive value.

2
T
Forum|Forum|5 months ago

Filter by Topic

  • All Topics
  • 3D
  • Academy Trainings
  • API and SDKs
  • Atlas AI
  • Authentication and Access Management
  • Charts
  • Contextualization
  • Data Modeling
  • Data Quality
  • Data Workflows
  • Developer Tools
  • Drilling and Wells
  • Extractors
  • Functions
  • Industrial Canvas
  • InField
  • InRobot
  • Jupyter Notebooks
  • Maintain
  • Other
  • Product Releases
  • Product Roadmap
  • Public Beta
  • Search and Data Exploration
  • Streamlit
  • Toolkit
  • Pygen
  • Security Updates
  • Simulator Integration
  • Transformations and RAW
Terms & ConditionsCookie SettingsAccessibility statement