eQuipAPI

AssociateTransactionAttachmentsToAssets

Associates transaction's attachments to the assets. Requires a valid userid to authorize the caller to complete this request.

The following routes are available for this service:
POST	/workflows/{WorkflowID}/transactions/{TransactionID}/assets/associate-attachments	Associates transaction's attachments to the assets.

**AssociateTransactionAttachmentsToAssets** Parameters:
Name	Parameter	Data Type	Required	Description
UserID	query	Guid	Yes	The Api key that authorizes the caller to complete the request. Contact your eQuip admin.
WorkflowID	path	Guid	Yes	The workflowid uses to check the configuration for `Associate an attachment to assets within a transaction`.
TransactionID	path	int	Yes	The transactionid uses to get the assets and its attachments.
TransactionTableID	query	int	Yes	The transactiontableid uses to associate transaction attachments to the assets.
TransactionTableName	query	string	Yes	The transactiontablename uses to get the assets from transaction detail.

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

<AssociateTransactionAttachmentsToAssets xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/eQuipModel">
  <TransactionID>0</TransactionID>
  <TransactionTableID>0</TransactionTableID>
  <TransactionTableName>String</TransactionTableName>
  <UserID>String</UserID>
  <WorkflowID>String</WorkflowID>
</AssociateTransactionAttachmentsToAssets>

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

<boolean xmlns="http://schemas.microsoft.com/2003/10/Serialization/">false</boolean>