<back to all web services
SetOrUpdatePositionsToFix
The following routes are available for this service:| All Verbs | /SetOrUpdatePositionsToFix | | |
|---|
SetOrUpdatePositionsToFix Parameters:| Name | Parameter | Data Type | Required | Description |
|---|
| LedIssue | query | LedIssue | Yes | Led issue object |
LedIssue Parameters:| Name | Parameter | Data Type | Required | Description |
|---|
| ID | form | int | No | |
| ReservedDateTime | form | int | No | |
| AreaID | form | int | No | |
| PositionKey | form | string | No | |
| Note | form | string | No | |
| Owner | form | string | No | |
| Reason | form | LedIssueReason | No | |
| Status | form | LedIssueStatus | 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 /SetOrUpdatePositionsToFix HTTP/1.1
Host: webadmin.clouddemo2.pickeos.com
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<SetOrUpdatePositionsToFix xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/GoToLightAPI">
<LedIssue>
<AreaID>0</AreaID>
<ID>0</ID>
<Note>String</Note>
<Owner>String</Owner>
<PositionKey>String</PositionKey>
<Reason>UNKOWN</Reason>
<ReservedDateTime>0</ReservedDateTime>
<Status>NULL</Status>
</LedIssue>
</SetOrUpdatePositionsToFix>