Product Ideas

Hello Team,Although i have checked the documentation. I would be interested to understand if there is any discussion to generate charts programattically. this would help us Automate ESP surveillance for wells in one go.the idea is that once a well comes online it would automatically generate a ESP chart. 

This feature request is to add the ability for Charts to send notification alerts via mobile texts. Often times, manufacturing leadership would like to be alerted off-hours for major operational issues. Text messages have proven to be an excellent means of alerting key resources outside of normal working hours.

When creating calculations in CHARTS it would be VERY useful to have logic functions (AND, OR, NOT, XOR) which allow multiple (>6 for AND and OR) boolean inputs (TRUE/FALSE) and a single output.This would be really useful for tracking events which may be dependent on multiple conditions being active (or not active). 

Manual rotation of credentials is often time-consuming and leads to outages when done incorrectly. To make it simpler to automate, could Cognite add API endpoints dedicated to updating credentials?This is especially relevant for Cognite functions, which currently require sometimes lengthy redeployments to update secrets. When I ask GitHub Copilot about which API endpoints Cognite Toolkit invokes to update secrets and credentials used by a Cognite function, implementing this myself on top of the existing API seems very brittle.I think automating the rotation of credentials will be much simpler if it can be decoupled from other deployment processes.

We observed that search behavior differs between Asset Centric and Data Model.Asset Centric search provides more flexible matching and returns results based on relevance, allowing users to find assets using partial text. The Asset Centric View would performs a Fuzzy Search and returns results that are best match to the search text.However, in Data Model View we are required to input the exact text with correct spacing/hyphenation, prefixes etc. to get the results and does not perform fuzzy search.Users transitioning from Classic to Data Model have found difficult to work with the new search mechanism as they do not always key in the correct names or search queries. While we understand the Search mechanism from Classic cannot be implemented on Data Model we wanted to add a topic to see if we can have the Data Model search to more forgiving and user-friendly through partial matching, typo tolerance, relevance-based ranking or similar mechanisms.

Preference to use the term "time series" instead of "trend". 

Add SORA attribute from BMS. 

Add location codes as static information in the F.LOC view to inhance user experience.

Ability to create conditional tasks in InField. An example is shown below: If a user answers "Yes" to any of the items in the checklist below, new checklists (Category 1, 2, 3) should be generated.Norwegian: Ønsket er å kunne opprette conditional oppgaver i InField. Et eksempel er vist under. Hvis man svarer "Ja" på noen av punktene i sjekklisten under ønsker man å opprette nye sjekklister (Kategori 1, 2, 3) 

As an administrator of CDF in Aker BP I have a need to see all apps we have deployed, not necessarily accessing the apps, but knowing they exists. As a minimum this information should be available through the API. This is the information I’ve found in the Cognite Docs, I can do it per app from the app repo. But that requires that I already know it exists and that’s the heart of the issue, I don’t know all the apps that exists. If someone has deployed and published an app without activating it, then I have no way of knowing about it. Hiding non-activated apps from most users is a useful feature, but hiding it from the admins is a security breach. I am aware that tooling for managing this will come, but that does not remove the need for the information to be available through the API. There is still a need to export the information to data/app catalogues for the sake of governance. Markus PettersenAker BP - Data Platform Architect

As our main data model grows we are seeing a need for better management and navigation in the Fusion UIWe are doing what we can to “trick” the UI into behaving how we want. But we still run into limitations. Grouping the views by the Core Data Model (CDM), doesn’t really serve the purpose we need when the semantics of our views rarely match with the CDM setup. So grouping them by business meaning and relevance is something we see a great value in and would help our end users navigate the UI more easily.We have an “aggregate” model designed for the Fusion UI that contains all our views in one giant model allowing our users to see the full context of what we have in CDF. This model is invaluable to us. This model is also expected to grow with time. Because of this we also see the need to have some kind search/filtering for the views within a location filter as the number of views will force endless scrolling. Markus PettersenAker BP - Data Platform Architect

Ability to sort by multiple attributes simultaneously to improve usability. For example, sorting by area and f.loc. at the same time.Norwekgian: Kunne sortere på flere attributter samtidig for å skape brukervennlighet. F.eks. sortere på område og f.loc. samtidig.

Links from InField should open directly within the InField app instead of an external web browser.Norwegian: Når man åpner linker fra InField så vil man InField skal åpnes og ikke nettleser

We would like some way to give a CDF project an alias and also to set the order in which they are shown. The technical name of the CDF projects is not always what we would like to communicate with our end users, rather than telling them to use “abp” I could tell them to go to “Production”. Just more friendly to the less technical users we have more and more of.And our projects have a natural order that is not reflected by an alphabetical sorting.Here is an example from a Flows app showing what I mean: 

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