Community Discussions

Hi Cognite Community,We are looking at ingesting approximately 1 million engineering and operational documents into CDF, including equipment manuals, datasheets, inspection reports, SIL/HAZOP studies, operating procedures, technical studies, maintenance reports, and other asset-related documents.Our key requirement is for an Atlas AI agent to answer questions across this entire document repository without the user having to identify or pinpoint a specific document first.For example, a user should be able to ask:“What are the recurring compressor seal issues reported across our engineering and operational documents?”The user may not know which documents contain the relevant information. We therefore expect Atlas AI to discover the appropriate documents/passages, retrieve the relevant content, and generate a grounded response with references to the source documents.According to Cognite's documentation, CDF Semantic Search does create vector embeddings for PDF documents as part of the bui

Hi Cognite Community,We have a requirement for CDF Charts to dynamically use configured tag limit attributes as chart thresholds, rather than requiring users to manually enter static threshold values on an ad-hoc basis.For industrial tags/time series, we maintain multiple engineering and operational limits, for example:High / High-High limits Low / Low-Low limits Operating upper and lower limits Design limits Alarm limits Safe operating limits Other tag-specific engineering thresholdscurrently supports configuring thresholds for time-series analysis and monitoring. However, we would like these thresholds to be dynamically sourced from the contextualized attributes associated with the tag/time series, rather than manually entering a value each time a chart is created.Expected capabilityFor example, if a pressure tag has contextualized attributes such as:High: 80 bar High-High: 90 bar Low: 30 bar Low-Low: 20 bar Design Pressure: 100 barWhen the user adds that time series to a CDF Chart,

Hi Cognite Community,We have a requirement to extend the CDF 3D experience beyond displaying attributes from the Core Data Model, so that users can visualize related transactional and operational information as configurable layers directly on the 3D model.Our industrial knowledge graph connects equipment and functional locations to multiple types of information, for example:SAP Notifications and Work Orders Maintenance Plans Inspection findings Reliability events / Bad Actors RCA and TFN records MOC records Alarms and operational events Engineering and operational documents Time-series conditions and calculated KPIsThe Cognite Core Data Model provides standardized industrial concepts and can be extended through additional models and relationships. [docs.cognite.com], [docs.cognite.com]However, we would like the 3D visualization to make greater use of these contextual relationships, rather than limiting the user experience primarily to the attributes directly associated with the core 3D

Hi Cognite Community,We have a requirement to provide configuration control over how data model objects are organized and presented in CDF Search and the Details view.As our industrial knowledge graph grows, an asset or equipment can be connected to many different object types, such as:Functional Location → Equipment → Time Series → Notifications → Work Orders → Maintenance Plans → Documents → Engineering Studies → MOCCDF already allows users to search and navigate connected resources. Data explorer - Cognite Docs However, for a large enterprise data model, the sequence in which these related objects are presented becomes important for usability and business context.We would like the ability for an administrator/data model owner to configure: Search pane object ordering Define which object types appear first and in what sequence. Details view tab ordering Configure the sequence of related-object tabs when a user opens an Asset, Equipment, Functional Location, or another object. Sho

In Flows (Search and Charts), a Data Modeling time series shows up under the Default categories (Classic data model time series) by default. When selected in Search it appears with incomplete metadata (including an empty External ID) and cannot be added to a chart (“You can only add time series with external IDs to a chart”), even though the underlying time series does have an external ID.The same time series can also be found under Other categories, where it works as expected: the External ID is shown and the time series can be plotted.The confusing part is that users are presented with the non-working version by default, and there is no obvious indication that they should instead select the time series from another category. Since both entries appear to represent the same time series, I would consider this a UI bug or an inconsistency between how Classic and SDM time series are surfaced in Search & Charts.  

Hello Team, I have created interactive diagram in my project and its working fine, showing all related assets and timeseries associated with each part on diagram. But all this happening on cognite data fusion environment.My query is, how can we bring this diagram to POWER BI dashboard or Cognite Flows App. Is there any way to do this? or its not possible? ThanksRupali  

Today October 15, 2026 we're announcing the deprecation of the classic asset-centric services in Cognite Data Fusion. They will be fully retired on December 31, 2027. The full list of affected services, and the details for each, is in our official deprecation notice.Many of you have already made the move to Data Modeling and the Core Data Model (CDM). Since late 2024 we've recommended that every new project start on CDM, and all of our new product development has gone into Data Modeling. This announcement completes that shift. Running two parallel architectures slows us down. Focusing on one lets us put all our effort into the foundation that gives you the most value.We know an upgrade takes real work, so we want to be clear about two things: why it's worth it, and what we've done to make it as smooth as possible.Why Data ModelingDescribe your operations in your own language - The classic APIs gave every customer the same fixed shapes: assets, events, time series, files. Data Modeling

 What a quarter! With Q3 2026 is in the books, let’s take a moment to recognize the people who keep the Cognite Hub thriving: our outstanding community members. Our Top 3 Contributors for the past quarter have gone above and beyond to help their peers, share hard-won knowledge, and spark new ideas across the Hub:🥇 ​@Kubota Mami  – Cosmo Oil Co., Ltd.🥈 ​@Christophe ALLANIC  – TotalEnergies🥉 ​@Shun Takase  – Nippon ShokubaiThank you for sharing your expertise and ideas, for helping others move forward, and for showing us better ways to get things done. 💙👀 And now, a little something to look forward to...Later this October, we’ll announce our Cognite MVPs for 2026. These are the community members whose experience, insights, and honest feedback help their peers succeed and shape where Cognite goes next.New this year: in addition to public recognition, our MVPs will receive exclusive MVP swag, made just for them. 🎁Stay tuned!👇 In the meantime, drop a comment below to help us congratu

We’re reviewing how to ingest data from external REST APIs into CDF RAW and would like to hear how other teams choose between the hosted REST extractor and a Cognite Function.My starting point is the hosted REST extractor when the source can be handled with scheduled requests, pagination, incremental load, and mappings. A Function becomes attractive when the integration needs more complex request sequences or Python logic. But then our team also owns the extraction state, retries, recovery, and monitoring.I’m particularly interested in how you make this decision when: The source API requires calls to multiple endpoints or hosts, or data from several responses must be combined before writing a RAW row. A large initial load cannot finish in one Function execution. The source uses a change timestamp or cursor, and a run can fail after writing some rows but before completing the batch. You need to replay a date range without losing later changes. Authentication or network access ma

We’re designing a layered data model in Cognite Data Fusion and would like to hear how other teams handle the boundary between enterprise and solution models.Our current approach is: Enterprise layer: Create domain views that use implements: to extend relevant CDM or IDM views, with enterprise-owned containers for our domain properties. Solution layer: Create application-specific views that map properties directly from enterprise containers, instead of implementing enterprise views. The intent is to let each solution shape its own consumption interface while reusing the underlying data. We’re considering enterprise containers as the longer-lived storage contract and views as versioned interfaces for different consumers. Cognite’s guide to designing scalable data models appears to support direct container mappings for solution views.For teams using this pattern in production: Do your solution views map directly to enterprise containers, implement enterprise views, or use a mix? What d

Hello! I have got a new phone and am not able set up the authenticator app again.Could you please help with the set up.Thanks,Rahul

Hello everyone,  I am in the transformation part in the Cognite Fusion Data Fundamentals Part 2 - Hands-on. I ran a transmation as asked but it doesn´´t appear in the filter