To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml
HTTP + XML
The following are sample HTTP requests and responses.
The placeholders shown need to be replaced with actual values.
POST /xml/reply/GetDropDownField HTTP/1.1
Host: equipstage2.e-isg.com
Content-Type: application/xml
Content-Length: length
<GetDropDownField xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/eQuipModel">
<FieldName>String</FieldName>
<FieldUsage>String</FieldUsage>
<ParentFieldInternalID>String</ParentFieldInternalID>
<ParentFieldName>String</ParentFieldName>
<UserID>String</UserID>
<Workflow_configuration_id>String</Workflow_configuration_id>
</GetDropDownField>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length
<GetDropDownFieldResult xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/eQuipModel">
<DropDownFields>
<GetDropDownFieldResultValue>
<DisplayValue>String</DisplayValue>
<InternalIDField>String</InternalIDField>
<ParentFieldInternalID>String</ParentFieldInternalID>
<ParentFieldName>String</ParentFieldName>
<Value>String</Value>
</GetDropDownFieldResultValue>
</DropDownFields>
</GetDropDownFieldResult>