Overview
- Avoid overriding menu attributes at lower levels in the product hierarchy.
-
Overriding of AVP attributes is not possible at lower level; Attributes cannot be overridden at the lower level to include static pricing.
All AVP features must be set up at the level where the attribute was created.
-
Use the Set Properties tab to define array attributes and easily change association to other sets.
This tab appears only when the configuration attribute is of the type: Array.
- Don't have displayed information be case sensitive or be a condition for a rule (for example, Part Numbers).
- Have as few attributes "auto-update" as possible.
- The more Attributes that exist in a flow, the slower the performance.
-
Define Attributes at the level in which they are applicable.
If two entities in a level use the same Attribute, move the Attribute to the parent level; if the Attribute is used in multiple models, define it at the Product line.
- Limit the length of an Attribute variable name.
Note: Customers should not use any of the following names for Configuration attribute variable names. Using these values may cause issues with customer configurations and could possibly alter site functionality.
- action_id
- bm_cm_process_id
- _bom_
- bs_id
- commerce_doc_url_params
- commerce_list_id
- document_id
- document_number
- folder_id
- formaction
- from_config
- scrollTop
- shopping_cart_id
- step_id
- token
- version_id
- Single select attributes cannot be displayed as radio buttons for use in sets.
-
An array attribute cannot be of multi-select menu type.
In the Attribute Editor, if you choose the attribute type as a multi-select menu and then select the array type option, then the attribute will automatically change to text-field.
- Once you define an attribute as an array, you can't change it to a non-array attribute.
- You can create configuration attributes with the same label name, though the variable names must be unique.
- The Image Menu option is not available for non-text menus.
-
Image menu attributes can be used in Configuration Rules and BML.
For example, the label can be used in all Simple Conditions while the variable name of the menu value is used to define BML rules. Rule messages will show menu values as text and not images.
- Bulk Upload and Download of Image Menus are supported.
-
Menu values selected in configuration are carried to commerce as text.
The image URL is not available in the sub-document and can't be rendered in the main document or the sub-document.
-
Image Menus are not available as Dynamic Data in the Main Document Rich Text Editor.
For sub-document RTE, Image Menus can be added as dynamic data to the template. However, if the image tag is chosen, then the URL will be printed as text and the image will not be rendered.
-
Before beginning with Image Menus, it is recommended that you update the Configuration Stylesheet. Navigate to the Regular Stylesheet List page.
Navigate to the Regular Stylesheet List page.
- Click Admin to go to the Admin Home Page.
-
Click Catalog Definition in the Products section.
The Supported Products page opens.
-
Confirm that Stylesheets is listed in the Navigation column, and click List.
The Regular Stylesheet List page opens.
