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
We would very much like for a new column to be added to this view, “extractor type”. Currently there are no indicators as to what type of extractor it is. For the developers working on the extractor this is not an issue because they know, but for others that just want an overview this is somewhat more difficult as we would need to click in on every single one of them to find out. Sometimes we would like to just see all REST extractors, or all MQTT extractors and so on. Another point is the throughput: “0 datapoints p/hr”What does the “p” stand for, is it “0 datapoints per hour” because if so the p is redundant as the standard use of “/” already signifies it. Also the SI unit for hour is h not hr. E.g.: km/h (km/t norwegian), m/s etc.
Hello, I have trying to use the ODBC extractor to pull data from Snowflake, I could do that by following instructions here https://docs.cognite.com/cdf/integration/guides/extraction/configuration/db/#-snowflake However, this requires me to put passwords in YAML config. Is there anyway to use DSN from ODBC instead? I see that connection-string parameter is not supported when I choose type as snowflake. Thanks!
Problem Description: Cognite File Extractor for Sharepoint is not able to recursively retrieve documents from a Sharepoint site where site and sub-sites, e.g. Document Control System Alternatives explored: Provide Sharepoint URL as mentioned in documentation for site (Sharepoint Online | Cognite Documentation) Results: no errors, however, no documents are loaded Evaluation: recursion does not occur from site-level down to the document or folder level where Sharepoint stores documents Provide document library and folder / sub-folder Results: working, however, sustainability not ideal Evaluation: will require potentially >100 URLs to be configured and kept up-to-date in case of new document libraries or folders created or deleted Recommended enhancement Recursion from root node (Sharepoint site). E.g. if site URL is provided recursion should go through each sub-site (if present) to document libraries and sub-folders to retrieve documents This should be treated as high-priority. Item 2B above can be seen as a work-around but maintaining Sharepoint URLs in config up-to-date will require coordination/sync with source – likely through custom
Problem: If one or more of the source-time series are missing data-points they will also be missing in the synthetic time series output.Would it be possible to add an option to supply a default “not available” value for missing data-points which could then be used by the API to calculate a partial result?Source:
I understand that updates older than 7 days may be discarded from the endpoint, which is perfectly fine. However, I’m wondering if it’s possible to determine when a cursor is older than the given limit, since updates older than 7 days are discarded. Based on my understanding of your Subscription API, it would simply continue iterating over the oldest available updates on the endpoint, which could result in missing important updates that occurred between the time of my cursor and the current oldest update. For the Subscription API to be fully functional, I believe it's essential to either receive a notification or an exception when using an expired cursor, be able to determine the age of a cursor, or somehow be assured that iterating from a cursor won't lead to lost data. Knowing the age of the cursor would be preferable, as it would allow us to gauge how much margin we have, but it should also be possible to receive a notification if an expired cursor is being used. Is this currently possible, or are there any plans to implement such a feature?
Once in a while we make changes to our telemetry setup in such a way that certain time series get deprecated. This happens when we change control systems, or make changes in our telemetry pipeline, or even discontinue operations at a location. We want to have the “deprecated” time series available in CDF, but it would be useful for us if these would not by default appear in search, or in the asset hierarchy, or through grafana and other solutions. It would be useful if there was a way to mark a time series as deprecated or as only containing historical data - and that in order to have the time series returned in search or list operations, the user would have to make an active choice to include those time series. My suggestion is an “isDeprecated” property on each time series. There are other solutions to the problem, but these all seem to make it more difficult for the user than simply not showing deprecated time series by default:Metadata field - isDeprecated (boolean) Move deprecated time series to a different data set Separate data models for “active” and “non-active” time series
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.
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.
Resolve the subtraction function issue in charts. Currently the smaller value must be on top of the subtraction function to get a positive value.
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.
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.
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
Add the ability to delete public chart(s) (if you the user is the owner) under the action location.
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.
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
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.
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.
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.
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.
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.
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.
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.
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.
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
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.
Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
