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.
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.
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.
We currently have the ability to turn off annotations & connecting lines in canvas. I do not always want these annotations because they can make the canvas become too “busy” on a canvas that I’m using on projects where I just want to share the canvas, collaborate, or present. Sometimes people I share the canvas with may not know how to turn these off. I would like for Canvas to cache or “remember” my choices so the annotations/connecting lines do not have to be turned off each time someone opens the canvas. Default should be to have these turned “on”. I would just like them to stay “off” once I select that choice. Attaching visual examples. I would be happy to answer any clarification questions. Thank you!
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.
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.
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?
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.
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