request |
read for query parameters to be used as search criteria; use any combination of fields from tables:
edistatus - use edistatus or no prefix
customer - use customer prefix
edistatus_profile - use profile prefix
For example, /ediStatus/search?edistatus.partner_id=TESTPARTNER&customer.state_id=AL
would find shipment statuses for partner ID 'TESTPARTNER' where the related customer is located in Alabama.
Sorting: To sort the result set, you can provide the following reserved query parameter: orderBy If the orderBy parameter is not provided a default sort of edistatus.order_id+ASC,edistatus.direction+DESC,profile.partner_name+ASC,edistatus.customer_id+ASC,edistatus.stop_number+ASC,edistatus.xmit_sequence+ASC,edistatus.status_code+ASC will be applied.
For example, /ediStatusr/search?edistatus.partner_id=TESTPARTNER&orderBy=customer.name+DESC would return all edi status records for partner ID 'TESTPARTNER' sorted descending by the customer name. Multiple sort columns can be provided in a comma delimited format. orderBy=prefix.field+direction,prefix.field+direction
Pagination: To page the result set, you can provide the following reserved query parameters: recordLength and recordOffset
For example, /ediStatus/search?edistatus.partner_id=TESTPARTNER&recordLength=100&recordOffset=50 would return 100 records starting at the 51st record in the return record set. If no recordLength parameter is provided the search result maximum value in the mobile service control file will be applied. |
context
|
|
HttpServletRequest
|