Symptom
Catalog asset OData API (/api/v1/datasphere/consumption/catalog/assets) returns a list of assets that does not include local tables.
Environment
SAP Datasphere
Reproducing the Issue
- Perform a GET request to the catalog asset API (/api/v1/datasphere/consumption/catalog/assets).
- Observe that local tables are not present in the response.
Cause
Local tables cannot be returned by the Catalog asset OData API. The OData APIs mentioned in the following document can be only used for consuming data exposed as views, analytic models, or perspectives:
Consuming Data via the OData API
Resolution
- To consume local table's data via OData APIs, create views, analytic models, or perspectives on top of the local tables and expose them for consumption.
- Use the following SAP Datasphere Command Line to list objects of a given type within a space, for example:
datasphere objects LocalTable list --space <id> [--output file.json]
Details can be found in the document: Managing Modeling Objects via the Command Line
Keywords
datasphere catalog api, assets endpoint, local tables missing, odata api, consumable views, metadata retrieval, datasphere cli, list objects, space objects, catalog limitation, expose for consumption, datasphere catalog , KBA , DS-BB-ODATA , To address issues related to Odata consumption API , Problem
SAP Knowledge Base Article - Public