Skip to main content

Product Ideas Pipeline

Filter by Idea Status

Filter by Topic

1354 Ideas

Zachary BurkeCommitted ⭐️⭐️⭐️

Enhanced Access Management for PI ExtractorGathering Interest

Though many companies are pretty liberal with read access on tags within a PI Data Archive, some out there need to control access at a more granular level. (Often driven by the need to protect intellectual property.) Only certain groups of users should be able to see data for certain tags.In our case, we would like our access model with respect to PI data in CDF to mimic what’s in PI. In a PI Data Archive, this is governed by the datasecurity metadata field. Unfortunately, the PI extractor seems to strip off this metadata on ingestion. Without that, we’re looking at a workaround solution in which we maintain this mapping in CDF and use something like a Cognite function to apply a security category that mimics the PI tag’s data access. However, this does come with some headaches:We’ll have to maintain a separate mapping of PI tags to the right level of access (that would otherwise be present in that datasecurity metadata field). The PI tag data can’t be secured before that security category is applied.I provide all this background information in the hopes that it’s useful for developing features that are useful for this need. But if I had to make a concrete ask:Provide an option for the PI extractor to not strip off “internal bookkeeping attributes in PI” from incoming PI tags. Provide a means to apply a security category during the extraction process, itself. (Similar to how the file extractor does.)Thank you for your attention and looking forward to discussing more! 

Anders Brakestad
Seasoned ⭐️⭐️⭐️
Anders BrakestadSeasoned ⭐️⭐️⭐️

Power BI Connector: Cannot filter on external id when using push-down filtering to load Sequences into CDFNew

We use push-down filtering to get our relevant data from CDF into Power BI. We filter on the external ID property, since this is constant across our environments in CDF. Here is an example of that this looks like: Source = Cognite.Contents(cdf_env & "/Timeseries/?$filter=ExternalId eq 'an_external_id'", null) This works great for Time Series, but doing the same thing for Sequemces leads to an error:DataSource.Error: Microsoft.Mashup.Engine1.Library.Resources.HttpResource: Request failed: OData Version: 3 and 4, Error: The remote server returned an error: (400) Bad Request. (The provided filter was invalid.)OData Version: 4, Error: The remote server returned an error: (400) Bad Request. (The provided filter was invalid.)OData Version: 3, Error: The remote server returned an error: (400) Bad Request. (The provided filter was invalid.)Details: DataSourceKind=Cognite DataSourcePath={"project":"akerbp-dev\/Sequences?$filter=ExternalId eq 'val_alarms_top_10_weekly'"} Push-down filtering on the external id seems to be supported based on the information here; Am I doing something wrong? Is there maybe a bug somewhere? Filtering on the Name attribute does work, and it keeps us going for the moment, but I don’t like that the Name is not a unique identifier of the object. Thanks for any help and advice! :) 

Viet LePractitioner ⭐️⭐️⭐️

Cognite Data Fusion: Explore Assets search and hierarchy view suggestionsImplemented

Search results in the hierarchy view of Explore Assets is difficult to use. It’s almost impossible to find what you are looking for in a very large/deep hierarchy. We are almost always resorting to the list view and disregarding the hierarchy view entirely since even after searching, one finds themselves scrolling and scrolling to find yellow matches. Because the hierarchy view also shows close matches, the view is littered non-exact matches.After finding the asset, you can only view children. There is no way to navigate to the parent from the asset view. It is quite useful for us to find an asset and be able to view the ancestry tree to the root and its children.The ONLY way for us to get the ancestry view of a particular asset goes like: Explore Data → Assets Search Skip Hierarchy view, use List View instead View Details of the Asset, copy the External ID Open Filters Put External ID in filter Finally have a hierarchy view with only the ancestry of a particular Asset I have some suggestions that may help bring some usability into search.  An option to show exact matches only… for times I know exactly what I am looking for. (99% of the time) Similar to Find in a document search, there needs to be a Next and Previous button that auto-focus on the next match. There needs to be a way to navigate up and down the ancestry tree. One can only descend from Asset to Children. It is impossible to navigate from Asset to Parent. Instead of a Children tab, perhaps just show the Lineage/Ancestry of all Assets in this family tree? Perhaps give the option to show how many degrees up and down from the current asset, in case there are hundreds or more in a family. We are not able to search by ID, this would help allow us to find the exact search. Search box results should not reset, such as the user’s position or search text, via actions in an expanded sheet on the right. EX: Have a very large hierarchy. Search for an Asset via text in Hierarchy view (no filters), something that required scroll down to middle of search results, click on it. Its details are expanded in a sheet on the right. Click any Tab in the sheet. (Children, Asset, …) Search text and position in the search results are fully reset.