Developer Q&A
WO not creating for clean request
We are generating WO from our application using corrigo credentials. We were able to create all request(maintenance/clean) until your last upgrade. there you had requested us to change the SubTypeId to 259 from 4. After these changes, we are able to create WO for maintenance requests only not clean requests.
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:int="http://corrigo.com/integration/">
<soap:Header>
<int:CorrigoNetOptions>
<int:ImposeConcurrencyId>false</int:ImposeConcurrencyId>
<int:UpdateLastModified>true</int:UpdateLastModified>
<int:CanDeleteMissingEntity>false</int:CanDeleteMissingEntity>
<int:LockOnDataRetrieval>Default</int:LockOnDataRetrieval>
</int:CorrigoNetOptions>
</soap:Header>
<soap:Body>
<int:Execute>
<int:commandRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="int:WoCreateCommand">
<int:WorkOrder>
<int:TypeCategory>Request</int:TypeCategory>
<int:SubType>
<int:Id>259</int:Id>
</int:SubType>
<int:Priority>
<int:Id>1</int:Id>
</int:Priority>
<int:Customer>
<int:Id>144</int:Id>
</int:Customer>
<int:ContactName>Janitor</int:ContactName>
<int:ContactAddress>
<int:AddrTypeId>Contact</int:AddrTypeId>
<int:Address>214-555-5555</int:Address>
</int:ContactAddress>
<int:Items>
<int:WoItem>
<int:Asset>
<int:Id>48132</int:Id>
</int:Asset>
<int:Task>
<int:Id>20351</int:Id>
</int:Task>
<int:Comment>Location/Column ID/Cubicle Number : TestingBuilding_TestingFloor1_MensRestRoom Describe your problem in detail : Toilet Not Flushing</int:Comment>
</int:WoItem>
</int:Items>
</int:WorkOrder>
<int:ComputeSchedule>true</int:ComputeSchedule>
<int:ComputeAssignment>true</int:ComputeAssignment>
</int:commandRequest>
</int:Execute>
</soap:Body>
</soap:Envelope>
Above request is created WO and we can see that in Work Orders List page but
if I change the AssetId(Clean) and TaskId(Toilet) like below,
<int:Asset>
<int:Id>48163</int:Id>
</int:Asset>
<int:Task>
<int:Id>22193</int:Id>
</int:Task>
it gives an error,
0EmployeeIDSystem.IndexOutOfRangeExceptionBut we are able to create a clean request manually in the dashboard and it gives the same AssetId and TaskId.
Please help us to solve this issue.