Skip to main content

Product Ideas Pipeline

Filter by Idea Status

Filter by Topic

1256 Ideas

J
Practitioner ⭐️
Jesse JenkenPractitioner ⭐️

Hosted Event Hub Extractor Triage / Routing to Different DatasetsClosed

Posted for inquiry here: Cognite Hub but I don’t believe the feature exists currently. We need a way of routing time_series and datapoint items from within a Hosted Extractor configuration to different, or possibly multiple datasets. Question copied from referenced posting here, for product feature descriptiveness: Within our implementation we have an existing Hosted Extractor reading data from an IoT Hub that contains multiple sites worth of data. Our Hosted Extractor Mapping Template filters for events that have a particular deviceId on it, representative of the location these events are coming from. In effort of ingesting another site-location datafeed, I wanted to extend the template with an ELSE IF condition that has the mapping rules for the other location, which are almost identical to the first except for the target datasets, which I’ve come to realize is set in the Sink section of the Extractor Configuration. The net result here is needing to create redundant Hosted Extractor configurations that change only a filter, rather than having a cascading ELSE IF ruleset that applies to the full stream. For example, this pseudo-template for our existing hosted extractor configuration for one site: if (context.messageAnnotations.`iothub-connection-device-id` == "SITE_A") { input.map(record_unpack => { "type": "raw_row", "table": "tb_iot_test", "database": "db_iot_testing", "key": concat("TS_CO_", record_unpack.NAME), "deviceId": context.messageAnnotations.`iothub-connection-device-id`, "TAG":record_unpack.NAME, "IP_INPUT_VALUE":record_unpack.IP_INPUT_VALUE, "IP_INPUT_TIME":record_unpack.IP_INPUT_TIME, "IP_INPUT_QUALITY":record_unpack.IP_INPUT_QUALITY }).filter(item => item.IP_INPUT_QUALITY == "Good").flatmap( item => [ { "type": "time_series", "name": item.TAG, "externalId": item.key, "metadata": { "IP21_DEVICE_ID": item.deviceId }, "isString": false, "isStep": false }, { "type": "datapoint", "externalId": item.key, "value": try_float(trim_whitespace(item.IP_INPUT_VALUE), null), "timestamp": to_unix_timestamp(item.IP_INPUT_TIME,"%Y-%m-%dT%H:%M:%S.%6fZ"), } ] ) } else { [] } Ideally I want to add an ELSE IF condition where the only change to the outcome is the iothub-connection-device-id equals SITE_B in this case. While the record_unpack step is able to route different locations to different staging tables, I was unable to find a means to specify an alternative target to route the time_series and datapoint items in the outside of creating a whole new configuration and having a different Sink setting for this extractor.  We have multiple sites all sharing one IoT Hub. IoT Hub has a limit to the number of consumers that can be connected, in this case larger than our number of sites. We handle routing in the Consumer logic of this stream however Cognite appears not to provide us with this mechanism in the templating language, instead specifying it in the sink.  This presents a configuration-limit issue for us with respect to our source data, and the constraints presented by the Cognite Hosted Extractor with specifying the target.  Am I missing something and is there a way to achieve what we’re looking for, or will this require a secondary hosted extractor configuration to be implemented? If we must go down the path of redundant hosted extractors with modified logic and a different Sink, we’re going to hit an Azure IoT limit prior to our full scale out, and would like to understand if this is a feature that can be provided, or if we should be planning otherwise.

1
T
Forum|Forum|9 months ago
S
Committed ⭐️
Shinichi MaedaCommitted ⭐️

Support for Double-Byte Characters in Property NamesClosed

Hello,We have confirmed that there is a restriction in the data model View (Container) definition that prevents the use of Japanese (double-byte) characters in property names.This limitation also applies to the Records/Streams API. Currently, our database column names and CSV file headers include Japanese characters, which means we are unable to use the existing names directly when registering these datasets as Records.As a result, we are now required to define a mapping between the Japanese column names and alphanumeric property names, and to establish, standardize, and manage a naming convention. However, this process is labor-intensive and may lead to confusion and operational burden in data utilization.Therefore, we would like to kindly ask if you could consider supporting the use of Japanese (double-byte) characters in property names within the data model View definitions and the Records API.

3
U
Forum|Forum|9 months ago
T
Seasoned ⭐️⭐️
tddahnkeSeasoned ⭐️⭐️

