ODATA service : access IO_DATA_PROVIDER in GET_EXPANDED_ENTITY_SET

[Former Member]

Hi All,

My requirement is to use READ_ENTRY_DATA in GET_EXPANDED_ENTITYSET method. Can anybody help me out.

Thanks.

[Andre_Fischer]

There is no read_entry_data if you perform an expand yourself.

This might only happen if you try to perform a deep insert.

There are numerous blogs around how to handle $expand.

For example:

https://blogs.sap.com/2014/11/24/multi-level-expansion-with-getexpandedentityset/

Regards,

Andre

[Former Member]

Hi Andre,

Thanks for the answer. What if we need to pass Sales org and DIst channel combination records in GET_EXPANDED_ENTITYSET. Is there any way ?

[Andre_Fischer]

Please provide more details to your question. This way there is nothing I answer. How does your OData service look like?

[Former Member]

Hi Andre

I am planning to fetch DEEP entity data within GET_EXPANDED_ENTITYSET method using method IO_DATA_PROVIDER->READ_ENTRY_DATA like we do in CREATE_DEEP_ENTITY methods.

Input to the GET_EXPANDED_ENTITYSET methods will be be same as that of CREATE_DEEP_ENTITY method i.e. JSON Paylod.

My issue is IO_DATA_PROVIDER is not importing parameter in GET_EXPANDED_ENTITYSET method signature. So input payload in JSON format is not accessible in GET_EXPANDED_ENTITYSET methods.

[Andre_Fischer]

You have not understood the purpose of the GET_EXPANDED_ENTITYSET method.

It is for read only and thus accepts no input parameters.

[Former Member]

Can't we fetch data using FOR ALL ENTRIES. I 🙂

How internal table can be passed as input in GET_EXPANDED_ENTITYSET method.

[Andre_Fischer]

Please accept that there is no way and have a look at the OData specification.

http://www.odata.org/documentation/odata-version-2-0/uri-conventions/

You can only filter the data that is requested.

[Andre_Fischer]

There is no read_entry_data if you perform an expand yourself.

This might only happen if you try to perform a deep insert.

Regards,

Andre