An embedded object is a simplified custom object created within (or embedded in) another custom object. They are similar to child custom objects, but have fewer capabilities.

A child object is a custom object in a hierarchical relationship with another custom object. It has all the functionality of a custom object (such as wizards, rules, assignees, and phases), and has a dynamic life cycle and workflow.

An embedded object has a hierarchical relationship with a custom object, but does not have workflow or a dynamic life cycle. Embedded object records are best suited for static information—information that is not likely to change as the parent record moves from phase to phase.

Embedded objects do not have a workflow or dynamic life cycle. As outlined in the Properties of Embedded and Child Object table, you cannot define phases, assignees, or rules in embedded objects. They are best suited for information that is not likely to change as the parent record moves from phase to phase. Because the information is owned by the parent record, it is not relevant to other records.

The following table compares embedded objects and child objects in key functional areas.

Properties of Embedded and Child Objects