Impact 2024: The Industrial Data and AI Conference for and by Users | Nominate Speakers Now for a Ch...
Enhance the SAP extractor to incorporate a configuration option enabling the division of large date range inputs into smaller segments. This functionality aims to prevent SAP requests from failing due to size constraints.
Feature Request: Implement a dynamic visualization module in the Cognite Monitoring for extractors to enrich data insights. Users should have the ability to visualize the extractors status by plant in a traffic signal format (red/green/blue). The feature must support real-time updates, allowing users to monitor live data and historical trends seamlessly. Include interactive elements like drill-down options, tooltips, and data filtering for a user-friendly experience.
We kindly request your support in enhancing the SAP extractor to include support for OData V4.0 endpoints.By extending the compatibility of the extractor to encompass OData V4.0, we can seamlessly extract the required data from SAP, enabling us to optimize our integration processes and derive valuable insights from our SAP data.The addition of support for OData V4.0 endpoints would significantly enhance the functionality and utility of the SAP extractor. OData V4.0 is the latest version of the OData protocol, offering improvements in areas such as performance, scalability, and flexibility compared to previous versions. By enabling the SAP extractor to communicate with OData V4.0 endpoints, users would benefit from enhanced performance and compatibility, ensuring a smoother and more efficient data extraction process.A lot of SAP API’s are on OData V4.0 and having the support will enable us to progress on ingestion of these API’s
I am writing to request a new feature for the Cognite File Extractor tool that would enhance its functionality and usability. Specifically, I propose the addition of a configuration option to control the number of files loaded by the extractor.As a user of the Cognite File Extractor, I have encountered situations where I need to manage large volumes of files during extraction processes. Currently, the tool loads all files present in the specified directory, which can lead to performance issues and inefficiencies when dealing with a high number of files. Therefore, implementing a feature that allows users to specify the maximum number of files to be loaded in a controlled manner would greatly improve the tool's flexibility and performance.The proposed configuration option would enable users to define a limit on the number of files extracted, through a numerical input . This would give users greater control over the extraction process, allowing them to tailor it to their specific needs a
Transferring asset hierarchy data between the root assets within Cognite poses a challenge due to a limitation within the Cognite Data Fusion (CDF) platform. However, this functionality is readily supported within SAP. In other words, while SAP facilitates the seamless movement of asset hierarchy data across various root assets, Cognite's CDF platform lacks this capability, presenting a constraint in data engineering management and pipeline failures. This limitation results in the real time failures as SAP changes are typically not in our control and business teams perform these changes periodically.
Request: Enhance our SAP extractor by incorporating compatibility with SAP transaction codes. This integration is crucial for seamless communication between systems, allowing to execute specific SAP transactions directly through the extractor interface. . This feature will streamline processes, providing efficiency and convenience for obtaining data from SAP system.
Idea to develop an API-based extractor designed to facilitate seamless integration between external system APIs and Cognite. This extractor serves as a crucial link between diverse APIs and the Cognite platform, ensuring efficient data transfer and integration capabilities.Current approach is we go to the source system and custom configure the API’s of source system and Cognite API’s to integrated data. API Compatibility: - The extractor must support a wide range of APIs to accommodate various data sources and types, including RESTful, GraphQL, and other standard API protocols. - It should be adaptable to changes in API versions and structures, allowing for easy updates and maintenance.Extractor should have capability to send data to Cognite Raw/FDM/any specific target area within Cognite. Data Extraction and Transformation - The extractor should enable configurable data extraction parameters such as date ranges, filters, and pagination options to retrieve relevant infor
Feature request : We need to enhance the existing cognite sharepoint extractor by incorporating the capability to seamlessly integrate with SharePoint lists. This extension should support the integration of CRUD operations to facilitate efficient and comprehensive data management from the SharePoint environment to CDF.
Subject: Feature Request - File Size detail in CDF Documents APIWe request the inclusion of a File Size within the CDF Documents API. Currently, the absence of this crucial feature impedes our ability to identify file corruption based on size. This limitation compels us to download files for manual checks, causing inefficiencies and resource wastage. Although file size is available in metadata, it reflects the ingested value, not the actual size stored in CDF. The introduction of a dedicated File Size API would enhance efficiency, enable real-time corruption checks, and streamline downstream processes like contextualization. Your prompt attention to this feature request will significantly improve our workflow.
Feature Request: Enhance the SAP extractor functionality to enable the ingestion of attachments which are on multiple objects such as notification, work order.., along with associated document metadata. Additionally, ensure seamless support for CRUD (Create, Read, Update, Delete) operations to manage attachments effectively for the integration
Ensuring the security of PI credentials is critical in the Cognite PI extractor.In the context of Azure Vault, the requirement involves implementing robust measures to safeguard PI access credentials. This entails storing sensitive information, such as usernames and passwords, securely in Azure Vault. The system should be configured to read these credentials from the vault when needed, providing a secure and centralized method for managing and accessing PI authentication details. This approach enhances overall data security by minimizing the exposure of sensitive information and adhering to best practices for credential management in cloud environments. we have implemented in other custom extractors. can you share the documentation to implement in Cognite PI extractor
Upsert functionality is available in the cognite Java SDK but not in the rest API calls On a high level there are two types of Rest interfaces which are coming from SAP to CDF 2)Assets are going through asset hierarchy so they get automatically linked. Events : there are two major concerns Cognite doesn’t have an upsert API – we need to check every time whether the record exists from PI PO and then call create/ update API based on the response. This is doubling the calls from PI PO side In the event API as per the documentation available in https://docs.cognite.com/api/v1/#tag/Events/operation/createEvents the request body schema assetIds is expecting internal ID . Asset IDs of equipment that this event relates to). Due to the above cognite design there is duplicity of calls . So, we are requesting the below requirements Requirements Assets Functional Location, Equipment. Events Notifications, Work order The ch
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.