integration_documentation:request
Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
integration_documentation:request [2019/05/22 15:18] fe80:c3d7:1f3e:2181:6345:72ce:e0c6:d356 ↷ Links adapted because of a move operation |
integration_documentation:request [2019/07/04 14:09] florian [Values of the ''order'' parameter] |
||
---|---|---|---|
Line 90: | Line 90: | ||
==== Values of the ''order'' parameter ==== | ==== Values of the ''order'' parameter ==== | ||
- | The values //dynamic// and //ASC/DESC// can be added to every value listed below, f.e.: //salesfrequency dynamic DESC//. | + | The values //dynamic// and //asc/desc// can be added to every value listed below, f.e.: //salesfrequency dynamic desc//. |
- | The values //ASC/DESC// are specifying whether to sort the results ascending (ASC) or descending (DESC). | + | The values //asc/desc// are specifying whether to sort the results ascending (asc) or descending (desc). |
- | The value //dynamic// is calculating the specified value in a dynamic way and does not sort the results hard. This means that the textual relevance is still influencing the sorting. | + | <note>The values //asc/desc// have to be transmitted in lowercase</note> |
+ | |||
+ | The value //dynamic// is calculating the specified value in a dynamic way and does not sort the results hard. This means that the textual relevance, the configured merchandising features and boosting via the personalization API is still influencing the sorting. | ||
**We strongly advise our customers to use a dynamic calculation for the default order. ** | **We strongly advise our customers to use a dynamic calculation for the default order. ** |