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
Hi team,There should be a API provision to migrate the pre-existing charts and canvas developed in Dev project to be migrated to Prod. Currently all of them need to be recreated from scratch.
Posting on behalf of Koch Ag and Energy Solutions SummaryWe are requesting functionality to enable support for defining custom GraphQL schemas and resolvers on top of CDF. This capability would allow our team to build tailored, efficient APIs for operational applications that surface actionable insights from contextualized manufacturing data.ContextWe are using CDF to centralize and contextualize key plant data — including assets, sensor readings, events, shift logs, inspection documents, and relationships to business systems.Our application team is developing internal tools for specific use case enablement.These tools require fast and intuitive access to data, but CDF’s default GraphQL schema is too low-level for these user-facing applications.Current ChallengesOur frontend developers must manually chain multiple queries to get asset status, performance trends, and associated work orders. Common business logic (like calculating asset availability, filtering alarms, or joining time series to asset metadata) must be repeated in each app. We cannot easily present business-specific views like “ProductionLineHealth” or “ShiftSummary” without building and maintaining our own middleware.Requested CapabilitiesWe are asking for the ability to:Define custom GraphQL object types that aggregate and shape CDF data into operational concepts (e.g., ProductionLine, MachineStatus, DowntimeSummary) Implement custom query resolvers for calculated fields (e.g., OEE, MTBF, energy efficiency) Integrate external system data (e.g., SAP PM, shift logs, scheduling systems) into a unified query layer Apply business rules, KPIs, and filtering logic server-side for reuse across applications Secure the schema and field-level access based on user roles (operator vs planner, plant vs corporate)Example Use CaseCustom Type: ProductionLineOverviewgraphqltype ProductionLineOverview { lineId: ID! name: String currentThroughput: Float availability: Float topFiveAlarms: [Alarm] openWorkOrders: [WorkOrder]energy UseToday: Float} This schema would simplify dozens of low-level CDF queries into a single, reusable API call for our production dashboard.Expected ValueBenefit Impact Streamlined application development APIs are aligned with plant workflows, not just data structure Lower integration effort Data from multiple sources can be presented in one logical schema Faster time to insight Field users access actionable metrics in fewer steps Consistent KPI logic Calculations like OEE or uptime are standardized Broader adoption of CDF More teams (maintenance, operations, digital) can build on it directly Potential Implementation PathsAllow deployment of custom GraphQL services inside CDF projects (e.g., based on Apollo Server) Provide schema extension hooks that pull and reshape data from CDF's GraphQL or REST APIs Offer first-party support for calculated fields or composite objects in GraphQL Enable hybrid access to external data systems within the same query contextClosingThis capability would significantly enhance how our teams leverage CDF in the field, drive app development efficiency, and improve visibility across operations.We would be happy to participate in design validation or pilot this capability if/when it becomes available.
In Canvas, when you add an Object, if it is related to another object through Annotation (purple lines). We’d like the canvas to show when Objects are related as well (similar to my red lines below). Also, the ability to turn each type of line off independently. !--scriptorendfragment-->
hi, when using rule in canvas, I would like it to be easy to see which rules are assigned to which objects.i can’t do it in rule lists, i have to select each object(shape)to see which rules are asigned to it.I'd be happy to have it checked.
At Aker BP we the need for support of video files. Much like with regular files (PDFs) and 3D models we want to annotate videos towards tags and assets in CDF. An added complexity here is that the tagging within a video should have a time element so that we can tell at what part of the video the tag was seen.Potential use cases include, but not limited to:Drone footage ROV Headcam Robots (boston dynamics like)
As we are learning more about how our users use Canvas, there are two main themes emerging from several use cases. STATIC: Use cases that are focused on events are more static in nature and users DO NOT desire the data on their canvas to change or update. (RCAs, Investigations, work packages, etc.) LIVE: Use cases include collaborative spaces for teams to use for ongoing monitoring require the data (timeseries, files, 3D, etc.) to update to the newest version as it flows into Cognite.We are seeking a way to allow users (or systematic processes -- system built work package canvas) to determine the behavior of the canvas that best suits their needs. This could be a toggle in the settings able to be set by the user in the settings or and setting that can be systematically set. This affects files the most today for us and we have to choose one or the other (we have chosen to keep files live at this point). We are happy to demonstrate examples to help define this out more.
Users are asking for functionality within the note-card or similar interface to be able to have full text editing capabilities, similar to a PDF editor, which would allow them the following (and more, reference PDF editor as needed). Another feature they requested was to have shapes that text can be added to (think of a balloon with an arrow on it) where the balloon can have text put in the middle with the arrow pointing to the line. This could be a shape with a connector if needed but having more defaults (custom created by customer if needed) or prebuilt to standard industry symbols and uses. The balloon reference is commonly used for tie-points for projects, another example could be a triangle with a number in it used commonly for revisions. Details requested for the shape of the box and the text functionality within it. (The users specifically said everything we can do with this product request entry text would be great with reference to this request pane). 1. Change the format including shape (rectangle, circle, triangle, etc.), size (dimensions), color (border and internal)2. Change the font color at a character level (not a whole card level), change the bold/italicized/underline of text, change the justification of the card.
Currently if a checklist was not done due to an UPE or any other plant outage, there really is not a good way to capture these situations. The only options are:Option 1 - Set all tasks to “NA” or “Not OK”, set the checklist to “Done”, & add a note explaining why the checklist was not done.Option 2 - Delete the checklistsNeither are good options from a metric tracking POV. This doesn’t tell the whole story of why the checklists were not completed. Adding a status of “Not Done due to Outage” or something similar would easily give us insight into situations like these.
Provide an additional attribute level to filter 3D resource layers, e.g. “Unit” or “Project”. Example:CAD models → Project → Model NamePoint clouds → Unit → Point cloud Name
We recently encountered an issue where we had to delay a task in a workflow to wait for transformation metrics to become accurate. To solve this we put a sleep in a Cognite Function. We can also use external function calls to create a delay, but I was thinking that this might be a feature that would be nice to have built-in to Data Workflows.Considering that there are times when you may want to delay a task for n minutes:I was wondering if there are any plans to add a built-in delay task-type, or a delay field for the existing task-types, into Data Workflows?e.g.# maybe put it in the dependsOn field #############################- externalId: someTask type: ... ... dependsOn: - externalId: transformationTaskId1 delayMinutes: 10# or as a dedicated field for each task ###########################- externalId: someTask type: ... delayMinutes: 10 dependsOn: ...# or as a unique task type ########################################- externalId: '10MinutesAfterTransforms' type: delay minutes: 10 dependsOn: - transformationTaskId1 - transformationTaskId2- externalId: someTask type: ... dependsOn: - externalId: '10MinutesAfterTransforms'And if not:Is this something the Cognite team would consider adding?Currently I think you can build a dedicated delay function by having a Cognite Function forward a delay instruction to an external endpoint using the isAsyncComplete flag, and have some external process tell the workflow to complete the task when the delay is over.But I imagine this is the sort of thing that many teams who use Data Workflows would eventually need to build themselves.You can also sleep inside the Cognite Function but, it’s wasteful since you’ll be paying for the time slept, it will increase the risk of the function timing out, and the function needs to “know” more about timing quirks of the other processes in the workflow.
Hi,Currently, transformations must target a view to populate a container. But if we update the view (e.g. remove an attribute that we no longer want to expose), the transformation will no longer populate that field — even though the container still supports it.As a result, existing users relying on older views that still expose this attribute will see empty data, creating unintentional breaking changes.Suggestion: Enable transformations to write directly to containersThis would:Ensure stable ingestion regardless of view changes, Prevent breaking downstream users, Simplify the data pipeline.
In order to make it easier to use the data registered in CDF, we propose the development of a data linkage function with Excel.From the data registered in the CDF (mainly time series data), for example, when creating a plant operation report,Right now, I have to download the time series data as a CSV, then copy and paste it into the report, which is very time-consuming.If it is possible to acquire data directly into Excel cells by the Excel linkage function, the utilization of data will be promoted.There is still an Odata function, but it would be best if it was in a more user-friendly form like an Excel function.
Create a “next Day/week/month” button in Maintain to easily move from one time period to the next without having to click 6 times to select a new timeframe.
Enable assignment to More than one Grid Zone, some activities such as drain piping can extend through multiple grid zones and therefore need to deconflict large areas.
For a good User Experience, in general, a Cognite Specific Icon should serve the same purpose in all Cognite programs. Navigation and functionality should be similar across modules. Cognite should adopt a consistent philosophy in how you manage this and converge all of your applications for consistency:1) When you search for MBD1070, CDF finds MBD-1070, but Maintain does not find any asset.2) In CDF, when you pan to another asset in the 3D model and single click , you can select the next asset over (MBD-1270) and open the meta data. In Maintain, if you select another asset you highlight the shape only. You do not get any data or even identification of the asset.3) When you select an integrated asset (PW-424-A) in CDF you get a section of pipe and 6 valves. In Maintain, you are able to select and highlight a single valve or shape.4) Maintain has no access to photogrammetry or laser scans as layers in the 3Dmodel.5) You are able to take measurements in both Maintain and CDF modules, but the measuring tools in CDF are much more robust (polylines, polygons, areas, volumes). Maintain has straight line distance only. In CDF you can change the units from metric to English, in Maintain distance is in mm only.6) CDF allows slicing in all three planes. Maintain allows slicing in the vertical plane only.7) In canvas, if you add a 3D view, you cannot use any of the 3Dmodelling tools, such as measurements.8) The icon for adding layers in CDF search changes the marker legend in Maintain9) An icon with a question mark in CDF shows Navigation guidance, while an exclamation point shows the same information in Maintain.
The engineering team will add support to allow a user to load single 3d model in 3D page when there is no location or scenes are configured.
When working with Charts we often start testing it in the “dev” environment where we collect relevant timeseries as a set. In order to then proceed we normally move on to run tests in “qa” and finally our “production” environment. Unfortunately each time we need to recreate the Charts setup from scratch since we could not find a way to export/import or simply copy over a Charts setup to a new environment. Having such a feature would be a great help
Request CDF to be able to auto pre-sort the documents into different groups
Diego, Sofie,Can we please put a direct link to 3D search in the left-hand navigation pane?
Define graph axis for time series data in Industrial Canvas. In this example below, date range and UOM are needed to understand the graph effectively. Submitted at the request of the Cognite project team
By default, filters in Cognite seem to be set to “AND,” meaning that to get a successful return, if you have slected two criteria, the target bust have both properties. There are times when the user wants to cast a wider net, and use “OR,” meaning that the filter will return results if either criteria is met in the filter. For example, if the user wants results from two different platforms, but not all platforms. Or, in some cases, the filter will not allow the user to select the filter element because of this property. Suggest standardizing how filters work and allow user to select either “AND’ and “OR”
When a CDF transformation fails the error message could be more details pertaining to which record instance (external id) caused it to fail. Currently the CDF transformation provides the error why it failed but no information on which record caused the failure.If the transformations are triggered using python SDK, the returned object contains detailed info on which instances caused the transformation to fail. Some similar details would help with expediting the debugging and resolution process.
Is it possible to add support to combine name and SourceID as the external ID.From a Data management point of view the best solution might be to use PointID. But from a consumer point of view it might be more convenient to use name. However with name we have the possibility to overwrite if there is created a new timeseries with similar name. But how about a combination? external-id-prefix string Enter the external ID prefix to identify the time series in CDF. Leave empty for no prefix. The external ID in CDF will be this prefix followed by either the PI Point name or PI Point ID. external-id-source either Name or SourceId Enter the source of the external ID. Name means that the PI Point name is used, while SourceID means that the PI Point ID is used. Default value is Name.
Currently, there is no checkall button in Data Model → Data Management. If I have a long list of data that I would like to export/download to CSV file, I have to tick the data row by row.
Instead of writing lot of yaml configuration files in the CDF tool kit better to generate those using trained Chatgpt models to generate. Nowadays Kubernetes deployment yamls are getting generated instead of configuring it manually.We can make use of this github repo to get some idea about generating yaml files. https://github.com/Luxadevi/yaml-generator-Litellm
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
