Skip to main content

Product Ideas Pipeline

Filter by Idea Status

Filter by Topic

1256 Ideas

Andrew Wagner
Seasoned ⭐️⭐️
Andrew WagnerSeasoned ⭐️⭐️

Feature Request: Display Time Series Tag Name on Checklist ItemsGathering Interest

ProblemIn checklist items today, users can only see the time series description, not the actual tag name. Because assets often have multiple associated tags, it can be difficult to determine which time series a checklist item is referencing. This is especially challenging when users click through to view trends and must manually identify the correct tag.Proposed EnhancementDisplay the time series tag name directly on the checklist item (alongside or in addition to the description).Value / BenefitsImproved operator usability: Newer or less experienced operators are not yet familiar with tag naming conventions, making it harder for them to confidently navigate from checklist items to the correct trend. Faster troubleshooting: Power users and IT frequently need to diagnose checklist or tag write‑back issues. Seeing the tag name directly eliminates the need to switch back and forth between checklists and templates to identify the correct time series. Reduced ambiguity: When multiple tags exist for a single asset, explicitly showing the tag name removes guesswork and reduces the risk of viewing or writing to the wrong signal.Who BenefitsOperations (especially new operators) Power users IT / support teams maintaining checklist templates and tag write‑back logicThis small UI enhancement would meaningfully improve clarity, efficiency, and supportability of checklist‑driven workflows.Mockup Example: ​@Andrew Montgomery ​@Mike Hammons 

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.