|ofr_price||Price (the grouping when there is a separate field only growing - should always be used as sort of the last condition in the case when we use several sorts at a time)|
|ofr_maxPrice||Max price (only the grouping, and only in the descending direction)|
|trp_depDate||Date of event|
|trp_depCode||Name of departure place / departure|
|obj_category||hotel category ( available from version 2.3 )|
It is possible to provide several parameters separated by a comma, eg:
<conditions> <order_by>obj_xName,obj_tourOp,ofr_price</order_by> ...
Price may be appropriate only to the last field, example of an incorrect order of fields:
<conditions> <order_by>obj_xName,ofr_price,obj_tourOp</order_by> ...
From version 2.1, you can also sort the results in the grouping, however sort results by fields with values that are not fixed for grouped entry, may return inconsistent results, (From version 2.2 this sort will be ignored and in response to the message “Sorting ignored - invalid field for a given group”) example of the wrong question:
<conditions> <group_by>obj_xCode</group_by> <order_by>trp_depDate</order_by> ...
Example of proper use of the sort the grouping (grouped by object and date, sorted by date, object name and price):
<conditions> <group_by>tourOpCodeDate</group_by> <order_by>trp_depDate,obj_xName,ofr_price</order_by> ...
To obtain the reverse order of the results, insert minus, for example (hotels from Z to A):
<conditions> <order_by>-obj_xName,ofr_price</order_by> ...
IMPORTANT You may only receive the results sorted by price in descending order in the grouping, using ofr_maxPrice