eQuipAPI

<back to all web services

GetMappingTableDetail

The following routes are available for this service:
All Verbs/GetMappingTableDetail
GetMappingTableDetail Parameters:
NameParameterData TypeRequiredDescription
UserIDquerystringNo
TableNamequerystringNo
MappingTableDetailResponse Parameters:
NameParameterData TypeRequiredDescription
TableTypebodystringNo
PrimaryKeyFieldNamebodystringNo
FieldsbodyList<MappingTableFieldDetail>No
MappingTableFieldDetail Parameters:
NameParameterData TypeRequiredDescription
FieldNamebodystringNo
FieldTypebodystringNo
FieldTypeIDbodyshortNo

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/GetMappingTableDetail HTTP/1.1 
Host: equipstage3.e-isg.com 
Content-Type: application/xml
Content-Length: length

<GetMappingTableDetail xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/eQuipModel">
  <TableName>String</TableName>
  <UserID>String</UserID>
</GetMappingTableDetail>
HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length

<MappingTableDetailResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/eQuipModel">
  <Fields>
    <MappingTableFieldDetail>
      <FieldName>String</FieldName>
      <FieldType>String</FieldType>
      <FieldTypeID>0</FieldTypeID>
    </MappingTableFieldDetail>
  </Fields>
  <PrimaryKeyFieldName>String</PrimaryKeyFieldName>
  <TableType>String</TableType>
</MappingTableDetailResponse>