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.
When working on hosted extractor format / mappings, I always had to copy / paste my examples to test format.I would like to upload examples so I can validate them all at once.Having a list of the example name and a summary of the created resources (like “1 datapoints and 1 timeseries “ or “1 table row”)
I have a View that is an extension of CogniteAsset. There are a lot of properties in the View that are not visible via Search. These are simple data types like String and Boolean. Is this by design? The only way of seeing all the properties is to open the instance in Canvas, but then the information is shown as an image, making it impossible to copy the property value.
There somecases where the site needs to always have one checklist available and if this available checklist was executed, a new one needs to be created automatically.A real use case is for Madurai site and also for Forli. Unloading checklists doesn’t happen in a defined recurrency but they need to have one available all the time if needed.Considering the usage without a digital tool, think like you printed many copies of a checklist and the user will just come to a room and get the paper to be filled in.Some checklists needs to be always available on the checklist list so users without permission to create a checklist could execute.
Problem Statement : There is an increasing demand from one of our key regional customers to embed third-party dashboards and visualizations - such as those from Power BI or similar platforms - directly within the CDF Canvas environment. However, the current platform limitations prevent the embedding of third-party visual content via external URLs. At present, the only available workaround is to provide users with a hyperlink that redirects them to the external site, which disrupts the user experience and limits seamless integration.The Ask:Enable functionality within CDF Canvas that allows users to dynamically load and render third-party content - such as dashboards or visualizations - using API calls or embedded URLs. This enhancement aims to provide a seamless, integrated user experience without requiring redirection to external sites.Benefits:Enabling embedded third-party content within CDF positions the platform as a centralized hub for accessing high-level metrics and dashboards. Users - ranging from operational SMEs to upper management and key stakeholders - can view critical insights without navigating away from the platform. This enhancement is expected to drive increased monthly active users (MAU) across a broader range of roles, reinforcing CDF as the go-to interface for decision-making and operational visibility.
Our extractors doesn't support routing data from running instance to different spaces/datasets. This approach will become a major issue when we scale to many sites for one customer. Could we make it possible to assign space/dataset dynamically based on some information in the payload. This is based on experience from our SAs, potentially from several of our customers.
I am submitting this idea on behalf of LyondellBasell, and it consists on the ability to search for parts of a name, whether that is a filename, equipment name, asset, etc. One scenario is that an end user is interested in a particular subsystem (ie a flow loop), so the user would search for the number of that subsystem expecting all elements of that subsystem to be returned. For example, searching for “28806” would return:TI-28806 TI28806 TE-28806 PI28806 HY28806 HY-28806
Request per multiple end users, using multiple different devices-Add scroll bars to the right and bottom so that the user can scroll instead of having to drag their way around the screen and then zoom in/zoom out
ArcGIS Enterprise is a central data source for our 2D/3D geospatial data, with rapidly growing content and high value use-cases. It would be very useful to be able to view and contextualize this data in CDF, reducing the end-user need to access multiple systems to collect data, while also augmenting existing data and use-cases for CDF. REST api, iframe and various standardized GIS formats are available to facilitate this integration, and the ability to contextualize this data will be key to value.
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.
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.
With the use of Cognite Core Datamodel, we can create different types of Assets. Right now I have a case where I have EquipmentTag and Functional Locations.An EquipmentTag always has a FLOC a parent. So the Hierarchy is always:FLOC1-- FLOC1.1----EquipmentTagFLOC2--EquipmentTagIn this case, If I open the EquipmentTag, te UI is trying to get all the hirarchy as EquipmentTag, so the UI knows that exists a path, but can’t create the tree-view cause no data is returned. If I open the same EquipmentTag just as an Asset, the tree-view works fine, but then I lose all the specific data from my EquipmentTag.Openning as EquipmentTag
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.
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