Skip to main content

Product Ideas Pipeline

Filter by Idea Status

Filter by Topic

1354 Ideas

Ben Brandt
Seasoned ⭐️⭐️⭐️
Ben BrandtSeasoned ⭐️⭐️⭐️

Cognite Data Fusion: Data Set Archive Feature That Also Archives Data Within the Data SetClosed

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”? 

Ankit KumarSenior Cloud Architect

Cognite Data Fusion: Enabling CDF OData apis for Microsoft Sustainability ManagerGathering Interest

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.