Change in "Universal REST API integration" in SAP Build Apps ; "Response key path" is missing

[Amitabha_Bandyopadhyay]

Hi Experts,

I have been using the public REST API: https://services.odata.org/v4/northwind/northwind.svc/Orders.

In the new Configuration UI for "Universal REST API Integration," the "Response Key Path" is missing. I tested the API with the below configuration, saved the schema, and mapped it to a data variable for use across UI containers and components (refer to attached screenshots). However, no data appears during the web or mobile test process.

Please assist.

[Dan_Wroblewski · Accepted solution]

If you display the data in your data variable, you will find it empty, which explains why you don't see anything further along. There is a fundamental problem, which is you are executing a list, but you are returning an object (see your first screenshot).

There are 2 ways to do this:

1. Fix the current way.
2. Probably use the right data source.

To fix the current project using a REST data resource, you need to return a list in your list action. SO you have o get rid of everything else besides your list in the response. To do this, use the response mapper. It already has the basic coding, so you just add "value" to be the top level to be returned in the response.

{records: response.data.value, driverCode: response.status}

Now you use he data variable for the repeat, and the bind the fields to "data items in repeat". Not sure what you are doing with the nesting repeats, since there are no nested objects in the response.

But all his begs the question: Why not use the OData data resource for this OData API?

In the past people wanted to send complex OData filters, and this was not possible with the OData data resource, but now you can define actions, which will let you do all that, so I would think that is the way o go.

[Amitabha_Bandyopadhyay · Accepted solution]

Hi Dan, I’m new to BTP Build, transitioning from an ABAP background with certifications in BTP IS and SAP ABAP on HANA. Apologies if this seems odd—I’m in a self-learning phase and created a scenario to fetch OData input and display orders in Build Apps. After some trial and error, I managed to make it work. Initially, I struggled with nesting, only extracting the schema with "value" from Northwest Orders OData. Thanks for your guidance and suggestions—they were very helpful! and I truly appreciate.

[Dan_Wroblewski · Accepted solution]

No worries, and no reason to explain. I'm glad I can help on your journey. Please continue to ask questions -- that is what the community is for. Your post shows SAP has to do a better job of explaining how to use the product.