Community Discussions

 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

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

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.  

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

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 perfo

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 implementat

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.

Hi!The Q2 Product Release describes the new Atlas Skills feature as “reusable, lifecycle-managed assets”. In my experience the current designmakes skills very hard to reuse makes it impossible to manage their lifecycleReusing skillsTo reuse skills means to me that I can add skills to my agents that have been authored by someone else for another use case. The agent builder in CDF lets me add new skills in two different ways:Search among the skills already added to the agent Upload a skill markdown fileSo the only way to reuse a skill is to download a skill from another agent and re-upload it to my agent? There is no lifecycle management here. Skill versions will become stale very quickly. You have no idea whether your skill is up to date or not.There is no repository of skills where I can search for something relevant to me. I have no idea what skills have already been created. There is no way to inspect a skill once it has been added to my agent (I need to download it locally). Is ther

SummaryThe Cognite Toolkit forces an agent to be defined as a single monolithic YAML file — config (name, id, description, LLM), instructions, the skills list (external IDs to pre-existing skills), and tools (including inline Python source) all in one file. We need a modular, file-structure-based agent definition that the toolkit parses at deploy time, so skills and Python tools can live as standalone, testable, version-controlled source files that are created and attached to the agent automatically on deploy. Pain pointsThe monolithic YAML blocks normal DevOps practice (isolation, unit tests, review, reuse). Concretely:Skills cannot be deployed from source. A skill should be an isolated directory containing a SKILL.md (possibly other supporting files as well, as per the emerging standard). But the toolkit references a skill only by external ID — the skill must already exist in CDF. There is no way to point the toolkit at a SKILL.md and have it create and attach the skill on the fly du

Today an Atlas AI agent (and Flow app) uses my personal access rights when accessing CDF. However, we see the need for being able to further restrict this. One example is: I have write access, but I do not want my Agent to have the same write access. This issue is currently not solvable by using a separate service principal for the Agent, since different users will have different read access, so I cannot have one Agent with a fixed set of access rights. What would work is to be able to grant the agent certain (maximum) access rights, and then the final access rights are the minimum of the agents and mine access rights.This becomes increasingly important when the capabilities of the (reasoning) agents are growing. We need to be able to provide additional (and strict) guardrails

