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.
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?
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
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.
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.
To use Canvas for Incident Investigations in our company, we need the cause map to be much more customizable. Currently the cause map defaults to arrows pointing to the left, it would be better if there was no arrow at all instead of pointing one direction or another because we don’t want to have to change direction on every single box. Also, when adding a box below another box, it defaults to a parallel path instead of a box directly under the primary box.
The 3D preview, like what is shown on the asset search preview tab, is unusable with default settings, as the render quality is too low and the point size is too large. We need the ability to set a global default setting for this preview that is usable with our 3D data. Example-
Users would like to see visible annotation / connection lines for equipment drawings (or files) that are linked to assets. The files are linked to assets based on the file meta-data. Currently in Industrial Canvas, it is clear from the asset view that the files are directly linked however in Canvas there are no visible connection lines between the file and the assets. Users will be able to quickly see how their data is connected and drive work package development, RCAs, and other use-cases in Canvas much easier.
Engineers completing calculations on equipment (required thickness, remaining life, etc.) have an interest in building calculations within Canvas. Specifically, when performing RCA or engineering workflows, these calculations validate hypothesis and are currently done in other applications. Having the ability to have default calculations that can be reused would be helpful for non-time series type data. This may come in from an inspection report (we have a pipe this thickness) and we want to validate whether it is acceptable to run. The output should show the calculation, the inputs, and the output.
Hello All,A repetitive feedback we got from clients is that they noticed when a checklist is assigned to a person- they recieve no notification for it - they have to go to “assigned to me” tab & check .They wish there would be an email notification - at activity assignment stage & at expected execution day / a few hours prior- with all checklists assigned to person so they would know to open app & start executing them.
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