Tell us what features you’d like to see and support other ideas by upvoting them! Share your ideas in a user story format like: As a ˂role˃, I want to ˂function˃, so that ˂benefit˃. This will help us better understand your requirements and increase the chance of others voting for your request.
Hello, Workflow cancel operation should cancel underlying processes (transformation, function..etc). Today when a workflow run is canceled underlying processes keeps running and must be stoped by the user separatly. What do you think? Thanks
We’ve encountered a limitation while using the monitoring function in Cognite Charts. Currently, the minimum duration we can set is 59 minutes. However, our machine sends rejection data every 60 minutes, which means no alerts are triggered if the duration is set below that value. As discussed with Ben and Dilini, I understand that for critical parameters—where data is received every few seconds—the current setup works well, allowing quick alerts within 5 or 10 minutes. But in our case, the scenario is different, and we need the flexibility to set a longer minimum duration to match our data frequency. Would it be possible to increase the minimum duration setting? This would allow key users to adjust the timing based on their specific use cases.
On Canvas is the select not supposed to work on a mobile device?For example selecting the equipment card on the desktop lets you open up the equipment info in the side panel, which can have the 3D and files, etc.On the mobile, you aren't able to select the card at all, the only selection that works is on the contextualized assets and file links.It would help to have Canvas mobile friendly so we get more usage out of it in the field. This is from NovaChem.
It should be possible to create SQL variables/inputs on tranformations for easily modifying values on the queries, like table names, tag arrays, etc.
Required the functions/features to be able to append prefix to the name of the ingested data instead of only the prefix for externalId.We had 50 or more machines with the same OPCUA data structure, if we ingest the data into Cognite, the timeseries name will be the same though we can append prefix to the externalId. It will be great that the OPCUA extractor able to append the prefix to the name as well so it is easier to identify the data or events.
Can not open 3D preview into fullscreen from asset overview. There is no option to open to full screen, or to search, like what is available on the other resource previews. You can select the 3D resource tab directly at the top, but that isn’t consistent with how users are expanding other data sources.
Programatically able to create charts, calculations (currently can be done by creating a Cognite Function that does the calculation and create a new time series), Monitoring jobs, and Alerts.This could be done by transformation, Python SDK, or Rest API.
Our services occasionally receive 429 Too Many Requests errors when we reach concurrency limits. A specific example we encounter is:Project exceeded maximum number='8' of concurrent instance_read requests. Please try again later.Currently, to handle these situations, we rely on a client-side exponential backoff strategy. While functional, this method requires us to guess the appropriate delay, which can be inefficient. It can lead to our services either waiting too long or, more critically, retrying too quickly, thereby placing unnecessary load back onto the API when it's already at capacity.To address this, we kindly request the inclusion of the standard Retry-After HTTP header in all 429 responses.We are confident that this small addition would be a significant improvement. We would appreciate it if you could consider this feature for your development roadmap.Thank you for your time!
When you add a view from a data model to Canvas, it only show properties that has a single simple type. Eg, lists are not shown. It would be useful to also show the content in these lists, like Search shows all the items in the tag list for the CogniteAsset
One of our use cases that uses Canvas results in an overpopulation of documents as an initial draft, letting users review and determine which are to be kept. Having the ability to select the documents that are relevant and have a button to delete all the unselected documents, would save time vs. having to select the unwanted documents.
Hello, It would be neat if conditional formatting could be applied to shapes on a canvas. For example, when using a rectangle shape as a visual container around various charts on a canvas - I’d like to be able to dynamically change the background color of the rectangle (when a calculated value drops below a threshold). For example, set the background shape color to red when our calculated OEE value drops below an acceptable limit - set the background shape color back to green when we are back into acceptable limits. Thanks!
I would like to be able to create Cognite functions (and transformations) schedules in a local timezone. Right now, I can only specify the time for triggering a function in UTC. There are cases when daylight savings time changes the working hours and thus affects the set-up. It would be useful to have the ability to run the function in a local timezone.
Hello!It would be most helpful if it was possible to use keyvault secrets directly in defining the connection string of a db-extractor. An example of this belowdatabases: - type: odbc name: mssql-sap connection-string: > DSN=value; UID=!keyvault SOME-KEYVAULT-ID; PWD=!keyvault SOME-KEYVAULT-SECRETThis would allow us to use client/secret directly from keyvault and enable auto-rotation. Something that is more difficult with having the entire connection string stored in the keyvault
Currently CDF has support for synthetic timeseries, but those are specified as a parameter to the API call, which means that every user has to specify it, and it is a different API call then the ordinary timeseries.A very powerful feature would be to define a synthetic timeseries the same way as an ordinary timeseries, but it is not a persisted timeseries but instead an on-the-fly calculated timeseries. Pros:It doesn’t fill up cdf with a lot of unnecessary persisted timeseries We avoid having to depend on a calculation function that will have lag, being vulnerable to going down, secret expired,+++ Any UI or other functionality that consumes timeseries will automatically work It will be a “company” approved calculation We can add proper documentation, metadata, link it to the right assets (contextualisation),+++Cons:Added computational cost Need to agree on how to treat the “endpoints” in the timerange, how to do the data point alignment, how to do fill etc If at some point the calculation need a different timeseries, or the calculation changes, the synthetic timeseries will not be valid for the historical data (can be handled with a range validity identifier) The intention of this is to define relatively simple calculations. More complex calculations will be handled outside this framework.Example could be: I need a timeseries for whether a well is flowing or not. It is a combination of the position of 3-4 chokes. Not all users will know which chokes, so by creating this predefined synthetic timeseries we have a “approved” way of doing this calculation. Another relevant example is routing, which can be a combination of many different routing valves, requiring extensive investigation of P&IDs to figure out how to calculate.
hi cognite product team, i want interactive diagram to make it more easily change the posision of annotations by dragging or some easier way. i’m in charge of contexualizing updated files and Japanese team has made “annotation-copy” streamlit apps and has improved much time and effort when updating P&IDs, but still struggle deleting and repointing annotations when P&ID has slightly changed such as one pipe has removed. Annotations stand still and can’t move.i really appriciated if one of you think of it.
If I select a property to filter on, it is not possible to deselect it before I select a new one. If the list of properties is short, this is not a big problem. But if the list is long so I search up the property, I need to search for the new property, select it, search for the old and then deselect it. Would be nice to be allowed to deselect before I select a new
At present, we are reading data from CDF Data Models for the creation of PowerBI Dashboards. However, some use cases may not require a Data Model and could simply need a single CDF Staging table. Since CDF Staging tables lack defined indexes, this could lead to performance issues. Could you assist us in creating indexes on the CDF Staging tables, or let us know if there is an alternative approach?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK