Community Discussions

When selecting the “File category view” for a CogniteFile extended View, the table width for the header is disconnected from the columns containing the values. Note that the Name width match the width of the “Manufacturing...” column (which is the category and not the name of the file), but is disconnected from the actual name column  

If I choose a different language than English under “Admin account->Language”, the Atlas conversation window is still in English 

Issue Summary – Cognite connection reliability (Power BI / CDF)We’ve had reports of a recurring problem when using Cognite connections in Power BI (Desktop and Service) where the authentication session does not persist.Problem DescriptionThe Cognite connection repeatedly logs out users unexpectedly. Users must re-authenticate frequently, often daily, using Aker BP credentials. This behavior occurs in both Power BI Desktop and Power BI Service. The issue is specific to Cognite connectors and does not occur with other integrations (e.g., Microsoft Fabric connections), which maintain stable sessions.ImpactDisrupts workflow and user experience due to repeated sign-ins. Reduces productivity, especially for users working with frequent or scheduled reports. Creates inconsistency compared to other data platform integrations.Expected BehaviorAuthentication sessions should persist for a reasonable duration, similar to other enterprise connectors. Ideally support long-lived sessions or token refr

Unfortunately, I cannot insert the approved table as a true table in Canvas using the currently available tools. The Canvas integration only supports data elements and chart/box structures, not tables, spreadsheets, or formatted notes.Any previous box-based table attempts should be removed manually. The table provided in the previous response is the complete and corrected source and can be copied directly into Excel or a Canvas table/note without losing the column layout.

Using Search, when selecting an instance and then choosing the Properties tab, all the populated properties are listed with the key and value in two columns. The key column is apparently a fixed width column (40ish char wide), not possible to manually resize, and it doesn’t resize when the browser window is resized. This becomes a problem when the property key is long, something that may happen when the property is a JSONObject such that the key becomes “nested” Below is an example of how it looks It seems like the UI is able to wrap the line if the key either has a space or a hyphen, but not else (have not tried all characters...) We can of course mitigate this by creating more compact keys, but it would be really helpful if we could resize the column such that our key naming convention do not have to take a 40 character UI limitation into account. 

ProblemField users commonly create Observations while working at the asset, but the mobile experience does not currently support the same file attachment capabilities already available in the desktop version of InField. As a result, users are unable to attach important supporting documentation, particularly PDFs, at the time the Observation is created.Many Observations require supporting documents such as P&IDs, equipment drawings, procedures, vendor documentation, inspection reports, and other asset-related files. While users may have these documents available on their mobile devices, they must often return to a desktop computer to complete the attachment process.PDFs are the most commonly requested file type, especially for P&IDs and other engineering documentation associated with the asset. Today, users often need to stop their field activities, walk back to an office or control room, locate a computer, open the Observation, and attach the document. Depending on the location

Search Experience ImprovementsWe would like to see the "Show More" expansion button removed from the Search experience.Today, as additional datasets are added, the interface progressively hides content behind the "Show More" control. This creates friction for users who must repeatedly click to access information that is already available. More importantly, users who are unaware that new datasets have been added may never discover them because they remain hidden by default.Instead, we recommend allowing the full list of datasets to be displayed in a scrollable view. If the number of datasets exceeds the available page space, users can simply scroll through the list rather than repeatedly expanding sections. This would improve discoverability, reduce clicks, and create a more intuitive search experience.Collapsed  Expanded​@Andrew Montgomery 

Currently when filtering with certain column on Cognite Industrial Tool Search we have options to filter byIs Equal to Is not Equal to Starts With Doesn’t start with Is set Is not setCan we please add another option “Contains”?This would significantly improve the ability to filter data and files on text-based fields such as Title and Description, enabling more flexible and effective search capabilities. 

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... 

The idea is to get a Search and Filtering options in the “Data Managament > 3D” tosearch something in the structure of the 3D model filter the nodes to display or not in the 3D model, this Filtering option should be possible with a “contain” option with multiple filters option. This should save the active filters to display the “cleaned” 3D CAD model in the Industrial tool domain. By this filetring we keep the original structure of the 3D CAD model and we can clean it for its display in the CDF

