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
The comment feature in Canvas is really great and we are planning to use it for our shift handovers. We plan to add multiple comments but having to click the comment icon every time to read the content is quite tedious. Since we want the comments to be immediately visible as soon as we open Canvas, we would love to have a feature, like ”pin” comment content.
The proposal is to get in the Search overview, the location of the contextualized tag in the 3D CAD structure. Such feature will help the user from where the 3D CAD contextualization is coming from in teh 3D CAD structure.Rigth now we do not have this feature, and this should allow us to potentially correct, add, remove some pieces of the 3D CAD structure contextualizationSee the attached illustration...
When dropping a file from your desktop/drives into Canvas, the file size increases. As one example, it went up 30 times; from 84kb --> 2520kb (without the canvas coverpage). The file size change makes it difficult to download the canvas, as it gets stuck. The end users cannot download the canvas they create and therefore are prone to stop using the platform.
Hi Team,It was observed that List and Search queries have some functional limitations which are handled explicitly by teams. Below are the expectations: Search queries must support pagination, enabling users to retrieve results beyond the current 1000-record limit. Pagination should include a cursor or offset mechanism, allowing seamless navigation through large datasets without data loss or duplication. List queries must support case-insensitive filtering Users need substring search over large datasets, which is not fully supported. Can we provide feature like "Contains" which will allow substring search.Thanks,Rahul
Problem Statement: Currently, there is no great way to print comments in industrial canvas (If there is not aware of a good way). Potential Solution Option(s):Anchored to DocumentComment Selection box in the download list (similar to multiple pages) that would allow comments to be turned on that would be anchored to the document based where the user placed it. Comment Pane on right side that shows comments for that page. (Similar to microsoft suite review pane)Separate Comment PageComment Page independent similar to the cover page that could be checked or un-checked that would display on a separate page that would be part of the download. Downside is the comments may not make sense if there are not associated with the drawing.
Cognite Data Fusion (CDF) appears to enforce a limit of approximately 200 Azure AD group memberships when resolving permissions for Service Principals. This limitation does not exist in Microsoft Graph, which supports retrieval of all group memberships associated with a user or Service Principal.As organizations scale their authorization models using Azure AD groups, this restriction can prevent access inheritance from functioning as expected and requires manual workarounds that increase operational overhead and governance complexity.Business ContextMany enterprise deployments use Azure AD groups to manage access to assets, plants, data products, and other resources within CDF.A common architecture relies on: Azure AD groups representing access domains. Group Object IDs mapped to corresponding Source IDs in CDF. Service Principals inheriting permissions through group membership. However, when the number of group memberships exceeds the current supported threshold, some memberships are not considered during authorization, resulting in incomplete permission resolution.Current WorkaroundThe current workaround consists of adding Service Principals directly to individual access groups instead of relying on inherited permissions through the existing group structure.While functional, this approach presents several challenges: It does not scale as the number of groups and data products grows. It increases administrative effort and maintenance activities. It complicates access governance and auditing processes. It introduces a higher risk of configuration errors and permission inconsistencies. Problem StatementThe current behavior creates a gap between Microsoft Entra ID (Azure AD) authorization capabilities and CDF authorization behavior.Since Microsoft Graph supports retrieval of all group memberships, the limitation appears to stem from the current implementation within CDF rather than from the underlying identity provider.This can impact organizations that rely on group-based authorization models to manage access at scale.Business ImpactOperational Impact Increased administrative effort for access management. Additional maintenance when new groups, assets, plants, or data products are introduced. Reduced efficiency of centralized identity management practices. Governance Impact Increased complexity in maintaining access-control policies. Reduced effectiveness of group-based authorization strategies. Greater effort required for auditing and access reviews. Security and Compliance Impact Increased reliance on manual permission assignments. Higher risk of access inconsistencies. Potential compliance concerns resulting from non-standard authorization processes. Scalability Impact Reduced scalability of Azure AD group-based authorization models. Growing operational burden as enterprise environments expand. Limitations on adoption of best-practice identity and access management patterns. Requested EnhancementEnhance CDF authorization to support all Azure AD group memberships associated with a Service Principal, or significantly increase the current limit, ensuring alignment with Microsoft Graph capabilities.Possible implementation options include: Removing the current membership limit. Supporting pagination when retrieving group memberships from Microsoft Graph. Supporting complete transitive group membership resolution. Providing configurable limits for enterprise deployments where required. Expected Benefits Improved scalability of enterprise authorization models. Elimination of manual access-management workarounds. Better alignment with Microsoft Entra ID / Azure AD capabilities. Reduced operational, governance, and compliance risks. Simplified lifecycle management for users, groups, and Service Principals.
The layers on a PDF are not currently clickable within CDF. I have an example of a file that was loaded as a PDF with certain layers turned off. When we put this PDF in a canvas and then downloaded the canvas, all the layers were turned on, making it difficult to read. It appears Cognite turned on all internal PDF layers when creating the download.Ask: A - Let’s leave the layer state as is when downloading from a CanvasB - Don't embed the layers and leave them exposed in the resulting PDFC - Have layers viewable in Search PreviewD - (Future) Expose the internal layers in Canvas/preview
SummaryWhen building workflows in Cognite Data Fusion to populate views in Data Models, there is often a need for intermediate, curated datasets between raw source data and the final target data model.Today, this intermediate data can be stored in RAW tables, but that requires customers to manage temporary tables, cleanup logic, naming conventions, and lifecycle handling manually. A native, workflow-managed temporary storage layer would make workflow development cleaner, reduce repetitive transformation logic, and simplify the overall implementation. Business ContextWe are using CDF workflows to populate an Asset Hierarchy data model.The source data comes from multiple systems:SAP Functional locations Equipment AVEVA PI Tag metadata The target asset hierarchy data model contains the following views:Site Area Line Equipment System Subsystem TagThe source metadata arrives without the required treatment, standardization, or contextualization. Before writing to the final data model, the data needs to be cleaned, normalized, enriched, and structured according to the target hierarchy.Current ChallengeIn practice, the workflow needs several intermediate transformation steps before writing to the final views.For example, the workflow may need to transform SAP functional locations into a cleaned and standardized structure before deriving sites, areas, and lines.Example flow for Site: tb_functionalLocation -> tb_functionalLocation_curated -> tb_site_curated -> Site view Example flow for Area: tb_functionalLocation -> tb_functionalLocation_curated -> tb_area_curated uses tb_site_curated for contextualization -> Area view Example flow for Line: tb_functionalLocation -> tb_functionalLocation_curated -> tb_line_curated uses tb_area_curated for contextualization -> Line view Example flow for Equipment: tb_equipment -> tb_equipment_curated -> tb_equipment_contextualized uses tb_line_curated / tb_area_curated for hierarchy mapping -> Equipment view Example flow for System and Subsystem: tb_functionalLocation + tb_equipment -> curated functional location and equipment tables -> tb_system_curated -> System view tb_functionalLocation + tb_equipment -> curated functional location and equipment tables -> tb_subsystem_curated -> Subsystem view Example flow for Tag: tb_tag -> tb_tag_curated -> tb_tag_contextualized uses equipment/system/subsystem curated data -> Tag view These intermediate curated tables are useful because they allow the workflow to:Reuse cleaning and standardization logic across multiple transformations. Avoid duplicating the same transformation logic in every step. Avoid using the final data model views as inputs to transformation logic. Keep the workflow logic easier to understand and maintain. Separate raw source data, intermediate workflow state, and final modeled data.However, this intermediate data can be transient. It is only needed while the workflow is running. After the workflow finishes successfully, the data can be deleted. There is also value to optionally allow users to view this intermediate datasets to analyze/debug the quality of the contextualization. Today, we can use RAW tables as intermediate storage, but this creates additional responsibilities for the customer:Creating and maintaining temporary RAW tables. Cleaning intermediate tables before or after each workflow run. Preventing stale intermediate data from being reused accidentally. Managing naming conventions for temporary workflow data. Adding cleanup steps to the workflow. Handling failed workflow runs where temporary data may be left behind. Writing additional code that is not part of the actual business transformation. Product IdeaIntroduce a native workflow-managed temporary storage capability in CDF.This could work as an internal temporary storage layer for workflows and transformations, where intermediate datasets can be written and read by different workflow steps, but their lifecycle is managed by the workflow execution itself.Ideally, this temporary storage would be:Scoped to a workflow or workflow run Usable by transformation steps Automatically cleaned up after successful execution, while still allowing end users to later review intermediate datasets for debugging. Temporarily retained for debugging and/or review Separated from RAW and from the final Data Modeling views Managed by CDF instead of customer-maintained cleanup logic Expected BenefitsThis capability would make workflow-based data modeling pipelines much cleaner and easier to maintain.The main benefits would be:Reduced amount of customer-managed code. Less duplication of transformation logic. Cleaner separation between raw data, temporary workflow state, and final modeled data. Reduced risk of stale intermediate data impacting future workflow runs. Easier debugging and monitoring of workflow execution. More straightforward workflow design for complex contextualization processes. Better support for multi-step data preparation before writing to Data Modeling views.
As I solution architect I would like to arrange persistently all my categories in my landing “Search page”, in a multilevel (tree) format, with minimal 2 levels, so the “Search page” is not convoluted/big and users still have access to all their categories with minimal clicks. As of today, I see that the only categories that allow multiple levels are the ones that were “inherited” from the old resource types, such as asset, files, time series, activity. Everything else added in the data model will be available view bullets.For PBF we have several data models within the same project, what causes the search page to be very extensive and not user friendly. As a workaround, we created a solution data model and configured a new location to expose a simplified “search page”, but for that we are omitting several of the categories that users would like to see. So if the user wants to access data that is not in this simplified view he/she needs to select the “full” location that has all the data, what is a bad user experience in terms of multiple clicks.. on the other hand if we keep everything exposed it is very hard to find a category and the search page gets convoluted. In the work around we implemented, user can still change location go from the “full” location to the “simplified” location, but it requires multiple clicks, what is not desirable. A better solution would be to allow multilevel configuration for categories (parent/child relationship), so we could groups categories that are related to each other. Also the data would be more organized and friendly from the user point of view. Note: The following it is just and example to show the desirable outcome for a “look & feel” in terms of arranging data, please ignore the “material” reference, once it is not relevant.- Material - Material Group - Material Type - Material Status
Example document from the pdf preview in fusion. There is a rotate symbol, but the rotate symbol does not rotate the image, but it resets the view to “fit to full page”. How do I rotate the documents previewed? or do i need to download it and do it an do it in a native app? And if not so, can rotation functionality in the document viewer? and maybe change to icon of the rotate symbol and also maybe remember the rotation of the page in the viewer aswell? cause there are often documents and diagrams combind in a single pdf file?
Hi all,The point is to get the possibility to enlarge the All Categories column in the Search. This should be useful if views names are too long to facilitate the navigation.
Example: The filter shows options in English, while in the list view they are displayed in Norwegian. For example, the filter shows “Ready”, whereas in the view it shows “Klar”.
When using the "scheduled calculation" function in Charts, there is a situation where you can select either "CDF sign-in credentials" or "CDF Client ID and Client secret" as the authority to perform the calculation. Of these, "CDF Client ID and Client secret" is supposed to be selected in order to perform "scheduled calculation" stably, but general users do not know "CDF Client ID and Client secret", so they cannot use it casually.Therefore, I would like to be able to perform "scheduled calculation" stably even if "CDF sign-in credentials" is used. In that case, there is no situation where you want to use "CDF Client ID and Client secret", so you don't need to select this permission in the first place, and I would like you to be able to perform all "scheduled calculation" with "CDF sign-in credentials".
Be able to copy the URL for a given checklist, template, etc. for sharing with a colleague.
Documents that are most important for the technician should be listed first, e.g. P&IDs (XB).
Wants the option to print a checklist with selected attributes from InField.
Atlas AI – agent building and chatbot notesThe GoodAble to switch between list and tile view as well as Search. Having a Description is helpful. Nice that there are sample questions. Loading feedback. Ability to stop generation. Legal disclaimer near prompt area. Nice that it shows reasoning steps. Like the suggestions with Show More Bot background color is fine. Reasonable area to write a prompt. Great to be able to view the details using the info icon of what each agent is good at before switching to it.Could be improvedPriority 1Starting a new chat is “risky” because there is no history, copy or chat download/export functionality. Part of the point is to aggregate information for analysis later, sharing or collaboration Chat history/multiple threads Need a way to set expectations up front so that when a new chat is started, we can orient users as to what can and cannot be done. Description helps but gets cut off. Sample questions as defaults are not injected but auto triggered. This can be an issue since the prompt is most likely not exactly what they want. Need some sort of prompt library so that users will be presented with prompts that have been vetted, and we are sure will produce relevant answers and get them quickly started. So not just examples but starter prompts. When it suggests follow ups, it would be great if these may be clicked and injected into the prompt area (but not auto submitted). Priority 2I would expect the naming for Atlas Agents to be in Industrial Tools and Agent Library to be in the Atlas AI. Ability to choose to share threads Edit icon should maybe use a plus. I know Copilot uses that but it’s still odd. Not sure what to do about location action and listing. What does this mean or how does it affect bot? Needs link to terms or docs. No file attachment. Users will probably want need this to override on a case by case basis. Publish / Unpublish flow is a bit awkward when prompt engineering between multiple people. Prompt area should be fixed to a certain height (perhaps one half the viewport) and scroll or be resizable. The use of a full takeover modal with a close button is odd when starting a chat. Switching to a new chat when moving between agents without a chat history is somewhat dangerous since users will lose all their work. It’s good that we can switch between agents while in a thread. However, I would expect that when I am in the agent library, clicking on another agent starts a new thread with that agent. Returning to the original agent would show my previous conversation with the agent. Cannot generate tables easily. Although I did manage to do so one time. I easily miss My Agents and Published tab. This causes a starter problem. Would like to add multiple tools at a time and not need to add them one by one.Possible bugsSeemed to lose past chats bubbles after a certain amount of conversation. Reloading shows them. Need to verify. Ran into an issue when switching between an agent within a thread created a new chat.
Simple Dashboard to display all the projects running in the organization - Project DashboardDetails of the projects when expanded
Hi Team,I would like to request for a new feature from Cognite to provide the hard delete options of instances in FDM.Currently, the instances are by default soft deleted and if the soft delete instances limit is reached, no further ingestion is allowed in the Project.Issues faced in the past - We have a shared Cognite Project, which is being used by multiple teams, and one team was in process of migrating their data from SQL to Cognite FDM. In the process, transformations run successfully but few data were corrupted. So, they deleted the entire FDM dataset and performed the transformation again. Meanwhile the soft delete instances limit was reached, making the ingestion failure for all the teams using that project.Here, the first team wants to hard delete the instances however, with no option currently available left them with no choices. And the similar incident has occurred again.Hence, we are requesting to provide a feature to perform hard delete of instances, considering the performing party holds the complete accountability of the activity.
When adding time series data to industrial canvas, providing the name of the tag and the description field in the time series tile window would clarify what tag is being shown. Submitted at the request of the Cognite project team.
I would like to submit a product idea regarding Charts calculations.Currently, calculations in Charts are performed only within the time range that is visible on the screen. We would like to request an enhancement that allows users to define a specific calculation period (i.e., start and end points) directly within the calculation formula.For example, when using the “sample average” operator, the result is calculated only based on the data currently displayed. As a result, the calculated value changes when the user scrolls or shifts the visible time range.We would like to be able to calculate metrics such as average values over a fixed, explicitly defined time range, including data outside of the current view. This would ensure that the result remains consistent and is not affected by scrolling or changes in the displayed window.We believe this functionality would significantly improve usability and enable more stable and meaningful analysis.Thank you for your consideration.
While working with a selection of time seies in canvas, I would like the ability to select a number of these to send to canvas in one action for further analysis. The way it works now I can send one time series to canvas and then have to search for the other time series i want to add to charts manually.
Currently, the search function starts only after entering a keyword and pressing Enter.Would it be possible to support incremental search, where results are updated dynamically as the user types?I believe that the “Data explorer” in Data Fusion (prior to the current Search feature) used incremental search.With incremental search, users can see results immediately, which makes it easier to try different keywords—especially for users who do not remember exact equipment names or file names. It also reduces the need to retype words.In addition, with the current behavior, there are cases where pressing Enter does not seamlessly trigger the search. In such situations, users need to click the search box again before pressing Enter, which can be slightly frustrating.On the other hand, I understand that incremental search may increase system load and could have performance implications. If introducing incremental search negatively impacts overall search performance, then the current implementation might be preferable.I would appreciate it if you could consider this as one piece of feedback.
When searching for assets or timeseries, there’s a feature in the detail tab that shows a list of Canvases where they’re used.↓Would it be possible to extend this to also show a list of Charts that use a given timeseries?Some example use cases:・Charts tend to be created in large numbers, so it’s sometimes hard to remember which Chart was used to create which visualization. Being able to trace Charts from a timeseries would make it much easier to reuse existing work.・Especially for scheduled calculation tags, it can be difficult to find the Chart where the original calculation logic is defined. It would be really helpful if we could trace back from the timeseries to the corresponding Chart to review the calculation.
Currently when plotting Work orders and Permit to work on Charts is difficult to see the difference. The colors are too close. It would be great to have different colors there to choose from or at least make more contrast on the default ones.
Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
