Suggest features, upvote favorites, and use the user story format: > As a [role], I want to [action], so that [benefit]. Help us build what you need - post your idea now!
What you should know submitting product ideas to our product team
Share your product ideas with the community and our product team
When using classic data model, there is a separate button in the right column allowing you to add events in the Charts For Data Modelling you have to do “+ Add data” → “Add time series” → select either Asset or the Activity category → select the Activity you want to include.For a new user, the “Add time series” might throw you off a little (reoccurring feedback from SMEs trying Data Modelling in Charts).It would be good to have names that allow a new user to find things more easily
All hosted extractors needs some kind of monitoring like extraction pipelines. This is supported for on-premise extractors and we don’t understand why this has been left out of the hosted extractors.We have requirements for monitoring all extractors and integrations we have in production, as I assume a lot of other companies does as well, but without monitoring hosted extractors are not an option at all. We simply can’t use them, it is unacceptable to skip monitoring.We would very much like to use them, but in their current state they’re a selling point for a powerpoint presentation with no real applicability. Markus PettersenAker BP - Techniacal Domain Architect for CDF
When I view files in the search file preview or directly in the Canvas, the maximum zoom level isn’t sufficient for detailed inspection. Even at full zoom, small details are hard to see clearly.Is there a way to increase the zoom limit? Maximum zoom within canvas (Red line indicates the zoom area in the native pdf viewer screenshot below) Zooming in with native PDF viewer
Can a simple label be added to Infield so that a user knows which environment they are in? We have 3 different environments and the only way to know which we are in for certain is to log out and log back in. We have had users create templates in our UAT environment before they realized it. Then they had to recreate them manually again in production.A simple label at the top would suffice. This would save us countless times of logging in and out and also make sure users know when they are not in the correct environment. @Andrew Montgomery
When printing from canvas, if you reduce the default size of a text or object, it prints to PDF extremely blurry and you can’t read it.
The File category view is very useful, allowing you to quickly filter on the right files. But some file categories are more important than others, especially the P&IDs. It would be good to be able to configure the order of the file categories in that list, allowing us to eg “pin” the P&ID category on the top
there's an unnecessary amount of filtering options under search. I guess its okay to show the options available, but for several tags there are multiple filters without any hits - why are these shown? The number of filters is already many, some of them with descriptions not too accurate (but I guess they are for some people...) This is mainly for trying to remove some noise from the filtering functions. An explanatory information document for the filter options would also be nice. many people who will be trying to filter will really struggle to know what to filter on.Can hide properties from filter if none of the values are populated.
When selecting an instance in Search, the Overview tab is very useful (seeing more than one data category without having to switch view). The challenge today is that the tiles have pre-defined columns, and they do not allow for filtering. It is of course possible to go into the “full screen mode” for each category, like Activities, but then you loose the possibility of seeing data from more categories in context.It would be very useful to be able to configure the properties we see in each tile and to filter on properties, like we can do in the “full screen mode”.
When selecting the property that will be used for the x-axis in the graph, the list is not searchable. For more complex Views the list of properties can be long (100+), which makes a non-searchable non-sorted list relatively hard to work with
The closest to that solution as for now would be adding a timeseries on the canvas, then you have an option to Open in charts and then choose a new one or existing one. This is too cumbersome.See picture below of suggested solution directly in canvas:
I am submitting this idea on behalf of LyondellBasell, and it consists on the ability to search for parts of a name, whether that is a filename, equipment name, asset, etc. One scenario is that an end user is interested in a particular subsystem (ie a flow loop), so the user would search for the number of that subsystem expecting all elements of that subsystem to be returned. For example, searching for “28806” would return:TI-28806 TI28806 TE-28806 PI28806 HY28806 HY-28806
The OPCUA extractor can only write time series instances to a single target space per deployment, even when the underlying OPCUA server contains data from different sources, governance domains or folders which should be handled individually. The only practical workaround is to run many OPCUA extractor instances against the same OPCUA server/hub, each with different tag filters and a different target space, which is hard to scale and operate. [Governance & spaces; Multi-space limitation]I would like the OPCUA extractor to support multiple target spaces from a single deployment, where the space is selected per time series based on configurable filters. Typical examples would be routing by tag name prefix or pattern (for example, ABB* to space site-abb, VAL* to space site-val), or by attributes / metadata / folder structure mapped to specific spaces. [Filter-based routing idea; Enterprise scaling concern]. This capability would avoid both the operational overhead of many parallel extractor instances.This is strongly related to the need of the same functionality for PI Cognite Hub
Recently a change was implemented to make the connection lines between documents on a Canvas to be orthagonal and to combine and flow between documents.There are some Canvases where I would like to be able to see a direct straight line connection between my references to quickly locate interconnectivity.My product idea: add a toggle to allow me to choose between orthagonal connectors or straight line direct connector.
Currently, the PI-AF Extractor works as a forward synchronization tool that reads the PI-AF structure and sends it to Cognite Data Fusion (CDF).The extractor correctly handles: Insertions: New elements created in PI-AF are detected and created in CDF. Modifications: Updates to elements or attributes (such as renaming elements or moving branches) are synchronized and reflected in CDF. However, when elements or branches are deleted in PI-AF, the corresponding objects remain in CDF, and there is no indicator that the element no longer exists in the source system. This behavior is currently intentional to prevent accidental or irreversible data loss in CDF.While this approach protects data in CDF, it creates challenges for downstream processes. Without any indication that an object was deleted in the source system, it becomes difficult to automate workflows that depend on identifying obsolete or removed elements.Requested capabilityA mechanism to identify when an element has been deleted from PI-AF, without necessarily deleting the corresponding object in CDF.For example, the extractor could mark such objects with a metadata field, tag, or status indicating that the element was removed from the source system.This would allow users to implement their own logic for handling these cases (e.g., archiving, cleaning up, or removing the objects in downstream processes) while maintaining the current protection against unintended data deletion.Use caseOrganizations that synchronize large PI-AF hierarchies to CDF often rely on automated pipelines and asset-based workflows. When assets or branches are removed from PI-AF, there is currently no straightforward way to detect this change in CDF, making it difficult to automate lifecycle management of these elements.Providing an indicator that an element was deleted in the source system would enable users to build controlled automation around these events. Regards Daniel
Hi,When retrieving datapoints in a Pandas dataframe through the Python SDK using the retrieve_dataframe() method the external_id of the timeseries is set as the resulting column header. The external_id is not very readable, and it would be nice if we could specifiy which attribute to be used as column header If there was a parameter in the function called e.g. use_timeseries_name [boolean] we could set the name of the timeseries as column header rather than external ID. This is more readable
Hello Cognite Support Team, I'm working with the Cognite Data Points API and would like to request a feature enhancement regarding aggregation functions. Current Situation: When querying time series data with a specific granularity (e.g., "1d" for daily), the available aggregates (Sum, Average, Count, Interpolation, StepInterpolation, etc.) don't directly provide the first or last actual data point within each granularity period. Feature Request: Could you add first and last aggregate functions that would:first: Return the earliest data point (by timestamp) within each granularity period last: Return the latest data point (by timestamp) within each granularity period Use Case Example: For a time series with granularity: "1d" and aggregates: ["first"], the API would return the first recorded value for each day (e.g., the value at 00:00 or the earliest available timestamp that day). Similarly, aggregates: ["last"] would return the last recorded value for each day (e.g., the value at 23:00 or the latest available timestamp). Current Workaround: Currently, we're fetching hourly data (granularity: "1h") and then manually filtering/grouping to extract the first or last value per day, which is less efficient for large datasets. Question: Are there any plans to add native first and last aggregate functions? If this feature is already available through a different approach, I'd appreciate guidance on the best practice.
The filtering capabilities needs multiple upgrades. Here are a few items below: Add a “Contains” option OR a select all button (which would work like contains, where when you type in the word you want filtered, you can then checkmark all items that appear) Slicers - add ability to drop column filters above the search results, so you have quick access to change results. This is hugely valuable and very common among similar applications Filters mess up tree view. If you try to search or apply filters in tree view, it does not give you the correct results. Example: If I filter by unit, it only shows me a fraction of the assets with that unit tag in the tree view.
As a developer and maintainer of a fleet of projects and sites for my company, it would be beneficial for me to have improved the monitoring capabilities of CDF Functions. As of now, diverting the function monitoring dataflow through a new function and then to an extraction pipeline is cumbersome. For some functions we have, it is the end user that ends up notifying when the data is wrong.Having an easy overview is difficult, as the UI in CDF shows only the latest call status on the frontpage. One of our projects has around 50 functions running. Having a good overview is not easy. It is only when you click into the function calls you may be able to se some more data. Navigating here from a notification from an extraction pipeline is time consuming.An optimal solution would be to have an inherent monitoring metrics in the CDF functions, as well as notification capabilities, as are in the extraction pipelines. It would enable us to monitor all calls on a dashboard. Having the ability to dashboard function call statuses on all functions that I’m supporting would relieve a headache.
Sometimes workflows fail and I really need to know as soon as possible when they do. I think being able to send a well structured email with links to the workflow, the task that failed, and the error from the task would be the perfect addition to workflows. Is this feature in the roadmap and what can I do to influence the decision to prioritize it?
This feature request is to implement email notifications for transformation errors within workflows.
Currently, the Japanese translation for the operator used to perform exponentiation in Charts is shown as 「電源」, but this makes it difficult to understand at a glance what the function actually does.Would it be possible to correct this to a more appropriate translation? It’s a minor detail, but since this is a function that is used fairly often, I would really appreciate it if you could consider reviewing the translation.
In Charts, it’s possible to freely configure the units for each time series.However, I’m having trouble when trying to merge a manually set unit with the default unit.For example, in the screenshot, the upper time series is a calculated value added using “Create calculation.” I manually set its unit to “°C,” and attempted to merge it with the lower time series using “Merge unit.”But Charts recognizes them as different units, so the merge doesn’t work properly. To work around this, I have to manually reassign the unit “°C” to the lower time series—even though it already has the correct unit. This is quite time-consuming.If I'm doing something wrong, I would really appreciate it if you could point it out.If this behavior is actually by design, I hope it can be improved in the future.
I'm seeking help and guidance from customers who have tackled or enabled features to improve the LINES when connecting files and assets within Cognite Canvas.We seek to have our connected lines more accurately flow and follow P&IDs as they are added to the canvas. Making the lines conform and adjust vs. extending across the visuals on the canvas.This means these lines should follow the “path” on the connected P&ID where they begin on the document vs. connecting randomly into the side of the document.
Current BehaviorIn the transition from InField 1.0 to InField 2.0, PDF rendering on mobile devices shifted from utilizing the device's native viewer to rendering in-app using the Unified File Viewer. Native viewers are written in native code (C/C++) and render directly to the GPU meaning that they can stream pages and down-sample large images on the fly without memory constraints. But this change, while necessary to support advanced interactive features, subjects the viewer to strict memory limits enforced by mobile browsers (e.g., iOS Safari, for example, caps total canvas pixels at ~16.7 million.). Consequently, when a user attempts to open a highly complex or large document that exceeds this safe mobile rendering threshold, the browser fails without providing any notification or context to the user.Proposed SolutionImplement a clear warning prompt within the Unified File Viewer when a document’s size exceeds the safe mobile rendering limit. A notification such as, "Document size too large for mobile, please use desktop," should be displayed to the user instead of the application failing silently.ValueThis enhancement will significantly improve the user experience by setting appropriate expectations and providing actionable guidance when mobile browser limitations prevent document viewing.
Alternate Tank Numbers – It looks like the alternate Tank numbers are not included. I tried to search for Tank 35-2 and it wasn’t able to locate it. Would be possible to add a field for the alternate name for tanks?P&ID Connections – I like how Cognite draws connection lines between references currently, however I think this could be improved by adding a conditional for matching line number so that each exact pipe connection only is shown.Text ID – on some of the P&IDs, it looks like the text identifier struggles to ID rotated text, is there any way to improve this? Ex. Can the AI run another similar search with each P&ID rotated 90 degrees?
Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
