ODATA $select= parameter

Hello experts,

Using ODATA one can easily access complete objects from SAP backend systems such as SAP Business One Service Layer.

However, in AppGyver there doesn’t seem to be a property available to define the object properties to be returned. In ODATA calls these are indicate by the $select query parameter.

This makes ODATA calls unfortunately unnecessarily slow, because the full object record is always returned. In our typical use case the speed and bandwidth improvement would be about 5 to 10 times faster/smaller.

Am I right in this assumption and could this be added in the future?

Thanks and best regards,


If you are using REST API you can simply add $select as a query parameter. In the OData Configurator it is already there (selected fields), at least for SAP Cloud for Customer.

Hello @Atakan_Tokgoz ,

Thanks for pointing this one out. I hadn’t given it much attention because it is located under the “Test” tab. Does this actually propagate to all subsequent calls? I was under the impression it is just for testing…

Could this parameter be set for each call instead?



Hello @Atakan_Tokgoz ,

I tried this a little more, here’s what I found with my tests:

  • The UI is there, but it is not applied to the calls executed with the “Run test” button
  • The selected fields are not even persisted when choosing “Save Data Resources”
  • The selected fields are not applied to any calls executed from the app

So it definitely seems to be “work in progress” from my point of view.

I submitted a feature request for this in the meantime: OData $select parameter support | Voters | AppGyver

Are you sure these parameters are actually applied to your C4C calls?

Best regards,


Just checked the data variables, you’re right!
I haven’t encountered this issue because I am using the rest data source and put the select as static value.
It definitely should be added to OData Integration though. Voted!


I am facing similar issue, I need a select parameter on ODATA API for C4C.
Has anyone figured a workaround?