RequestTo improve business continuity and operational stability, we would like to request your consideration for developing official applications within InField that provide the following capabilities:An application that can export individual inspection forms in both CSV and PDF formats. An application that enables approval of individual inspection forms and allows users to view and track their approval status.BackgroundCurrently, we operate a workflow in which inspection results are entered through InField, exported using a Streamlit application, and then submitted for supervisor approval through another Streamlit application.Under normal circumstances, this workflow functions without major issues. However, due to a Streamlit application issue that occurred yesterday, the workflow became temporarily unavailable. To the best of our knowledge, this is the second occurrence of a similar issue this year.In addition, since Streamlit is currently provided as a preview feature, we have conce

 SummaryEnable aggregation operations (such as step_interpolation) on requests containing both numeric and string time series in the same SDK call.Currently, aggregation works correctly for numeric time series, but the request fails when a string/alphanumeric time series is included alongside numeric series. This limitation prevents users from retrieving synchronized operational datasets that combine process measurements and categorical/status information in a single query.Problem DescriptionWhen using the Cognite SDK method retrieve_dataframe() with aggregation enabled, requests containing mixed data types fail if at least one time series is of type string.Example:Numeric-only aggregation → works correctly Numeric + string aggregation → failsThe expected behavior for string time series using step_interpolation is to replicate the last known value across the aggregation interval, similar to how industrial historians such as PI System behave.Example Use CaseOperational dashboards and an

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. 

Documents that are most important for the technician should be listed first, e.g. P&IDs (XB). 

Hello Cognite team,First of all, thank you for your continuous development and improvements to CDF.I'd like to share one feature request based on our daily use of Charts and Canvas.Our use case In our long-term operation monitoring work, we create multiple Charts for different monitoring items and paste them onto a single Canvas, so that we can monitor many Charts together in one place.The issue The ability to select multiple Charts on Canvas and change their display period all at once is very convenient. However, when we open the same Canvas a month later and refresh to the latest data, the start time stays fixed at the point we originally set. As a result, the displayed time range keeps getting wider and wider over time, instead of showing a consistent window.What we'd like We would like a feature that lets us refresh Charts using the same fixed period — for example, a rolling window of the last 1 month, 3 months, or 1 year — so the time range stays consistent every time we open the

Hi team, I'd like to submit a feature request. Request In Charts, a line is only drawn up to the point where a value is registered in the time series. I'd like an option to draw a horizontal line from the last value up to the current time (NOW). This is especially an issue in calculations. When a formula uses multiple time series that are registered in CDF at different times, the series that ends earlier is plotted only up to its last value, so the calculation result is cut off there. I'd like to avoid this. ExampleGiven two time series Ts_long (up to today) and Ts_short (up to 2025/04/01), using them as calculation sources pulls the output toward the Ts_short time axis, so nothing is displayed after 2025/04/01.Reference テスト Copy（工務 久保田） | Cognite Data FusionCognite Hub

Allow Custom Symbols for Dataset CategoriesWe would like the ability to assign custom icons or symbols to datasets rather than using the standard black dot that is displayed today.Allowing unique symbols would help users quickly distinguish between dataset types, sources, or business contexts, making the search results easier to scan and navigate. This would improve usability, particularly in environments with a large number of datasets.Expected BenefitsImproved discovery of newly added datasets Reduced user clicks and navigation friction Better visibility into available search content Faster identification of datasets through visual differentiation Improved overall search usability and adoptionThis enhancement would make the search experience more visually intuitive for end users. ​@Andrew Montgomery 

To keep clean structure in Charts monitoring jobs.

The current Cognite Grafana Plugin supports Time Series, Activities, and GraphQL-based queries, but does not provide native access to Records and Streams.As Records and Streams become increasingly important for data ingestion and operational use cases, native support within the Grafana Plugin would enable a more complete and consistent visualization experience directly in Grafana.Requested enhancement:Native querying of Records and Streams from the Grafana PluginSupport for filtering and visualization of Records dataIntegration with Grafana panels and dashboards without requiring intermediary services or custom pluginsThis enhancement would simplify data consumption, reduce implementation complexity, and improve the usability of Records and Streams across operational monitoring and reporting scenarios.

