The following figure shows the completed hierarchy for the example:

Load all your records into

CC360

. Do not populate the parent account values. After you load the records into

CC360

, the records are not part of a hierarchy and the records do not have relationships.

The following figure shows the lack of hierarchy structure among the records at this point in the process:

After you load the records, use an external tool such as Informatica Cloud Services to populate the parent account values. First update the parent account value for the nodes in the second hierarchy level. You do not need to update the parent account value for the root node because the root node does not have a parent. The parent account value for the root node remains null. The following table shows the parent account values to populate when you update the values for hierarchy level 2:

Node ID	Parent Account value
002	001
003	001
004	001
005	001
006	001
007	001

The following figure shows the hierarchy structure at this point in the process:

After you update the values for hierarchy level 2, update the values for hierarchy level 3. The following table shows the parent account values to populate when you update the values for hierarchy level 3:

Node ID	Parent Account value
008	005
009	005
010	005

The following figure shows the hierarchy structure at this point in the process:

After you update the values for hierarchy level 3, update the values for the root node in hierarchy level 4. The following table shows the parent account value to populate when you update the values for hierarchy level 4:

Node ID	Parent Account value
011	010
012	010

The hierarchy is complete. The following figure shows the completed hierarchy: