Symptom
In *-items,xml, if a relation item type is defined like:
<relation code="CarouselComponent2CarouselSubComponent" generate="true" localized="false" autocreate="true"> <description>This relation links CarouselComponent with one or more CarouselSubComponents. </description> <sourceElement qualifier="carouselComponent" type="CarouselComponent" cardinality="one"> <modifiers read="true" write="true" search="true" optional="true"/> </sourceElement> <targetElement qualifier="carouselSubComponents" type="CarouselSubComponent" cardinality="many" > <modifiers read="true" write="true" search="true" optional="true"/> </targetElement> </relation> |
In the "targetElement", there is no such ordered attribute in above definition, so by default ordered is set to "false", which means this target element type is NOT ordered.
Therefore, for this case, this one-to-many relation item will be displayed in a store front; but no matter how customer changed the order of the target element of "CarouselSubComponent" in this relation item type, the order is never changed, it still shows the same.
Read more...
Environment
all version of SAP hybris commerce suite
Product
SAP Commerce all versions
Keywords
relation type, cardinality, items.xml, relation type , KBA , CEC-COM-CPS-COR , SAP Commerce Core , How To
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.