Charts Calculation Reversal IssueImplemented

Resolve the subtraction function issue in charts.  Currently the smaller value must be on top of the subtraction function to get a positive value.

2
T
Seasoned ⭐️⭐️
Forum|Forum|9 months ago
N
Seasoned ⭐️⭐️
n989Seasoned ⭐️⭐️

Ability to Process DGN'sClosed

We are running into a very significant capability issue with Cognite where the platform cannot process DGN (Bentley Microstation) files. We (Marathon and the supporting Cognite project team) need immediate assistance with getting this resolved. Rachelle Harris requested I submit this ticket to help elevate the concern. 

4
Carlos.Herrera
Forum|Forum|9 months ago
Noah Karsky
Practitioner ⭐️⭐️⭐️
Noah KarskyData Engineer

Warn on duplicate document upload to CDFParked

It would be nice if CDF warned users if they are uploading a document that already exists within CDF. It should still allow them to upload it if they wish, but a warning might help to cut down on duplicate documents. This is specifically an issue with Canvas, where users can drag documents into their canvas. It is less of an issue when using file upload pipelines, because duplicated can be mitigated in those scenarios. 

1
Elka Sierra
Forum|Forum|9 months ago
Markus Pettersen
MVP ⭐️⭐️⭐️⭐️⭐️
Markus PettersenMVP ⭐️⭐️⭐️⭐️⭐️

Uploading files to Canvas: the list shows data sets I can read, not data sets I can write toGathering Interest

This is the cause of a lot of frustration from our users at the moment. When trying to manually upload a file to Canvas you need to select a data set. However, the list you get is not the data sets that you can actually upload a file to, but simply a list of all datasets you have read access to. This makes it really difficult to identify the data set that you can actually use as there is no indication before you click upload and get an error popping up.In general end users of CDF at us will not have access to upload files manually to most of our data sets in production due to governance. Which is why we’ve set up a dedicated data set for this purpose. So we think a better solution would be if this list showed all the data sets that the user could actually upload to (all data sets the user has write access to) rather than all the data sets that will produce an error.Or at the very least have some kind of an indicator of the access level. Trial and error on the user side here is just a nuisance. We don’t see the point in showing all the data sets that will fail without indicating that they will fail.The intended audience for Canvas are not the developers that know all aspects of our implementation of CDF, but the domain experts that know the data. We want their experience to be as seamless as possible and right now it is not, and to avoid the system even allowing for these kinds of mistakes. Markus PettersenAker BP - Technical Domain Architect for CDF

2
Mithila Jayalath
Expert ⭐️⭐️⭐️⭐️
Forum|Forum|9 months ago
T
Seasoned ⭐️⭐️
tddahnkeSeasoned ⭐️⭐️

Public Chart DeletionImplemented

Add the ability to delete public chart(s) (if you the user is the owner) under the action location.

0
T
Seasoned ⭐️⭐️
Forum|Forum|9 months ago
N
Seasoned ⭐️⭐️
n989Seasoned ⭐️⭐️

3D Search interface - Make columns filterableImplemented

Can we add the functionality to be able to filter by columns in the 3D interface search? Just like you can in the normal search. 

4
N
Seasoned ⭐️⭐️
Forum|Forum|9 months ago
crgomez13
Seasoned ⭐️⭐️
crgomez13Seasoned ⭐️⭐️

Cognite InField 2.0: Ability to view attached images in checklist overviewImplemented

On behalf of Celanese InField super users,I would like the ability to view images that have been attached to a line item within a checklist while using the checklist overview page. This would make the review process a lot easier then needing to navigate to the specific checklist on the active checklists tab. Currently the checklists only show a grey dialogue box indicating that an image has been attached to a line item but there is no way to view the image. @Kristoffer Knudsen 

6
K
Forum|Forum|9 months ago
M
Seasoned ⭐️⭐️
Matheus NunesSeasoned ⭐️⭐️

Go from 3D Preview to 3D Full View in the new SearchImplemented

When want to be able to go from 3D Preview to 3D Full View in the new Search.Right now, when using the preview I can only click on the selected equipment. I want to be able to select different equipment and navigate in the 3D Model. 

3
Ragnhild Byrkjeland
Forum|Forum|9 months ago
M
Committed ⭐️
marksassCommitted ⭐️

View document full screen from 3D viewImplemented

