For example, if a record belongs to a sales hierarchy, you might organize the hierarchy according to sales territories. A legal hierarchy, on the other hand, might show where the records appear within the financial reporting structure.

When you add a node and its children to a hierarchy of a different type,

Customer 360 for Salesforce

(

Customer 360 for Salesforce

) updates the record hierarchy type to reflect the hierarchy it has become a part of.

Customer 360 for Salesforce

populates the hierarchy type field of child records with the hierarchy type of the ultimate parent. If you edit the hierarchy type of a child record,

Customer 360 for Salesforce

overrides the change with the ultimate parent hierarchy type.

If you clone a node and its children to a hierarchy of a different type, you create a multidimensional hierarchy. The original hierarchy retains its hierarchy type and the clone of the hierarchy updates to reflect the hierarchy that it has become a part of.

Account hierarchies have a hierarchy type of Account. Any hierarchy that is not an account hierarchy is an external hierarchy. The source for account hierarchies is account records, while the source for external hierarchies is records from external data sources such as SAP. The default name for external hierarchies is the source name. You can set the hierarchy type when you load the data into

Customer 360 for Salesforce

.