With the data modelling framework, most models will end up with a significant number of Views. Today we are not able to control the order the Views are presented in a good way. By reverse engineering it seems like the order of the Views is based on The order of the (first mentioned) CDM extension in the model definition. Alle non-CDM Views are listed at the end, irrespectively whether it is listed before CDM or not  What is considered a CDM extension by the UI is not based on the implements, but whether it reference at least one property from one of the CDM containers Inside each Category (eg, a specific CDM extension, or the non-CDM Views), the order in the model definition dictates the orderIf I choose alphabetic sorting it seems to only affect the non-CDM-Views, and not the order inside each CDM category. It do however put all the CDM categories first or last It is very inconvenient to use the order of appearance in the model definition as the way of sorting (we have to sort both th

We need the ability to download all items to a csv in search.  In the downloaded CSV there should be a column for a hyperlink back to the item, as if you clicked the open button in search. Additionally, if the items is a file create a download hyperlink.  

The Smart KPI Tracking System is a data-driven performance management platform designed to enable real-time monitoring, analysis, and predictive insights across critical business and operational KPIs. The project aims to move organizations from traditional static reporting to a proactive, intelligent, and automated decision-support system.This solution integrates data from multiple enterprise systems (e.g., SAP PM, asset management tools, scheduling platforms, and financial systems) to provide a unified and dynamic view of performance across projects, maintenance operations, and asset reliability.

As described in the referenced link（Cognite Hub）, we create a Canvas once a month to monitor long-term trends of key operational parameters.Since this activity is performed monthly, we are facing challenges in how to properly store and manage these Canvases over time.Currently, Canvases can be organized by site. However, if further granularity were available—such as hierarchical folder structures—it would significantly improve:Management of the latest Canvas Searchability of past Canvases Overall organization and maintainabilityAt present, we are supplementing this limitation by using a custom application built with Streamlit, as shown in the attached example. This allows us to further classify Canvases beyond site level, down to individual units. Ideally, we would like to have this functionality natively available in Canvas.Although this request is not highly urgent, we would appreciate your awareness and consideration for future improvements.

We create a Canvas like the attached example once a month to monitor long-term trends of key operational parameters.Previously, this work was done using Excel, but we have recently migrated to Charts and Canvas.As we move toward full-scale operational use, we would appreciate your support in resolving the following two challenges.These improvements are critical for reducing operational workload and enabling sustainable use of Canvas for monthly monitoring.Request ①We previously requested a permission transfer feature for Charts. However, it is currently difficult to locate individual Charts from within Canvas.Cognite HubTherefore, we would like to request the following enhancement:Ability to select Charts directly within Canvas and transfer their ownership/permissions in bulkWithout this capability, when the responsible person changes, users must first locate all relevant Charts individually and then manually duplicate them one by one. This process is time-consuming and creates a signi

As part of driving internal platform adoption, we are requesting the ability to add custom "Help and resources" links through the Admin --> Project Settings options. This would be a new admin option to create new links to both internal/external URLs where we would like to route our users.For instance, we have an internal ticket/incident form, a custom Cognite portal, etc. where we would like to provide users the ability to find/link to from the Cognite platform.

Add option for setting dark mode in the InField application. Both for desktop and handheld units.

In our company, area codes (Which signifies which area an asset/functional location is placed in) is a central property that users want to see immediately when opening tag detail view. Area codes are available in the properties section but users want to have this visible in the header, to not have to scroll down. This is more helpful on the handheld unit as less information is visible upon opening the screen and the user needs to scroll further down to see the relevant information. Example of where to add location code is shown below. To make it more generetic, users could be able to add relevant info in the header themselves as maybe other companies/user groups have different interest in what they want to show in the header.

Problem StatementThe Cognite DB Extractor currently requires space to be a static, query-level configuration parameter, forcing users to create multiple identical extraction queries when distributing data across spaces based on hierarchical entity relationships.When working with hierarchical data structures, each distinct parent entity requires a separate extraction query, even if the source data and transformations are identical.Asset hierarchy:L1: Assets  L2: Area L3: Field (defines CDF space) L4: Installation L5: WellCurrently, if there are 10 distinct fields across multiple assets, the DB Extractor requires 10 separate extraction queries to distribute timeseries data across 10 spaces - one query per field, even though they all read from the same source table with identical transformations. With multiple assets, areas, and fields, this results in hundreds of extraction queries for a single source table. This creates:Configuration Bloat: Hundreds of nearly identical YAML configuratio

In Canvas, it is possible to configure rules for objects, but as far as I understand, the current setup allows only one trigger per rule (1 rule = 1 trigger).However, in practical use cases, there are often situations where we would like to define a rule using multiple trigger conditions (AND conditions). For example, when producing multiple product types on the same production line, the normal operating ranges for parameters such as temperature and flow rate may vary depending on the product.In such cases, we would like to configure rules like the following:When producing product A, it is considered abnormal if temperature or flow rate exceeds threshold α.When producing product B, it is considered abnormal if temperature or flow rate exceeds threshold β.To support these kinds of scenarios, it would be very helpful if we could configure multiple triggers within a single rule.Alternatively, if there is an existing way to achieve this functionality using current features, I would greatly

Would it be possible to provide a way to visualize trending content that is frequently viewed and utilized among those created using Charts, Canvas, and Streamlit?At present, even if someone creates an excellent Canvas or similar content, it does not easily spread to other users. However, if there were something like a trending ranking, high-quality content could naturally gain visibility and adoption. It could also serve as a helpful source of ideas for practical use cases.