Search for an equipment in 3d viewer and then open one of the associated documents.  It is shown in small screen that can only be enlarged by clicking and dragging the bottom right corner, most people will not notice this is possible - viewing in small screen is difficult.  Needs a ‘view full screen’ button. 

2
Ragnhild Byrkjeland
Forum|Forum|9 months ago
M
Committed ⭐️
marksassCommitted ⭐️

Full 3d viewing experience instead of previewImplemented

Search for equipment will enable a 3d preview.  Would be nice to have all feature of 3d viewing such as adding point cloud and 360 image layers as is possible if you start searching with the ‘Browse 3D’ button from the home screen.

3
Ragnhild Byrkjeland
Forum|Forum|9 months ago
P
Seasoned ⭐️⭐️
plheideSeasoned ⭐️⭐️

Geospatial support in FDM?Planned for development

Is there any plans to support geospatial queries in FDM? If so, would it be possible to share tentative timeline? Related to this is schema definition of coordinates.. Given a long pipeline with high resolution geography - I assume there is a tradeoff between storage optimization, geospatial query capability and managing (reducing) number of FDM instances.

7
HanishSharma
Forum|Forum|9 months ago
Pasindu Perera
Expert ⭐️⭐️⭐️⭐️
Pasindu PereraExpert ⭐️⭐️⭐️⭐️

general data explorer to view data in modelsParked

Despite multiple refreshes, the DM interface in CDF only shows two lines added to the Site. However, using Pygen, the user can see that all lines are attached to the Site.The user is suggesting another tool to use as a 'general data explorer' for data in models because the technical person can use Pygen, but other non-technical people at the organization do need to occasionally see what is in them.

3
Elka Sierra
Forum|Forum|9 months ago
W
Seasoned ⭐️⭐️
Willem MeijerSeasoned ⭐️⭐️

Show correct case for metadata and attributes in Data ExplorerClosed

I think this is more of a bug than a product idea.In Data Explorer, all metadata keys and values and all attribute values are show with lower case. Metadata fields like this, become less readable when everything is transformed to lower case:Also fields like “BagnG1” get transformed to “bagng1”, which also hurts readability.It is probably most problematic for units, where units like “Mm” and “mm” become the same.

1
Elka Sierra
Forum|Forum|9 months ago
Andrew Montgomery
Practitioner ⭐️⭐️⭐️
Andrew MontgomeryPractitioner ⭐️⭐️⭐️

Academy Course for teaching a data centric mindsetImplemented

I would like to help my solution building teams to understand a data-centric mindset (vs. asset centric) so they can effectively build solutions that take advantage of building on flexible data models. 

3
Elka Sierra
Forum|Forum|9 months ago
R
Seasoned ⭐️⭐️
Rani SupriyaSeasoned ⭐️⭐️

CDF - Search keyword, should allow to search any word, not only if started with the first word.Closed

DescriptionGeneral: Search keyword should allow to search any word, not only if started with the first word.Steps to reproduce the issue:Login to Cognite data fusion. Navigate to Data Explorer. Click on Events tabs in right side of the panel. Click on any filter option in under common filter section of left panel.Expected results: User should allow to search any word, not only if started with the first word and get results.Actual results: User cannot search if they search with second word of the statement.for e.g: PM Compliance, user try to search with word ‘Compliance’ results will not be found in Filter search.Here, attached screenshot. 

3
Elka Sierra
Forum|Forum|9 months ago
N
Practitioner ⭐️
Neerajkumar BhatewaraSchlumberger

Way to identify the reverse edges from UIGathering Interest

HelloEarlier I have seen that there was on UI of CDF({model_ext_id}/data-models/spaces) page to view the “view” in below visual format. There it was easy way to identify the reverse edges as shown below, it provided small visual clue, but now i am seeing of late, there is no way to identify the reverse edges from the below UI screen. Can we add back something to identify the reverse edges in fact all different type of  types individually. Refer field CogniteFile highlighted in yellow.Also 2nd Problem - the actual Properties name is files but shows up as CogniteFile. This problem is in both before and now as well. I expect actual property name to be shown here, for few it works and for many others it does not works.    1. BeforeNow Let me know incase of any doubts.  Regards, Neeraj B

0
N
Practitioner ⭐️
Forum|Forum|9 months ago
A
Committed ⭐️⭐️
asahafCommitted ⭐️⭐️

