Last Updated Date Utc
LastUpdatedDateUtc changes when different types of changes occur on an order, at multiple places in the order.
The table below provides context for what changes may occur to update this date. The REST API is changing regularly and new properties that could drive a change in this date can be introduced in the future.
Use-Cases / Best Practices
Retrieving orders updated recently (on a rolling basis) - looking for orders with updates in the last 4 hours
- Example: GET ge ‘<MovingDateWindow>’
ChannelAdvisor strongly advises use of the exported=true parameter to ensure results do not include orders the destination system does not already know about.
- Note: this is predicated on the idea an existing integration is marking orders as exported today.
Workflow Example to Check on 15 Minute Interval
- First Request: GET https://api.channeladvisor.com/v1/Orders?exported=true&$filter=UpdatedDateUtc ge ‘2022-03-09T00:00:00.0000Z’
- Second Request: GET https://api.channeladvisor.com/v1/Orders?exported=true&$filter=UpdatedDateUtc ge ‘2022-03-09T00:15:00.0000Z’
- Next Request: GET https://api.channeladvisor.com/v1/Orders?exported=true&$filter=UpdatedDateUtc ge ‘<insert last date/time + 15 minutes>’
What Changes the LastUpdatedDateUtc?
|Order Entity / Area||Change Description|