Skip to main content

Product Ideas Pipeline

Filter by Idea Status

Filter by Topic

1241 Ideas

DeelakaCSPractitioner

Support for Multi-Level Subsites in SharePoint File ExtractorGathering Interest

Currently, the SharePoint File Extractor fails with a ValueError: Couldn't obtain document library id when attempting to extract files from a document library located within a nested subsite (a subsite or deeper).The extractor successfully connects and works for standard site structures, but fails exclusively on deep hierarchies. Troubleshooting confirms this is not a permissions issue, and the URLs are fully accessible via a standard web browser.Technical Context & Limitation:The current Cognite SharePoint extractor expects the URL schema to follow a single-level subsite structure:https://<tenant>.sharepoint.com/sites/<parent-site-name>/<subsite-name>/library-nameWhen provided with a multi-level subsite URL (e.g., https://<tenant>.sharepoint.com/sites/<site-name>/<subsite1>/<subsite2>/library-name), the extractor attempts to treat the intermediate subsites as document libraries.  Because the extractor currently uses a trial-and-error method to differentiate between a library and a subsite, recursively checking multi-level nested sites would generate an excessively high number of API error calls, potentially hitting rate limits.Requested Solution:Enhance the SharePoint File Extractor to support multi-level subsite traversal. This may require evaluating and leveraging alternative Microsoft Graph API endpoints that can efficiently map directory structures without relying on the current trial-and-error query method, thereby avoiding API rate limit issues.

Several actions in the "Explore and select your data" view in Charts kicks you out and into Search, when using Data ModellingGathering Interest

When adding data in Charts via the “+Add data”→ “Add time series”→ “Explore and select your data” the behavior using classic vs data modelling is very different.  By using a CDM extended data model we see that a series of actions related to Assets push you out of the “Explore and select your data” and into full Search. We do not see the same behavior when using classic data model.Here is a non-exhaustive list of actions that kick you out of ChartsFrom an Asset, clicking on parent, an asset from the path, or children  from the “assets” reference  From a File, clicking on any Asset reference From an annotated file, clicking on the “Open” button on the popup when you click an Asset annotation From an Activity or TimeSeries, clicking on Asset references Clicking on any Asset in the “bread crumb” trail in the  “Explore and select your data”  Clicking on the back button in the “Explore and select your data”, if the last item in the “bread crumb” is an Asset What does not kick you out:Maneuvering the asset hierarchy using the “Tree view” Clicking on any non-Asset links (what I’ve seen so far) Clicking “Open” on the file link annotation from an annotated file Clicking on Files in the “bread crumb” trail in the  “Explore and select your data”  Clicking on the back button in the “Explore and select your data”, if the last item in the “bread crumb” is not an Asset Except using the “Tree view”, it seems like any Asset related action kicks you out. We do not see the same behavior using classic data model. If this is related to how we have extended our Asset, it would be good to have this documented so we can adjust our UI data model