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!
Feedback from customer:The landing page for InField is hard to understand. Tag scan or search should be more visible as the landing page in the app. Check-lists get too much focus.Importance: Should have.Context: Landing page, after logging on inField for offshore workers.User story: As an offshore user of inField I would like for tag scan or search to be more visible, and check-lists to get less focus, in the landing page after logging on, so that it is easier for me to access the features I want to use.Picture:Would like checklists to get less focus and tag scan to get more focus.
There is the arrow on the left hand side of the screen for CDF to go backwards. Please add a corresponding arrow to return to the screen from which you just went back. Makes navigating back and forth between data very easy.
I am entering this on behalf of customer Celanese - Acid South Unit - InField Superuser, James “Hud” Hudson: Trending in InField.Issue: Too many come up and they are just a random ID # and have no description coming in.For ease of navigating, it would be helpful to have an unselect all button so you don’t have to go un-click the list that InField decides to auto-check when you click on Trends for an Asset. Option to set My Favorites Trends that would be auto checked in Trends for each asset in Trends View. I can learn the names/ids of the time series coming in that I care about and set them as favorites to check by default. Even better would be to have ability to set Unit Favorites/Group Favorites AND have personal favorites where you could decide with you want set as default to open on Trends page. . then As a Learning Facilitator ability to set unit/team favorites to make it easier to onboard new employees and to make sure process experts are using all the features available to them.
Insert "descriptor" in Trends section of InField for time series so you can see the pi tag and the name of it
We realized that the grouping by “Document type” for files only applies to “Linked files” but not to the other options of the drop down.Can the grouping be applied consistently?
I’ve been using the retrieve_dataframe function in cognite-sdk and been missing the feature to getting a fixed size of the dataframe when doing separate requests. When requesting aggregates of data points in a timeseries, there is no output when the are no data points within a instance of granularity. For example, I have used:df = cdfClientRef.datapoints.retrieve_dataframe(external_id = '', start = '10d-ago', end = 'now', aggregates = ['average'], granularity = '1d')If there are no data points in that time I get an empty dataframe. If there are no data points within a day in this example that row would missing from the output.Empty DataFrameColumns: [ |average]Index: [] If I instead request several timeseries, the missing data is given as NaN to fill out the dataframe: |average |average2022-08-30 NaN 3803.4689552022-08-31 NaN 3837.4375942022-09-01 NaN 3826.1252392022-09-02 NaN 3841.2270532022-09-03 NaN 3834.5268552022-09-04 NaN 3839.3240812022-09-05 NaN 3829.4462602022-09-06 NaN 3833.0025602022-09-07 NaN 3853.3407272022-09-08 NaN 3854.664126 It would be useful with an option to make sure the output dataframe contains an entry for each requested instance for a given granularity, meaning that instead of an empty dataframe the output would be: |average2022-08-30 NaN2022-08-31 NaN2022-09-01 NaN2022-09-02 NaN2022-09-03 NaN2022-09-04 NaN2022-09-05 NaN2022-09-06 NaN2022-09-07 NaN2022-09-08 NaN
On behalf of AAS Unit and LDR unit at Clear Lake:As a process expert and a loading/shipping expert at Celanese, I need to be able to input text as an answer/to complete the ToDo to capture information for the day’s work. This information should be able to write back to CDF for reporting/dashboard purposes as well. (if this is captured elsewhere, please let me know)
Please allow queries to the datapoints “table” in the PostgreSQL gateway by the Timeseries ID.Not sure if id is intended here to be the id of the datapoint or the timeseries, but something like this:
As a production planner I want to be able to submit back-up orders to the Day Ahead Auction for D+2 (or several days ahead). In order to do that, I need a bid matrix for D+2,3,4...
Adding this idea to check demand for touch screen interactions with the 3D Model especially in Remote, for small screens like tablets. See also @ibrahim.alsyed @Jorge Lopez
When we create AIR models and define the input fields, is there any way of setting predefined values that is shown in the front end when configuring monitoring tasks?For example in config.yaml we define a field called max_timefields: max_time: name: “Max Time” description: “Max Time in ours between datapoints” type:”float” When configuring a new monitoring task I would like the “Max Time” field to be pre populated with a default value (8 hours). Is that possible?
In PostgreSQL gateway the datapoints use the field name “time_stamp”. In the PostgreSQL connection used by direct query the field is called “timestamp”. As much as possible, can these field names across these providers be consistent with one another?
It would be awesome if we can explore CDF Geospatial from the Fusion API, similar to how we explore assets or sequences.
During a site visit, I discovered the apparent need for multichoice input values in a checklists. Look:The example is fairly self explanatory. You want to confirm (check off as OK) that you’ve certified which helium bottle is in use, and you don’t want to leave an unchecked item as if there is a check you haven’t done. Ideally you would haveHelium bottle in use[_] A[_] BWhat are your thoughts on this?
I would like to have an option for an idempotent option for the Cognite Client. For example, I can add the same asset multiple times without rising an exception.Use Case: I have a script (running on a schedule in Cognite Functon) which dynamically create an asset hierarchy. Current behavior: If I try to add a list of assets in which one asset is existing in CDF, then no new assets are appended to the hierarchy and an exception is raised.Desired behavior: An option for suppressing the raised exception and add the new assets to the asset hierarchy.``client.assets.create(new_assets, skip_existing=True)``
Hello!After reading the documentation for CDF Data Sets I ran a few experiments with the Python SDK, creating assets, time series, and data points all within a data set. When I was done, so as not to clutter up the CDF instance we are all sharing while prototyping, I selected my data set within the “Create, view, and manage data sets” and clicked the “Archive” option.I browsed back over to the Assets page, but was surprised to still see my assets from my archived data set visible within the CDF UI. I thought maybe it was just because of eventual consistency as we all struggle with that with distributed systems. After a while I check the documentation and saw this:Edit and explore data sets | Cognite documentation You can also edit the data sets to add more documentation to them, or to write-protect them to provide an extra layer of protection to production-critical data. By archiving data sets, you can hide data sets that are no longer used. Archive data sets to hide them from the UI and make the data set unavailable to users. The data set and the data it contains is not deleted, and you can always restore archived data sets later. It seems to describe "write-protect" as something that affects the data, preventing others from inserting, updating, or deleting rows within that dataset. Then when Archive is described it says, "hide data sets that are no longer used" and "make data set unavailable to users", where I believe the natural assumption for the reader would be that data set is a set of data and operations on the data set affect the set of data in that data set.I understand that how the feature currently works is desired behavior, as Torgrim Aas had explained to me, “Datasets must be considered more like "labels with metadata" since it does not affect the data within the dataset. It only allow users to extract group related information about the data, which can span across different data sources.”But could we also add another option to “Archive Data Set, Including Data”?
Currently, the client.datapoints.insert() function does not support timezone aware datetime objects, and throws an error if you try to upload datapoints with such datetimes:Can you fix this? I imagine the fix would be very simple, simply switch out the definition of the datetime_to_ms() function to:def datetime_to_ms(dt): return dt.timestamp()*1000
Microsoft Sustainability Manager(MSM) is a service which answers organizations needs of building insights they need to manage their environmental footprint, embed sustainability through their organization and value chain, and create new value in a changing landscape. Building insights on the tool with CDF as source will give added advantage to Cognite’s customers in accelerating sustainability progress and business growth by bringing together a set of environmental, social, and governance (ESG) capabilities.The connector available in MSM is limited and the one which can be used for connecting to CDF resources are our OData Apis, However, OData call for now, only support authenticating with organizational account. On sign-in event for a CDF project, with organizational account, an app called App Service (a Microsoft 1st Party app) is trying to access a resource - Cognitedata API: westeurope-1 - by specifying one of its identifiers as part of the sign-in request: login.microsoftonline.com/common/oauth2/authorize?client_id=*&response_type=code&redirect_uri=*&resource=https%3a%2f%2fwesteurope-1.cognitedata.com&prompt=select_account&state=* When AAD handles this sign-in request, however, it returns the following error message: * AADSTS650057: Invalid resource. The client has requested access to a resource which is not listed in the requested permissions in the client's application registration. Client app ID: 7ab7862c-4c57-491e-8a45-d52a7e023983(App Service). Resource value from request: https://westeurope-1.cognitedata.com. Resource app ID: 209cbd1f-df92-4fb1-8e30-054812586bc9. List of valid resources from app registration: .The resource app (Cognitedata API: westeurope-1) https://westeurope-1.cognitedata.com is defined as one of its Identifier URIs. . In these scenarios, when the App Registration is created, we would also need to add "App Service" as a pre-authorized application on your resource (Cognitedata API: westeurope-1) - which can be done by navigating to Azure AD >> App Registrations >> Cognitedata API >> Expose an API >> Add a Client Application >> 7ab7862c-4c57-491e-8a45-d52a7e023983 >> Add Application:Once these steps are performed, Azure AD should be able to find the "missing" resource.
Hi, I’m customer success in Japan. I got a request from one of our customers who are requesting improvement of the feature of AIR about close activated alert. When we get alert notification via e-mail, it should be closed individually by opening each activated alert at AIR UI. From the feed back from the site operator, they would like to close the whole active alerts by selecting activated alerts one time, not individual opening to close. Kindly consider this request could be valuable for other AIR users.
In our project we have some events and assets who have many relationships (hundreds), viewing these relationships in Explore on the Fusion UI is almost impossible as you need to scroll for a very long time to find the relationship you are looking for. Luckily, we usually only care about the newest relationships to be created. I therefore wondered whether it would be possibly to add a “sort by” button or similar to Explore. Such that you can get the newest relationships to be on the top of the list of relationships, and therefore can avoid having to scroll through all the relationships to find the one I am searching for.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
