You are here:
Product Attributes in EPC
Products may or may not have attributes, which you can use in Industries CPQ to customize a product, to filter products to find the right one for customers, or to set pricing for a product.
Products may or may not have Product Attributes. A product that does not have attributes comes only in one form, and customers do not make any decisions about the features of the product. For example, a headset or a computer cord that come in one color.
If a customer can choose from a selection of product features, you must define these features as attributes before creating an object type. Also, if an attribute includes multiple values that a customer can choose from, you must define picklists before defining the attribute.
Product attributes provide a powerful and flexible way to extend product entities. Product attributes are stored in an aggregate JSON blob on the Product object and are used extensively throughout Industries CPQ and Order Management.
In Industries CPQ, you can use product attributes to filter products at runtime, displaying the best fit products to customers. You can use them to configure product specifications, allowing users to specify product colors, sizes, and other options. You can also use attributes to change product pricing using attribute-based pricing rules.
Finally, in Order Management, you can use attributes to map commercial products, or the products that customers see, with technical products that communicate with backend systems to fulfill the products that are purchased.
- Attributes vs. Fields
When defining product properties, you can use attributes or fields. The choice depends on how you plan to implement property data during order capture. - JSONAttribute v2 Schema Upgrade Considerations
The upgraded attribute schema provides multiple performance and storage enhancements. For example, the new schema extracts values from the vlocity_cmt__JSONAttribute__c field into separate fields: Metadata components, default runtime values, and metadata changes. - Encrypted and Not Assetizable Attributes
In Fall '18 and later, attributes for technical products can be set as not assetizable (to identify temporary data) and encrypted (to protect personally identifiable information or similar data). - Fix Duplicate and Empty Attributes in EPC
You can see empty attributes if you create an attribute for the Product2 object type and delete it. This deletion can create an empty attribute assignment under a child object type of Product2. Duplicate attributes can occasionally occur. You can run the following scripts to resolve these issues.
