Introduction

To simplify, when this documentation refers to Products it’s actually refering to Product Versions.

The Attributes it’s the lowest level configuration element for a Product Version. It’s in the attributes where the user/system can set specific values for specific product properties, for instance: the color, the height, the brand, etc.

Attributes are related, and only related, to products. However, you must keep in mind that a Product’s Component it’s also a Product, so we can say that you can also add attributes to a component.

The main Attributes features are:

• Different Data Types: Text, Decimal, Integer, Date, Time, Datetime, Checkbox, Toggle, Picklist, etc.
• Default value by Attribute definition.
• Validation Rules

Data Model

The Attribute is a standalone object which holds the deffinition for the corresponding product property.

On the other hand, when you assign an attribute to a Product it creates a relationship between the specified Product and Attributes (Product_Attribute_Assignment__c).

ADD DIAGRAM

Attributes and Versions

The attributes are setup at Product Version, not at Product level. This is because a Product can have different attributes depending on the Version.

It’s also important to remark that the attributes don’t have a versioning functionality, so when you edit an attribute those changes will be applied to any product version having that attribute.

Attributes Data Types

The Attributes can be of different Data Types:

Picklist Domain Items

When you define an attribute as a Picklist you need to add as many Attribute Domain Items as you desire to the picklist in the Attribute Definition record page.

Keep in mind that when you add a value you can add both the Name and the Value. Note that the attribute value will be the one considered in formulas or any other logic. The Name it’s just the literal to show in the user interface.

At this moment, the item Names cannot be translated but it’s in the roadmap to add multilingual support.

At some point, the Name field will be considered the internal code / value, and new Field called Visible Name (or similar) will be the one used to show in the User Interface, as right now it’s not intuitive.