QUESTION: How to use $Expand on POST reqeusts

[unchase]

QUESTION: How to use $Expand on POST reqeusts

[ChrisSchaller]

I have this requirement as well, it's not easily supported for actions the same as functions, a work around I used recently was to use BuildingRequest event to inject the additional $filter that I wanted to apply, however the same would work for $expand:

the commented code shows the syntax I was expecting to use.

ClientContext.BuildingRequest += ClientContext_BuildingRequest;
var query = ClientContext.Sensors.ByKey(this.SensorId)
                                 .GetTriggeredSensors(value, this.Timestamp);
       //                        .Where(s => s.VTDisabled == false)
       //                        .Where(s => s.Card.CardType.Driver == cloudVirtualCardDriver);

var items = query.Execute().ToList();
ClientContext.BuildingRequest -= ClientContext_BuildingRequest;

private void ClientContext_BuildingRequest(object sender, Microsoft.OData.Client.BuildingRequestEventArgs e)
{
    if (e.RequestUri.PathAndQuery.Contains("GetTriggeredSensors"))
                e.RequestUri = new System.Uri(e.RequestUri + "?$filter=VTDisabled eq false AND Card/CardType/Driver eq '" + cloudVirtualCardDriver + "'");
}

The issue is that DataServiceActionQuery (that we use to generate calls to Action endpoints, via POST) only accepts BodyOperationParameter as seen in the constructor for DataServiceActionQuery even though internally ExecuteAsync accepts OperationParameter that could be Body or Uri parameters.

On the flip side of this, DataServiceQuery restricts the input to only accept UriOperationParameter so we can't even try to work around this issue by using DataServiceQuery that targets the Action and then forcing the Method to "POST" instead of "GET"

I have raised an issue on the ODataLib project regarding a feature that would make supporting this easier: OData/odata.net#1657