xml_export_documentation:xml_format
Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Last revision Both sides next revision | ||
xml_export_documentation:xml_format [2023/01/18 16:45] rihad [Overview] |
xml_export_documentation:xml_format [2023/01/25 14:14] rihad [Using properties for product variants in search results] |
||
---|---|---|---|
Line 691: | Line 691: | ||
---- | ---- | ||
+ | ==== Using variants in search results ==== | ||
+ | <code xml> | ||
+ | [...] | ||
+ | <variants> | ||
+ | <variant id="variant_3"> | ||
+ | ... | ||
+ | </variant> | ||
+ | <variant id="variant_4"> | ||
+ | ... | ||
+ | </variant> | ||
+ | </variants> | ||
+ | [...] | ||
+ | </code> | ||
+ | |||
+ | A **<variant>** can contain the following data. This data is structured the same as for its parent. | ||
+ | |||
+ | * ordernumber, required | ||
+ | * attributes, required | ||
+ | * name, optional | ||
+ | * price, optional. In case it is not set, the parent price will be used as default. | ||
+ | * groups, optional. | ||
+ | * overriddenPrice, optional | ||
+ | * properties, optional | ||
+ | |||
+ | <note important>No other fields are allowed.</note> | ||
+ | |||
+ | <note tip>Currently it is not possible to use variants and usergroups together. | ||
+ | Variants only work without usergroups. But using groups is still possible. So filtering by group is working fine.</note> | ||
==== Example XML ==== | ==== Example XML ==== | ||