[Fusion] Fuzzy Search for Metadata/Labels Filters in CDF Fusion Data ExplorerClosed

When using the data explorer filters in CDF Fusion (such as the Metadata and Labels filters), it would be helpful if there was a 'fuzzy search' feature. This would allow users to search for relevant metadata or labels without needing to type the exact, full text. This could be particularly useful when there are many different metadata fields or label options to choose from, and remembering the exact wording may be difficult.

3
Elka Sierra
Forum|Forum|9 months ago
Priyanka Perera
Practitioner ⭐️⭐️⭐️
Priyanka PereraPractitioner ⭐️⭐️⭐️

Capability to define columns globally for a project in new search experienceImplemented

There is a feature request from National Grid UK that, super users should be capable of defining columns for different views in the search explorer globally.This means that a super user will be able to set the visible columns for different views and set that as the global project setting for everyone. Individual user can override it but it should be possible to re-apply got global columns settings for the project buy a click of a button(s). This should be applicable for both data model views as well as classic CDF resources.

2
Sofie Svartdal Berge
Forum|Forum|9 months ago
E
Seasoned ⭐️⭐️
EmilyViolaSeasoned ⭐️⭐️

List filters and items within filters alphabeticallyImplemented

Unless there’s some other sort applied, the filters and the items within the filters should be listed alphabetically to find items easily. 

2
Sofie Svartdal Berge
Forum|Forum|9 months ago
Øystein Aspøy
Seasoned ⭐️⭐️
Øystein AspøySeasoned ⭐️⭐️

Change default search settings for a tenant/projectImplemented

I would like to change the standard default search setting for all our environments for all our users.Today each user have to set up their own search setting with regards to which metadata to show etc, but I would like the users to have a better starting point first time they log in to fusion. This would make it easier to have a good start with using fusion, also I think most of the users does not know that this setting can be changed.Is it possible for me to set up the default fields to show for each category for all users? 

7
Sofie Svartdal Berge
Forum|Forum|9 months ago
E
Committed ⭐️⭐️
etatetooheyCommitted ⭐️⭐️

Globally Enable Metadata Columns to File Search ResultsImplemented

Please add the ability to globally enable metadata categories as default columns.For example on files - since the majority of our files are P&IDs (and the file titles are numbers) we would like to have the metadata categories such as drawing title or description a default option for our network rather than have to show everyone how to add it every time they log in - a large population are not computer savvy and this would help with product integration/user friendliness.

3
Sofie Svartdal Berge
Forum|Forum|9 months ago
Mithila Jayalath
Expert ⭐️⭐️⭐️⭐️
Mithila JayalathExpert ⭐️⭐️⭐️⭐️

Elapsed time unit should be next to Elapsed time by Default in CDF Data Explorer screen under Events tab for Meta data section for Failure events.Implemented

I’m creating this feature request on behalf of @Smitakshi Sen Elapsed time unit should be next to Elapsed time by Default in CDF Data Explorer screen under Events tab for Meta data section for Failure events.

3
Sofie Svartdal Berge
Forum|Forum|9 months ago
Philippe Bettler
Practitioner ⭐️⭐️⭐️
Philippe BettlerPractitioner ⭐️⭐️⭐️

Have a customer defined default configuration for the table view in FusionImplemented

Allow for customer to choose their own Configuration of columns rather than the default Cognite view.This would be the new default, after which users can move fields around as they choose as designed.The configuration includes:which column is displayed in the table view what order the columns appear in the width of the columnThis configuration is set by the customer - maybe in a dedicated page on fusion that is customer specific.

5
Sofie Svartdal Berge
Forum|Forum|9 months ago

Filter by Topic

  • All Topics
  • Quarterly Product Release
  • 3D
  • Academy Trainings
  • API and SDKs
  • Atlas AI
  • Authentication and Access Management
  • Charts
  • Contextualization
  • Data Modeling
  • Data Quality
  • Data Workflows
  • Developer Tools
  • Drilling and Wells
  • Extractors
  • Functions
  • Industrial Canvas
  • InField
  • InRobot
  • Jupyter Notebooks
  • Maintain
  • Other
  • Product Releases
  • Product Roadmap
  • Public Beta
  • Search and Data Exploration
  • Streamlit
  • Toolkit
  • Pygen
  • Security Updates
  • Simulator Integration
  • Transformations and RAW
Terms & ConditionsCookie SettingsAccessibility statement