eQuipAPI

GetRelatedFieldDataForLazyLoadUsingMappingFieldID

The following routes are available for this service:
All Verbs	/GetRelatedFieldDataForLazyLoadUsingMappingFieldID

**GetRelatedFieldDataForLazyLoadUsingMappingFieldID** Parameters:
Name	Parameter	Data Type	Required	Description
UserID	query	string	No
FieldID	query	int	No

**RelatedFieldLazyLoadDataResponse** Parameters:
Name	Parameter	Data Type	Required	Description
FieldCollection	body	List<RelatedFieldLazyLoad>	No

**RelatedFieldLazyLoad** Parameters:
Name	Parameter	Data Type	Required
ID	body	int	No
FilterName	body	string	No
AssetMappedFieldID	body	int	No
FilterNameForAssetMappedFieldID	body	string	No

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

<GetRelatedFieldDataForLazyLoadUsingMappingFieldID xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/eQuipModel">
  <FieldID>0</FieldID>
  <UserID>String</UserID>
</GetRelatedFieldDataForLazyLoadUsingMappingFieldID>

HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length

<RelatedFieldLazyLoadDataResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/eQuipModel">
  <FieldCollection>
    <RelatedFieldLazyLoad>
      <AssetMappedFieldID>0</AssetMappedFieldID>
      <FilterName>String</FilterName>
      <FilterNameForAssetMappedFieldID>String</FilterNameForAssetMappedFieldID>
      <ID>0</ID>
    </RelatedFieldLazyLoad>
  </FieldCollection>
</RelatedFieldLazyLoadDataResponse>