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
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 refresh mechanisms without requiring daily re-login.Suggested Improvement (Feature Request)Improve authentication/session management in Cognite Power BI connectors. Investigate support for: Persistent refresh tokens Extended session lifetime Seamless re-authentication (silent token renewal)
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.
All hosted extractors needs some kind of monitoring like extraction pipelines. This is supported for on-premise extractors and we don’t understand why this has been left out of the hosted extractors.We have requirements for monitoring all extractors and integrations we have in production, as I assume a lot of other companies does as well, but without monitoring hosted extractors are not an option at all. We simply can’t use them, it is unacceptable to skip monitoring.We would very much like to use them, but in their current state they’re a selling point for a powerpoint presentation with no real applicability. Markus PettersenAker BP - Techniacal Domain Architect for CDF
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 of the asset, this round trip can easily take 30 minutes or more.Allowing mobile users to attach the same file types supported by the desktop experience would enable them to fully document the Observation while standing at the asset, submit it immediately, and continue with their work.ValueEliminates unnecessary trips back to a workstation to complete Observation documentation. Saves valuable field time, with a single Observation potentially avoiding 30+ minutes of non-value-added travel and administrative effort. Improves adoption of Observations by reducing workflow friction for frontline workers. Increases the quality and completeness of Observations by enabling all relevant documentation to be attached at the point of work. Creates a consistent experience between desktop and mobile platforms. Improves collaboration and decision-making by ensuring engineers, planners, and supervisors have immediate access to supporting documentation.@Andrew Montgomery @Marius Biermann
The ability to attach a file with pictures or video of equipment in a checklist in INFIELD to complete a task. The Operators or Technicians will be able to see the equipment part that they need to check and what they need to check more easily.
It would be nice to insert additional default color pallet, based on the colors the company uses, as the first couple of default colors. and not just the default #RGB colors. just a place to push inn a list of HEX colors, and this then becomes the default color sequence for the user or the projects charts instance. But the color pallet should be changeable pr project basis, and that you could also have a custom color pallet aswell, based on user prefrernce. Additionally if we could also get a alpha / transparency factor aswell, that would be very nice :)
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.
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?
We would like the ability to rotate PDF displays.Scanned documents and documents containing charts often mix portrait and landscape orientations, forcing us to tilt our heads to view them properly. Could this be addressed on the product side?Other user companies facing the same issue, please vote!(Translated in Japanese below)PDFの表示の回転ができるようにしていただきたいです。スキャンされた文書や図表入りの文書が往々にして縦横混在のケースがあり、文書の閲覧時に首を傾けて確認しています。製品側でどうにかしていただけないでしょうか。同じような状況のユーザ企業さんvoteしてください！
With the use of Cognite Core Datamodel, we can create different types of Assets. Right now I have a case where I have EquipmentTag and Functional Locations.An EquipmentTag always has a FLOC a parent. So the Hierarchy is always:FLOC1-- FLOC1.1----EquipmentTagFLOC2--EquipmentTagIn this case, If I open the EquipmentTag, te UI is trying to get all the hirarchy as EquipmentTag, so the UI knows that exists a path, but can’t create the tree-view cause no data is returned. If I open the same EquipmentTag just as an Asset, the tree-view works fine, but then I lose all the specific data from my EquipmentTag.Openning as EquipmentTag
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
When multiple canvas are created in a company, then we need to get some more meta data on each Canvas to ease the search of the right/relevant Canvas.It could be interesting to get the option to insert a description of the Canvas, potentially the main discipline concerned by the Canvas and the main documents mentioned in the Canvas. So then we can develop AI agents to ease the search for Canvas.
Hi,I am using string Time Series to store machine state data (On/Off, Idle/Heating/Cooling) and want to be able to perform aggregations on these data via the API (specifically in Grafana). Obviously aggregations such as “sum” or “min/max” may not apply, but it would be great to perform aggregations for metrics like a count of how many times the machine entered each state over X time (e.g., cooling 5 times, heating 2 times), or what was the total time spent in each state over X time (e.g., cooling 3 hours, heating 5 minutes). There are probably other scenarios I haven’t described here as well.Thanks!
This request is coming from National Grid. BackgroundThe current behavior on Industrial Canvas is that only one person can edit at a time. This is very limiting when a team wants to do a collaborative (e.g: over a screen sharing session) troubleshooting, root cause analysis or QC of documents. RequirementAdd capability to support concurrent modifications to industrial canvas so that multiple users can work the same Canvas at the same time. Everyone who has write access to the industrial canvas should be able to edit simultaneously unless the Canvas is explicitly locked for editing by someone.
My team and I were utilizing Canvas during a hands-on session, with the expectation that everyone would be able to access the link and contribute simultaneously. Unfortunately, we encountered an issue, receiving the following error message:The inability to collaborate in real-time significantly limits the effectiveness of the tool, particularly for team-based activities. Real-time editing is a critical feature for fostering dynamic collaboration, and without it, the user experience is somewhat hindered.Is there any plan to introduce this functionality in the near future? Enabling simultaneous editing would greatly enhance Canvas’s collaborative potential, making it a much more powerful tool for teams working together.
Datasets have an “Access Control” page where you can see which groups have access.A similar feature is needed for Data Models / Spaces, so that we can quickly identify which groups have access.
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 concerns about relying on it as a core component of a workflow that supports critical daily inspection activities at a refinery. From the perspectives of stability and operational reliability, we believe there are limitations to using a preview feature for such business-critical operations.By implementing these capabilities directly within InField, dependence on external components could be reduced, leading to improved business continuity and greater operational stability.Furthermore, export functionality and approval workflows are commonly required features in inspection management systems used by Japanese companies and are generally available as standard features in many inspection applications. For this reason, we believe that providing these capabilities as native InField functionality would lower the barrier to adoption for Japanese companies and potentially contribute to broader adoption of InField within the Japanese market.We appreciate your consideration and look forward to your feedback.
Hello,We’re currently having some issues with pulling our PI data from Cognite since we have several PI tags that are string timseries vs numeric (as in rather than having 0 or 1, the timeseries shows open or closed). It appears that Cognite cannot handle string timeseries because they cannot be aggregated, however some of the logic that’s built in to our devices can only be pulled in this manner. We’d at least need a way for Cognite to convert the data pulled as strings as numeric and maybe auto assigning numeric values to each string event? A bonus would be to have an associated conversion of those numeric values to the associated string from the pullExample:Cognite pulls timseries EXAMPLE.TIME.VALVE.A.STATUS that contains “Open” and “Closed” and auto assigns 0 to “Open” and 1 to “Closed”There’s then an associated ‘conversion’ that states for timeseries EXAMPLE.TIME.VALVE.A.STATUS:0 = “Open”1 = “Closed” then Cognite pulls another timeseries EXAMPLE.TIME.VALVE.B.STATUS and happens to assign 0 to “Closed” and 1 to “Open” for whatever reasonThere’s then an associated ‘conversion’ that states for timeseries EXAMPLE.TIME.VALVE.B.STATUS:0 = “Closed”1 = “Open”
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
