Query parameters in SAP BTP Destination REST API integration using Classic Data Entities

Raj_Pawan_Gumdal · February 28, 2023, 4:49pm

Hi all,

There is a provision for query parameters on an URL endpoint when we build direct REST API integration using Classic data entities:

This query parameter can be set in the data variable and it can be dynamic in nature too:

However, the same is missing when it comes to REST API integration via BTP Destination using Classic data entities:

I have the following queries:

Is there a plan in roadmap to make provision for Query parameters in Classic data entities using BTP destinations?
Is there any workaround at the moment to achieve the same in existing infrastructure?

Thanks.
Raj Pawan Gumdal

James_Rapp · March 1, 2023, 4:15pm

Hi Raj,

You can use a Data Query property for this. First, set the query in your resource to one of the pre-defined properties, such as query.search.query:

Once you save it, the property will be available in your get record flow node:

Of course, you can make the value dynamic based on app or page variables instead. This should work for your scenario.

Raj_Pawan_Gumdal · March 2, 2023, 11:50am

Thank you @James_Rapp. This worked perfect

Slade_Rose1 · August 21, 2023, 1:55pm

Hi James, we had the same question and your explanation solved it, but we are trying to do this for a GET record, not a collection. Is there a way to tweak it to work for returning only one record? Thanks in advance

James_Rapp · August 22, 2023, 5:49pm

Hi @Slade_Rose1 - can you elaborate a little bit? Normally with a GET record you have the key value already and don’t need the query string. Is this also for a REST API or OData? What kind of parameters are you trying to pass?

Slade_Rose1 · August 25, 2023, 8:11am

Thanks for your response, James. It’s an SAP BTP Destination, I think OData, and the URL we’re calling for this destination looks like this: https://example.accounts.ondemand.com/scim/Users?filter=userName eq “example@gmail.com”

I get the key value from an input field in the app that serves as the variable to populate the parameter for userName, but when I run the GET I want to do a GET record not a GET record collection. However, the query.search.query that you proposed doesn’t seem to work for a single record, or it seems I don’t have the option to use that for a GET record. I hope I am making sense? Please let me know if you need screenshots or something else?