Tell us what features you’d like to see and support other ideas by upvoting them! Share your ideas in a user story format like: As a ˂role˃, I want to ˂function˃, so that ˂benefit˃. This will help us better understand your requirements and increase the chance of others voting for your request.
Currently, the Japanese translation for the operator used to perform exponentiation in Charts is shown as 「電源」, but this makes it difficult to understand at a glance what the function actually does.Would it be possible to correct this to a more appropriate translation? It’s a minor detail, but since this is a function that is used fairly often, I would really appreciate it if you could consider reviewing the translation.
In Charts, it’s possible to freely configure the units for each time series.However, I’m having trouble when trying to merge a manually set unit with the default unit.For example, in the screenshot, the upper time series is a calculated value added using “Create calculation.” I manually set its unit to “°C,” and attempted to merge it with the lower time series using “Merge unit.”But Charts recognizes them as different units, so the merge doesn’t work properly. To work around this, I have to manually reassign the unit “°C” to the lower time series—even though it already has the correct unit. This is quite time-consuming.If I'm doing something wrong, I would really appreciate it if you could point it out.If this behavior is actually by design, I hope it can be improved in the future.
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 the CDM extension, and then inside each category) since any change in the order will require pushing a new model definition to CDF.We need the ability to define the order it appears in the UI, independent of how it is listed in the model definition, and we need to be able to create groupings that do not follow the CDM extensions. Eg, we have maintenance information that are not a CogniteActivity extension, that we still want to group next to the other CogniteActivity extended maintenance information.The CDM based grouping is more relevant from a model developer point of view, and not that much from an end user point of view.We also need the ability to define what is the default View. Right now it seems to be the first View in the model definition that is a CogniteAsset extension.When changing location filer, it always reset to the (non-configurable) default, which we see create a lot of initial confusion with the users. Since the CDM Views are not explicitly described in our model, we do not see the CDM based grouping.
When manipulating the chart, like zooming/translating, or just moving the pointer to the chart are such that the slider appears, or select/unselect the browser, it triggers a refresh of the data in the “Explore and select your data” window. If you have zoomed in on a file, or searched and filtered on properties, everything gets reset. It seems unnecessary to refresh the data on the “Explore and select your data” window every time I touch the chart, and it makes it impossible to move back and forth when investigating a P&ID
The OPCUA extractor can only write time series instances to a single target space per deployment, even when the underlying OPCUA server contains data from different sources, governance domains or folders which should be handled individually. The only practical workaround is to run many OPCUA extractor instances against the same OPCUA server/hub, each with different tag filters and a different target space, which is hard to scale and operate. [Governance & spaces; Multi-space limitation]I would like the OPCUA extractor to support multiple target spaces from a single deployment, where the space is selected per time series based on configurable filters. Typical examples would be routing by tag name prefix or pattern (for example, ABB* to space site-abb, VAL* to space site-val), or by attributes / metadata / folder structure mapped to specific spaces. [Filter-based routing idea; Enterprise scaling concern]. This capability would avoid both the operational overhead of many parallel extractor instances.This is strongly related to the need of the same functionality for PI Cognite Hub
When selecting an instance in Search, the Overview tab is very useful (seeing more than one data category without having to switch view). The challenge today is that the tiles have pre-defined columns, and they do not allow for filtering. It is of course possible to go into the “full screen mode” for each category, like Activities, but then you loose the possibility of seeing data from more categories in context.It would be very useful to be able to configure the properties we see in each tile and to filter on properties, like we can do in the “full screen mode”.
When selecting an instance in Search, the Overview tab is very useful (seeing more than one data category without having to switch view). However, the tiles are static and cannot be resized. Resizing would allow the user to see more of the data in one category while still see the other data categories (eg I want to see more of the properties from the Asset while still seeing the list of workorders.For the same reason we would like to be able to change the order of the tiles, eg moving the workorder tile up next to the properties tile, to better focus on the things we want to see.The same behavior is also relevant when searching for data via Charts and Canvas
When selecting the property that will be used for the x-axis in the graph, the list is not searchable. For more complex Views the list of properties can be long (100+), which makes a non-searchable non-sorted list relatively hard to work with
When clicking “+Add data” and “Add time series”, you can search for other data types, like assets. However, if you try to follow links, like parent of child asset, you are kicked out of Charts and pushed over to full Search. This means it is impossible to use the asset hierarchy to locate relevant timeseries. Similar issues are seen if you use the files (like P&ID) to enter the asset (to find the timeseries) The test was done one a CDM based data model
I'm seeking help and guidance from customers who have tackled or enabled features to improve the LINES when connecting files and assets within Cognite Canvas.We seek to have our connected lines more accurately flow and follow P&IDs as they are added to the canvas. Making the lines conform and adjust vs. extending across the visuals on the canvas.This means these lines should follow the “path” on the connected P&ID where they begin on the document vs. connecting randomly into the side of the document.
Recently a change was implemented to make the connection lines between documents on a Canvas to be orthagonal and to combine and flow between documents.There are some Canvases where I would like to be able to see a direct straight line connection between my references to quickly locate interconnectivity.My product idea: add a toggle to allow me to choose between orthagonal connectors or straight line direct connector.
Current BehaviorIn the transition from InField 1.0 to InField 2.0, PDF rendering on mobile devices shifted from utilizing the device's native viewer to rendering in-app using the Unified File Viewer. Native viewers are written in native code (C/C++) and render directly to the GPU meaning that they can stream pages and down-sample large images on the fly without memory constraints. But this change, while necessary to support advanced interactive features, subjects the viewer to strict memory limits enforced by mobile browsers (e.g., iOS Safari, for example, caps total canvas pixels at ~16.7 million.). Consequently, when a user attempts to open a highly complex or large document that exceeds this safe mobile rendering threshold, the browser fails without providing any notification or context to the user.Proposed SolutionImplement a clear warning prompt within the Unified File Viewer when a document’s size exceeds the safe mobile rendering limit. A notification such as, "Document size too large for mobile, please use desktop," should be displayed to the user instead of the application failing silently.ValueThis enhancement will significantly improve the user experience by setting appropriate expectations and providing actionable guidance when mobile browser limitations prevent document viewing.
In Charts and Canvas and Streamlit, items created for quick checks or simple testing (which are not valuable and can be deleted without issue) are listed together with highly valuable items used in daily operations (which would cause problems if deleted).Although only the creator can delete their own items, as CDF usage grows and more Charts and Canvas assets are created, the risk of accidentally deleting important items increases.To prevent this, could we have an optional deletion lock feature for Charts and Canvas and Streamlit?When the lock is enabled, the item cannot be deleted; once the lock is manually removed, deletion becomes possible again.This would help protect important items from accidental removal.
When creating calculations, the four basic arithmetic operations are some of the most frequently used features. However, in the current Charts experience, creating even slightly complex expressions requires configuring a large number of Functions.For example, the Add Function can only add two time series at a time, so even for a simple expression like A + B + C + D + E, you need to place four separate Add Functions.Could this process be made simpler so that basic arithmetic can be built more easily?Ideally, it would be great if users could enter an expression directly on the “Create calculation” screen—for example:A + (B - C) / (B + C) * 100 + D × Eand Charts would automatically generate the necessary Functions.If the expression format followed something similar to Excel, most users would find it intuitive and easy to use.
Can we add the ability to use Wildcards like “*” in search terms? Our users say SAP and Oracle allow them to use wildcards, so Cognite should as well.
In the checklist section of InField it is a need to be able to sort on functional location attributes. If we first are able to choose which attribute to sort on, and afterwards if it is in rising or falling order it would be really helpful! A specific use case for this is to sort on location/area. Then the user are able to see all f.loc that is in the area that he currently is working in.
There is a need to create a check list based on a list of functional location copied from an external source (Such as an excel sheet) or manually typing in. The functionality makes it easy for technicians wanting to create checklists based on a list of functional location from mail or other list to make tag data/work orders and 3D model available in the field. Using templates for this is not a viable option since these are one-off needs (Check list is only needed once). This functionality has been available in earlier versions of our InField which can be used for reference.
Sylvamo users are looking to avoid scrolling with the trackpad, essentially. When navigating the Chart, the idea is: Buttons that allow users to scroll through the time series (see screenshot below). These buttons could dynamically scroll either large chunks of time or relatively small ones, depending on how quickly the user was clicking them. End users are using Dell, Lenovo etc. laptops
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK