We really need to get SAP Extractor going:
Product | Open item | Category | Ticket # | Status | Link |
SAP extractor | Support for OData v4 | Product idea | 3288 | Gathering interest | cognite-sap-extractor-support-for-odata-v4-0-endpoints-3288 |
SAP extractor | Performance concerns with larger SAP tables | ||||
SAP extractor | Attachments support | Product idea | 2528 | Planned For Development | cognite-sap-extractor-attachment-2528 |
SAP extractor | SAP extractor with "nested/dependent" entity queries | Product idea | 2753 | Planned For Development | sap-extractor-with-nested-dependent-entity-queries-2753 |
SAP extractor | Cognite SAP extractor: Intgerate with T-codes | Product idea | 2532 | Closed | cognite-sap-extractor-intgerate-with-t-codes-2532 |
SAP extractor | Cognite SAP extractor: Splitting large data ranges inputs | Product idea | 2529 | Planned For Development | cognite-sap-extractor-splitting-large-data-ranges-inputs-2529 |
SAP extractor | Cognite SAP extractor doesn't accept multiple keys | Product idea | 2205 | Gathering interest | cognite-sap-extractor-doesn-t-accept-multiple-keys-2205 |
SAP extractor DB extractor | Generating dynamic keys (e.g. while ingesting CSV/XLS files to RAW which doesn’t have a uniqueidentifier) | Product idea | 2792 | Gathering interest | new-feature-for-sap-db-extarctor-2792 |
Hi@ibrahim.alsyed thanks for synthesizing some of the key SAP Extractor enhancements. We’ll just mark this one as “Duplicate”, and the team is following up on the individual ideas. I’ve understood some of them may already be implemented. We’ll comment on the individual ideas with more details, including updated statuses.