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
Datasets have an “Access Control” page where you can see which groups have access.A similar feature is needed for Data Models / Spaces, so that we can quickly identify which groups have access.
When dropping a file from your desktop/drives into Canvas, the file size increases. As one example, it went up 30 times; from 84kb --> 2520kb (without the canvas coverpage). The file size change makes it difficult to download the canvas, as it gets stuck. The end users cannot download the canvas they create and therefore are prone to stop using the platform.
Currently, I don't think there is a fixed order in which checklists issued by Infield are displayed, but this makes it difficult to know where the checklist you are looking for is when you are looking for a checklist. I think it would be easier to find if you could sort by "Start time" in the checklist, but is this function feasible?I think the default sort order should be the most recent start time, but I would also like to see the ability to switch to oldest first.I would like to use this function for the list of checklists in the "Checklists" tab and the list of checklists in the "OverView" tab. (In "OverView", if you narrow down the checklist by search, you will not be able to use the sorting function of "Start time")
Hello,While developing inside of Canvas, it would be nice to be able to utilize the grid in the background by allowing us to optionally snap to the grid.
Documents that are most important for the technician should be listed first, e.g. P&IDs (XB).
Hello Cognite team,First of all, thank you for your continuous development and improvements to CDF.I'd like to share one feature request based on our daily use of Charts and Canvas.Our use case In our long-term operation monitoring work, we create multiple Charts for different monitoring items and paste them onto a single Canvas, so that we can monitor many Charts together in one place.The issue The ability to select multiple Charts on Canvas and change their display period all at once is very convenient. However, when we open the same Canvas a month later and refresh to the latest data, the start time stays fixed at the point we originally set. As a result, the displayed time range keeps getting wider and wider over time, instead of showing a consistent window.What we'd like We would like a feature that lets us refresh Charts using the same fixed period — for example, a rolling window of the last 1 month, 3 months, or 1 year — so the time range stays consistent every time we open the Canvas.This is already possible in Charts by clicking the heart (favorite) icon, but the same capability is not available on Canvas. We would love to have the equivalent function on Canvas as well.Thank you very much for considering this request.
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.
When clicking a file’s annotation, can time series records in the “Time Series” section be clickable links that open the time series in a new tab? You are already able to do this with Asset/File (green square in picture) Currently customer has to manually type in the name(s) of the TS they want to investigate, changing these to links would improve user experience significantly.
Hi team, I'd like to submit a feature request. Request In Charts, a line is only drawn up to the point where a value is registered in the time series. I'd like an option to draw a horizontal line from the last value up to the current time (NOW). This is especially an issue in calculations. When a formula uses multiple time series that are registered in CDF at different times, the series that ends earlier is plotted only up to its last value, so the calculation result is cut off there. I'd like to avoid this. ExampleGiven two time series Ts_long (up to today) and Ts_short (up to 2025/04/01), using them as calculation sources pulls the output toward the Ts_short time axis, so nothing is displayed after 2025/04/01.Reference テスト Copy（工務 久保田） | Cognite Data FusionCognite Hub
Allow Custom Symbols for Dataset CategoriesWe would like the ability to assign custom icons or symbols to datasets rather than using the standard black dot that is displayed today.Allowing unique symbols would help users quickly distinguish between dataset types, sources, or business contexts, making the search results easier to scan and navigate. This would improve usability, particularly in environments with a large number of datasets.Expected BenefitsImproved discovery of newly added datasets Reduced user clicks and navigation friction Better visibility into available search content Faster identification of datasets through visual differentiation Improved overall search usability and adoptionThis enhancement would make the search experience more visually intuitive for end users. @Andrew Montgomery
Search Experience ImprovementsWe would like to see the "Show More" expansion button removed from the Search experience.Today, as additional datasets are added, the interface progressively hides content behind the "Show More" control. This creates friction for users who must repeatedly click to access information that is already available. More importantly, users who are unaware that new datasets have been added may never discover them because they remain hidden by default.Instead, we recommend allowing the full list of datasets to be displayed in a scrollable view. If the number of datasets exceeds the available page space, users can simply scroll through the list rather than repeatedly expanding sections. This would improve discoverability, reduce clicks, and create a more intuitive search experience.Collapsed Expanded@Andrew Montgomery
To keep clean structure in Charts monitoring jobs.
The current Cognite Grafana Plugin supports Time Series, Activities, and GraphQL-based queries, but does not provide native access to Records and Streams.As Records and Streams become increasingly important for data ingestion and operational use cases, native support within the Grafana Plugin would enable a more complete and consistent visualization experience directly in Grafana.Requested enhancement:Native querying of Records and Streams from the Grafana PluginSupport for filtering and visualization of Records dataIntegration with Grafana panels and dashboards without requiring intermediary services or custom pluginsThis enhancement would simplify data consumption, reduce implementation complexity, and improve the usability of Records and Streams across operational monitoring and reporting scenarios.
Hi Team,In regards to Cognite Data Model UI we understand that the below features are currently not supported and would like to add them here as a Product Idea requests -Reorder the Sequence of the Views listed in Cognite Data Model UI. For example, Under "Assets" category we have 1) Piping Tag 2) SAP Assets. We would want the "SAP Assets" View to come first followed by the "Piping Tag" View. This would make easier for end users by having important and frequently visited views on top. Also, would reduce the number of clicks a users has to make to get the the required data - for example in Canvas when we want to "Add Data", the default category is set to "Piping Tag" and user has to switch to "SAP Assets" to get to the right view. Option to HIDE some of the views from the Data model UI main/home/landing page. Most of the Views need not be accessible from the Data Model main page and can be accessed through relationships. For example - Under "Activities" category we currently have 11 different categories. We done need "Work Order Operation" on the main page but can be accessed through "Work Order" View and its relationship with "Work Order Operation". We would like to hide these categories from which a user would typically not start their data search journey with. In below screenshot you see that some of the names of the Views are truncated in the categories panel. This panel seems to have static width and does not seems to have a feature to expand to see the entire names of the views. We end up having to hover on top to get to the right view which again becomes time consuming when we have many views to search from. Requesting if the sizing of this panel can be made dynamic.
RequestTo improve business continuity and operational stability, we would like to request your consideration for developing official applications within InField that provide the following capabilities:An application that can export individual inspection forms in both CSV and PDF formats. An application that enables approval of individual inspection forms and allows users to view and track their approval status.BackgroundCurrently, we operate a workflow in which inspection results are entered through InField, exported using a Streamlit application, and then submitted for supervisor approval through another Streamlit application.Under normal circumstances, this workflow functions without major issues. However, due to a Streamlit application issue that occurred yesterday, the workflow became temporarily unavailable. To the best of our knowledge, this is the second occurrence of a similar issue this year.In addition, since Streamlit is currently provided as a preview feature, we have concerns about relying on it as a core component of a workflow that supports critical daily inspection activities at a refinery. From the perspectives of stability and operational reliability, we believe there are limitations to using a preview feature for such business-critical operations.By implementing these capabilities directly within InField, dependence on external components could be reduced, leading to improved business continuity and greater operational stability.Furthermore, export functionality and approval workflows are commonly required features in inspection management systems used by Japanese companies and are generally available as standard features in many inspection applications. For this reason, we believe that providing these capabilities as native InField functionality would lower the barrier to adoption for Japanese companies and potentially contribute to broader adoption of InField within the Japanese market.We appreciate your consideration and look forward to your feedback.
Hi team,I'm a Cognite Data Fusion (CDF) user, and I'd like to submit a feature request regarding scheduled calculations in Charts that write results to a time series tag.Current behavior (as I understand it) When you set up a scheduled calculation in Charts to store results as a time series, the calculation only runs from the point the schedule is configured onward. It does not compute results for any period before the setup time. I confirmed this behavior in the following Hub post: 🔗 Cognite HubWhat I'd like to see I'd love an option to backfill / calculate historical data retroactively, so that the scheduled calculation can also produce results for the period before the calculation was created.Why this matters With this capability, we would be able to go back and review historical data as well, not just data going forward. This would be very valuable for our long-term monitoring and trend analysis, where being able to look back over past periods is essential.Thank you very much for your continued development work — this improvement would be a great help.
**Component**: OPC-UA extractor · `EUInformation` handling **Current behaviour** (confirmed by Cognite): the extractor never reads `NamespaceUri` or`UnitId` from `EUInformation`. The only value that reaches any config surface is thecomposed `DisplayName: Description` string. The UNECE code is dropped before`metadata-mapping` can see it, so `unit` / `unitExternalId` resolution to a`CogniteUnit` from the source unit is impossible today and is not planned. **Request**: carry `UnitId` through, and resolve the CDF `unit` direct relation from it. **Why it matters to us**: across our fleet the `unit` direct relation is populated on**0 of 2772** time series, while 528 of 854 at one line carry the composed string in`sourceUnit`. The only path available is post-processing that string-matches against theCDF unit catalogue. That is brittle in exactly the way a code-keyed lookup is not —`kW·h: kilowatt hour` has to be parsed and matched by display text, and it will differby server locale, by punctuation (`kW·h` vs `kWh`), and by however each gateway'sengineer typed the description. `UnitId` is an integer-ish UNECE code designed forprecisely this lookup. **Also useful even without resolution**: expose `UnitId` as a `metadata-mapping` sourceso consumers can do the mapping themselves deterministically.
Hi - It would be a huge time saver to have a filter somewhere (rather than file name) for all documents / drawings / diagrams that have been parsed. Imaging if I have 500+ pages or files to approve, i would only be interested in reviewing those that the system have captured my assets.
I am following up on the ability to view native files such as DWG and DGN in Cognite? We were promised that this will be enabled at some point.
Using Search, when selecting an instance and then choosing the Properties tab, all the populated properties are listed with the key and value in two columns. The key column is apparently a fixed width column (40ish char wide), not possible to manually resize, and it doesn’t resize when the browser window is resized. This becomes a problem when the property key is long, something that may happen when the property is a JSONObject such that the key becomes “nested” Below is an example of how it looks It seems like the UI is able to wrap the line if the key either has a space or a hyphen, but not else (have not tried all characters...) We can of course mitigate this by creating more compact keys, but it would be really helpful if we could resize the column such that our key naming convention do not have to take a 40 character UI limitation into account.
Recently, the use of Charts has been increasing, and more users are creating complex calculations for data visualization.In this context, we have received feedback requesting a “Back” button (undo function).When users are building complex calculation formulas, there have been multiple instances where the calculation source suddenly disappears, forcing them to restart from scratch. The more complex the calculation, the greater the impact of this issue.To mitigate this, it would be extremely helpful to have a function that allows users to go back one step (e.g., an undo or back button).We believe this feature would significantly improve usability and reduce the risk of losing work during calculation editing. Thank you for your consideration.
Hi there, We would like to be able to annotate instances that do not extend CogniteAsset, nor CogniteFile and visualize that in “Preview” in Search UI. Our context is purely data modeling.So we would like to have a view, that extends CogniteDescriable and to be able to annotate it towards a CogniteFile.Currently we are achieving partically that, by having an edge, (pseudo code below) ANNOTATION_TYPE = "diagrams.InstanceLink" type_node = NodeApply(space=REFERENCE_SPACE, external_id=ANNOTATION_TYPE)edge = EdgeApply( space=EDGE_INSTANCE_SPACE, external_id="annotation_<file_ext_id>__<entity_ext_id>", type=DirectRelationReference(space=REFERENCE_SPACE, external_id=ANNOTATION_TYPE), start_node=DirectRelationReference(space=FILE_SPACE, external_id=FILE_EXTERNAL_ID), end_node=DirectRelationReference(space=ENTITY_SPACE, external_id=ENTITY_EXTERNAL_ID), sources=[ NodeOrEdgeData( source=ViewId("cdf_cdm", "CogniteDiagramAnnotation", "v1"), properties={ "startNodePageNumber": 1, # 1-based page index "startNodeXMin": x_min, # (center_x - half_size) / page_width_px "startNodeXMax": x_max, # (center_x + half_size) / page_width_px "startNodeYMin": y_min, # (center_y - half_size) / page_height_px "startNodeYMax": y_max, # (center_y + half_size) / page_height_px }, ) ],)And it works particallyThe annotation is visible on the file preview, however the bounding box is just gray, nothing happens when you press it and no specific “info box” appears on top of it.Also on the right part, where is the list of all annotations, we have found out that this list filter is hardcoded to deriveables of CogniteAsset or CogniteFile, in our case our custom View is neither CogniteAsset nor CogniteFileSo I would like to ask a feature request, to display and visualize all of the annotations, even if they come from custom views, and not only the derivables of CogniteAsset or CogniteFile.Basically, if there is an annotation to it, I would expect that:bounding box will be coloured clicking on the bounding box will display the view name, instance name and instance description on the right panel the view will be filterable and listable (in Document preview in Search UI) I am part of data engineering team in AkerBP, so please do try to contact me for demos and examples, via AkerBP’s internal communication channels.
So, when I get documents to populate in canvas, it drops them off in an unorganized bundle. I tried to get ATLAS to organize them in a timeline but ATLAS states “I can add documents to the current canvas, but I cannot move or rearrange existing canvas elements with the available tools. Please drag the four cards into this left-to-right order:”. Is an update that can make it easier to organized documents in canvas. It gets very cluttered and time consuming to organize these documents when you have like 20-30 documents populating on canvas.
As per the 3D Config feature, it should be good to have a Canvas Config option to configure the colouring for a quick highlight of the contextualization results in a Canvas for P&ID or any “plan” documents like isometrics loaded in a Canvas.In the configuration option we should be able to select attributes/data linked to the OCR captures, then in Canvas we should have a button to select and highlight all the OCR captures contextualized to PI-Tags, 3D tags, WOrkorders, SECE equipments…This option is of importance, it will avoid to check one by one each equipment in a P&ID, it will accelerate the completion of the contextualizations workflows, but not only… it’s also of importance for operations when preparing an intervention.
Due to the limit on the number or Views/revisions, we need to deprecate and delete old revisions on a regular basis (in periods with heavy data model development). For Atlas agents and Canvas’ we can find the View versions via the API, allowing us to identify users depending on models that are deprecated. However, with Charts I cannot find any way of programmatically finding this.Is there a hidden API somewhere that allows me to inspect what the different Charts are relying on? If not,. this is an important functionality for governance of data models and needs to be added.
Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
