Defining Attribute Value Linking
For relationship types that have been defined as link relationship types, you can use attribute value linking to automatically propagate updated attribute values on a given product to any products that are linked to it.
As with attribute transfer property settings, custom property settings for attribute value linking must be entered in the attributesTransfer.properties file, which is found in the codebase.
You can only propagate attribute values for the
LCSProduct and
LCSSeasonProductLink type classes. See
Defining Attribute Transfer Values for related property setting values for type classes and names.
Attribute value linking defined for attributes on the LCSSeasonProductLink type class only links the product-season attributes if the season of the linked products is the same. For example, if product A is on season Spring 2008, and is linked to product B on season Spring 2009, only the product attribute values are linked; the season must be the same for both product A and B for product-season attribute values to be linked.
Likewise, if product A and product B are each on five seasons, but only share season Winter 2010, then only the product-season attributes for Winter 2010 have linked values.
Out-of-the-Box
No relationship types exist out-of-the-box. No attribute value linking is defined.
Configuration
To configure attribute value linking, you must enter a property setting for each attribute.
The basic form of the property setting to control value linking is:
SYNC.<TypeClass>^<TypeName>^<RelationshipTypeName>^<AttributeTypeContext>^<AttributeKey>>
Each property setting entry is separated by a caret (^).
|
|
The <AttributeTypeContext> entry is required only for product and season objects, as this object can exist on both the Product and Colorway types. Attribute context types must be entered in all capital letters, either as PRODUCT or SKU.
|
If the property setting does not reference the product-season object, then you must omit the <AttributeTypeContext> entry, but still enter all carets. The resulting property setting contains two side-by-side carets following the <RelationshipTypeName> entry.
The indication of a specific relationship type, such as Missy-Petite must be present in this property setting. The following is an example property setting:
SYNC.com.lcs.wc.product.LCSProduct^Product^Missy-Petite^^department>
In the example above, the system automatically propagates the department attribute on the Product type class on the Product type when products are linked using the Missy-Petite relationship type. The value of the parent attribute is propagated to all linked children attributes that are linked using the Missy-Petite relationship type
The following example is a property setting that includes a <AttributeTypeContext> entry:
SYNC.com.lcs.wc.season.LCSSeasonProductLink^Product^Missy-Missy^PRODUCT^designer
This property setting tells the system to propagate the designer attribute on the Product type on the LCSSeasonProductLink type class when the Missy-Missy relationship type is selected. The value of the parent designer attribute is propagated to all linked children attributes that are linked using the Missy-Missy relationship type.
