Cert++
Close

Custom objects versus custom attributes on system objects

Key Takeaway

If the data describes something B2C Commerce already models, add a custom attribute to that system object. Create a custom object only when the data is especially complex or doesn't belong to any existing system object. Custom object attributes can't be used in search refinement.

B2C Commerce stores storefront data in business objects. System objects, such as Product, Basket, and CustomerAddress, come with the platform. You can add custom attributes to them. Custom objects are new object types that you define yourself for data that has no natural home. Salesforce recommends using custom objects only when extending a system object won't work. The choice matters because custom objects can significantly impact overall performance, and custom object attributes can't be used in search refinement.

System objects and custom objects

Business objects define the structure of storefront data. System objects come with the platform. They already cover most of the data a storefront needs, such as product details, content, orders, and promotions.

You can add a custom attribute to a system object to store extra data on it. Custom objects are object types that you add yourself. Custom objects require custom code.

B2C Commerce Developer Study Guide

Checklist progress

0/237Learned

Given a business need to store custom data, determine if a custom object is needed and create and configure as required

0/5

Prepare for the Exam

Play Today's Certle

Study Community

Ask questions and get the latest info from other B2C Commerce Developer studiers. 796 members and growing.