The most common scenarios for the 'Data was already modified by another user' error when using WoAssignCommand are: 1. ImposeConcurrencyId = true in header 2. StatusId is included in request and does not match current work order status 3. The work order is in a status that does not allow reassignment As examples for scenario #2, if you wanted to assign work order with id 2548 and the work order was currently in New status: This request would work: false true false Default 2548 2 Primary This request would work: false true false Default 2548 2 Primary New This request would work: false true false Default 2548 2 Primary Unknown This request would return 'Data was already modified by another user' false true false Default 2548 2 Primary Open For scenario #3, you will need to know current work order status in order to know which status change command to call before using WoAssignCommand. If your work orders are assigned to both vendors and users, you will need to know current assignment type as well. As examples: If the work order was assigned to a user and the work order status was InProgress, you would need to call WoPauseCommand to pause the work order before using WoAssignCommand to change assignment. If the work order was assigned to a vendor and the work order was in Open status (meaning the vendor had already accepted the work order in Corrigo Pro) you would need to use the WoRecallCommand to recall the work order before using WoAssignCommand to change assignment. Scott Corrigo Integration Services

WoAssignCommand ActionDate Error