Hi Filippo,
when you're developing an oData service using the HCI Web Application, a pre-defined Integration Flow is created for all query operations: https://help.sap.com/viewer/368c481cd6954bdfa5d0435479fd4eaf/Cloud/en-US/585b5af228e74a3bbe434ab83a606609.html
The "script" step could be used to solve your issue. The standard script (automatically created) manage "$top" and "$skip" oData query options coming from the incoming URI , not the "$filter" one. You could append filter parameters to "oDataURI" header parameter with this code snippet:
After that, filter parameters are saved in the message header. The only thing you have to do is using that header parameter in the OData receiver channel:
Manuel Xiccato
Hi, not sure 100% if this is the direction you want to filter, but can you please review the following extract from documentation: https://proddps.hana.ondemand.com/dps/d/preview/93810d568bee49c6b3d7b5065a30b0ff/2015.03/en-US/frameset.html?3b52ea0b3973478094931f399f6c5696.html - section 11 on the page.
Hope this helps, let me know.
All the best.
Pavel
Add comment