Hi Team,In regards to Cognite Data Model UI we understand that the below features are currently not supported and would like to add them here as a Product Idea requests -Reorder the Sequence of the Views listed in Cognite Data Model UI. For example, Under "Assets" category we have 1) Piping Tag 2) SAP Assets. We would want the "SAP Assets" View to come first followed by the "Piping Tag" View. This would make easier for end users by having important and frequently visited views on top. Also, would reduce the number of clicks a users has to make to get the the required data - for example in Canvas when we want to "Add Data", the default category is set to "Piping Tag" and user has to switch to "SAP Assets" to get to the right view.   Option to HIDE some of the views from the Data model UI main/home/landing page. Most of the Views need not be accessible from the Data Model main page and can be accessed through relationships. For example - Under "Activities" category we currently have 11

Hi team,I'm a Cognite Data Fusion (CDF) user, and I'd like to submit a feature request regarding scheduled calculations in Charts that write results to a time series tag.Current behavior (as I understand it) When you set up a scheduled calculation in Charts to store results as a time series, the calculation only runs from the point the schedule is configured onward. It does not compute results for any period before the setup time. I confirmed this behavior in the following Hub post: 🔗 Cognite HubWhat I'd like to see I'd love an option to backfill / calculate historical data retroactively, so that the scheduled calculation can also produce results for the period before the calculation was created.Why this matters With this capability, we would be able to go back and review historical data as well, not just data going forward. This would be very valuable for our long-term monitoring and trend analysis, where being able to look back over past periods is essential.Thank you very much for

**Component**: OPC-UA extractor · `EUInformation` handling **Current behaviour** (confirmed by Cognite): the extractor never reads `NamespaceUri` or`UnitId` from `EUInformation`. The only value that reaches any config surface is thecomposed `DisplayName: Description` string. The UNECE code is dropped before`metadata-mapping` can see it, so `unit` / `unitExternalId` resolution to a`CogniteUnit` from the source unit is impossible today and is not planned. **Request**: carry `UnitId` through, and resolve the CDF `unit` direct relation from it. **Why it matters to us**: across our fleet the `unit` direct relation is populated on**0 of 2772** time series, while 528 of 854 at one line carry the composed string in`sourceUnit`. The only path available is post-processing that string-matches against theCDF unit catalogue. That is brittle in exactly the way a code-keyed lookup is not —`kW·h: kilowatt hour` has to be parsed and matched by display text, and it will differby server locale, by punctu

Recently, the use of Charts has been increasing, and more users are creating complex calculations for data visualization.In this context, we have received feedback requesting a “Back” button (undo function).When users are building complex calculation formulas, there have been multiple instances where the calculation source suddenly disappears, forcing them to restart from scratch. The more complex the calculation, the greater the impact of this issue.To mitigate this, it would be extremely helpful to have a function that allows users to go back one step (e.g., an undo or back button).We believe this feature would significantly improve usability and reduce the risk of losing work during calculation editing. Thank you for your consideration.

Hi there, We would like to be able to annotate instances that do not extend CogniteAsset, nor CogniteFile and visualize that in “Preview” in Search UI. Our context is purely data modeling.So we would like to have a view, that extends CogniteDescriable and to be able to annotate it towards a CogniteFile.Currently we are achieving partically that, by having an edge, (pseudo code below) ANNOTATION_TYPE = "diagrams.InstanceLink" type_node = NodeApply(space=REFERENCE_SPACE, external_id=ANNOTATION_TYPE)edge = EdgeApply( space=EDGE_INSTANCE_SPACE, external_id="annotation_<file_ext_id>__<entity_ext_id>", type=DirectRelationReference(space=REFERENCE_SPACE, external_id=ANNOTATION_TYPE), start_node=DirectRelationReference(space=FILE_SPACE, external_id=FILE_EXTERNAL_ID), end_node=DirectRelationReference(space=ENTITY_SPACE, external_id=ENTITY_EXTERNAL_ID), sources=[ NodeOrEdgeData( source=ViewId("cdf_cdm", "CogniteDiagramAnnotation", "v1"),

So, when I get documents to populate in canvas, it drops them off in an unorganized bundle. I tried to get ATLAS to organize them in a timeline but ATLAS states “I can add documents to the current canvas, but I cannot move or rearrange existing canvas elements with the available tools. Please drag the four cards into this left-to-right order:”. Is an update that can make it easier to organized documents in canvas. It gets very cluttered and time consuming to organize these documents when you have like 20-30 documents populating on canvas.