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
A customer from Oxy reported this.Issue describedThe current system restricts visualization of activities based on their distance from the activity of interest, limiting the user’s ability to comprehensively deconflict work. For Maintain to function effectively, users must have confidence that all relevant activities are visible in both 2D and 3D views, regardless of their spatial distance.
To frequent users of data explore, we use to click and make sure that annotations to other diagrams are correct in explore, but when we click annotations to other diagrams “open in canvas” botton appears right above the annotation and it makes hard to see the text below it.Is there any other way out to implement “open in canvas” feature? Such as implementing those bottons in property area on the right?
Cognite’s names for Categories (eg. Assets or Equipment) does not align with our companies internal FLOC/Asset/Equipment naming structure which is consistent across our internal source systems. We would like the ability to re-name Categories or fields from each source system so that we can maintain consistency across all of our data systems and make the user experience much cleaner and less confusing.
Thanks for the chat yesterday. Have summarised the current expected behaviour on the things we discussed below:Saved to layoutGrouping Filtering Sorting Columns you select to show Colour coding on ganttSaved to browser cacheColumn width Column order (overwrites what you have configured to be the default) What is saved to the browser cache will remain there unless it is cleared. We suspect that your browser is somehow cleared. We could look at that in a follow up session perhaps unless you know this is happening? In any case thinking we should include these two as part of the layout. Further, the issue u experienced with the grouping using layout is a bug. It does not clear the previous grouping. We will fix this one. Let me know if you have additional thoughts on this!cc @Daniel Knutsen
A customer from Oxy reported this.Issue describedAfter applying filters and creating a new Maintain Layout, if the user then tries to re-select the newly created layout, it seems like nothing happens - giving the impression that the layout isn't working.This flow is not intuitive. Users expect that clicking on the newly created layout should always revert to the saved layout filters, regardless of whether it's technically still selected.
As a user i want to have the possibility to select multiple activities and shift them all by a selected timeframe (e.g. 2 days, 2 weeks, 1 year ….)Reason: Often we have Projects with multiple activities and there are delays communicated, e.g missing spare parts so we have to shift the hole project! This is currently not possible and you might to adopt start and end date for a bunch of activities which is very time consuming! This is a downside especially when direct planing is used and the activities are created directly in the tool! (Other planning software such as Primavera or MS Project have this as an standard option)@Marius Biermann as discussed in the last Feedback session!
We’re able to attach physical documents and photos, but if we wanted to attach a link to a canvas or chart to support an observation, I’m only able to do that by putting the link in the text. Adding the ability to attach a link to the observation would give us better functionality.
Users at ExxonMobil Baytown are requesting the ability to show cardinal directions in the 3D models and their associated viewing interfaces to improve ability to locate equipment in the field. There should be a north / south / east / west toggle to show or hide such that if the model has been geo-located that users can see directions related to true north.
Something to improve upon would be canvas connectors on P&IDs.It would be nice to be able to click on lines and vote them up or down or hide them. That would train the model to not show those lines. If a line is voted down, it gets suppressed, or perhaps the AI gets a chance to try again. Lines should not be able to stack. They need minimum spacing. Make the lines rotate through a color palate when they generate so they can more readily show the relations when pulling several P&IDs in. Never allow the lines to run at diagonals. Put little jump over bumps when they cross each other. Allow them to be manually dragged around if necessary.
Hi!This are excelent recommendations → Request throttling | Cognite DocumentationCan be included in cognite sdk?I would like to do something like:client.files.list(limit=-1, retry_strategy=”rt”)Thanks!
Submitting on behalf of KAES Request SummaryAn increase in the query size limit for the GraphQL API in Cognite Data Fusion (CDF). The current query size restriction creates friction for our internal application development teams who need to retrieve moderate to large volumes of structured operational data in a single call.Business NeedOur application developers are building lightweight, data-rich internal tools for frontline operations teams.These applications are designed to pull:Time series samples across multiple sensors for a given production line Associated events, alarms, or trips within a time window Work orders or files linked to that asset via relationships Aggregated or contextual metadata for assetsHowever, due to current GraphQL query complexity or response size limitations, we are often forced to:Paginate aggressively (which requires maintaining state client-side) Perform multiple sequential queries (increasing latency) Fall back to using the Python SDK, which adds infrastructure complexity and is not viable for modern frontend applicationsExample Limitations EncounteredQuerying data for 10 sensors over 24 hours requires multiple GraphQL calls or switching to the SDK Fetching a list of assets and their most recent alarms or events cannot be done in one query Attempting to pull OEE metrics and supporting raw data exceeds query limits if not broken upWhile we understand pagination is supported, in many real-time or event-driven application contexts, pagination introduces unnecessary overhead and user complexity.Workaround LimitationsOption Limitation Python SDK Not feasible for frontend/web apps; adds middleware and cost Pagination Adds client-side logic and complexity, especially for low-latency UIs Query splitting Requires extra logic, multiple API calls, and longer response times Requested CapabilitiesWe are requesting the following improvements:Expand max query depth/complexity or size threshold for the GraphQL API Support batched subqueries within a single call (e.g., 10 sensors, one asset, one timestamp range) Improve documentation and telemetry on query limits, so developers can optimize before hitting errors (Optional) Add async support for large GraphQL queries with delayed response if needed for scaleExpected ValueBenefit Impact Reduced app latency Fewer round trips to CDF, less frontend orchestration required Cleaner, more maintainable code Developers write simpler, declarative GraphQL queries Broader adoption of CDF GraphQL Teams can use GraphQL directly without needing SDK wrappers Better operational UX Applications respond more quickly with richer context for operators and engineers ClosingExpanding the current GraphQL query size limits would have a measurable impact on our ability to scale and sustain application development on CDF. It aligns with our desire to use GraphQL as a first-class integration method — not just for dashboards, but for intelligent, plant-facing apps.We would be happy to participate in design validation or pilot this capability if/when it becomes available.
Customers want to be able to search the contents of a PDF file as part of their search experience. When looking for a tag or piece of equipment, they want to be able to quickly find the relevant information when exploring their data (whereas that equipment “lives” in a P&ID file, a manual, checklist, etc), and not only the Metadata. This capability is currently in solutions such as Documentum.
When clicking on an annotation to a file in canvas, it should display “Description” rather than “source ID”. Source ID doesn’t mean anything to the user. Match what is shown in the file preview annotations. The default name for a file in canvas should also include description, not just source ID.
Canvas should have the ability to drop or create editable documents. These are documents only applicable to the canvas and do not need to be stored anywhere else. An example would be a cover sheet for an execution package/project request form/DSP coversheet/etc.
I really like all the current functionality with Events in Charts. Something I’d like to see is the ability to hover my mouse over one of the Events on the Chart (like those shown below) and see a tooltip with information about the Event I’m hovering over. Being able to configure which fields appear in the tooltip would be ideal, but even just showing the fields that are already available in the event results on the right side of the screenshot would be a great start.
In the current state for charts, we only really see threshold based charts - Greater than or less than a particular value.This is limited since this does not take into account scenarios with timeseries that change state with time.For example if I have a timeseries monitoring pump health as (0 - steady, 1 - transient, 2 - medium criticality, 3 - high criticality) -- I cannot use this threshold based logic without creating a bunch of different alerts for tracking my pump's life health. Are there any options within CDF to tackle such issues?
Having unscoped access rights will never not be an issue. It’s an issue for functions and it’s and issue fir hosted extractors. We want to avoid all or nothing accesses, giving write access to all hosted extractors would never be acceptable, giving access to subset however could be an option.And again, this goes for all resources that are not scoped. It greatly limits their usability in an production environment. Markus PettersenAker BP - Techniacal Domain Architect for CDF
When you open the tree view under an asset, the FLOC are in a random order which makes it nearly impossible to find what you want. I also noticed that not all FLOCs are showing up in the tree view. Are you limiting it to a certain number of FLOCs that show?
On Maintain, after clicking on over lapping WOs, sort the menu of work orders that display on the right side Canvas window based on a specific column from the APM_Activities.
Please add a feature where you can select all when filtering on a “is equal to”. Similarly to how you would do it in excel. This is extremely helpful when trying to obtain a specific data set out of your search. !--scriptorstartfragment-->!--scriptorendfragment-->
With scaling Cognite to thousands of end users, we need a robust canvas management system to prevent the inevitable chaos. Initial ideas include:-Locking down the label generation to specific users-Archive or clean-up of un-used canvas-Folder structure for storing canvas-Better layout of the canvas search engine
Overlapping pop-ups covers the suggested functions in charts. Perhaps the pop up can appear to the side of suggested functions and not block the other wordings.
While comparing the charts, it will be very useful if we have the legends available in same display. May be at top right position or in a horizontal bar above or below charts.
Make the "Categories view" the default view for files related to an asset, as it is the most useful view for the user.
After typing in a search, sometimes “enter” works and sometimes you have to hit the drop down. It’s extremely finicky and we have gotten many complaints about it from end users.
Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
