Deep entity search in Get Record Collection in SAP BUILD Apps

[YogSSohanee]

Hello fellow Builders,

I have a seemingly common looking scenario, yet i couldn't find much pointers on the community on this issue. So thought of putting it here to get help. 

I have a build app scenario, where i have a Goods Recipient as a only input available and based on that I have to call MaterialDocumentHeader Api. I am going to pass some other inputs to this API as a FILTER, 4 of them are from the deep entity MaterialDocumentItem of this API and one of them is from the header part. 

I tried to use 2 ways to call this API in Build apps:

1) With S4HANA destination configured in BTP and calling it directly with the below option.

In this case, i see that there are options such as Query parameters and Filter condition, but not sure how to access the deep structure in this case. I have already enabled the Expand item entity option as below:

2) With Create entity -> SAP BTP Destination REST API integration option 

In this case, i am using query.search.query option as rightly suggested by @Dan_Wroblewski , and then gave the SEARCH url with options such as expand and filter like below:

but the moment i access the deep entity attribute such as plant like this, the odata call fails. Any pointers on how these calls should be made with Build apps formulas? Your inputs are highly appreciated. Thanks!

@Dan_Wroblewski, @Venkat_Vyza , any pointers please?

[oumaimachabbar]

Hello I am currently working on the sales offer requests feature in SAP Build Apps. For both GET and POST operations, I followed  https://discoveringabap.com/2022/11/10/building-odata-services-12-handle-deep-structures-using-expan... and https://discoveringabap.com/2022/11/10/building-odata-services-13-create-data-using-deep-entity/ . I’ve successfully set up data retrieval (GET), and I understand the structure required for data creation (POST). However, I need a clear and detailed guide on how to implement the creation (add) functionality for a new offer request in SAP Build Apps using my custom OData service . Specifically, I would like to know how to: Properly structure the data within SAP Build Apps to perform a deep insert (parent with related child entities), Dynamically bind multiple ToItem lines, Correctly trigger the Create Record action with the full payload. Thank you in advance for your support!

[Dan_Wroblewski · Accepted solution]

I'm not an expert here, but from a little research it seems that OData V2 does not allow filtering based on nested property which is 1-to-many. I'm assuming that is your case.

[YogSSohanee · Accepted solution]

Thanks Daniel, forgot to reply back on your post.