When creating a service object connection to a REST API, Complex object types should be able to be handled.

For example, if I have an endpoint that returns the Request object below:

public class Request

{

public int RequestId { get; set; }

public RequestClient Client { get; set; }

}

public class RequestClient

{

public int ClientId { get; set; }

public string ClientName { get; set; }

}

The way the REST connection works currently, the Request.Client property gets returned as a messy string displaying the type information, thereby never allowing me to access the properties on the RequestClient object unless I flatten the structure to include the ClientId and ClientName on the Request object.