Moving Accounts

To fine-tune your go to market model, it is often necessary to move things around. For example, you might create and delete territories or move accounts between various segments. During these operations, the changes are reflected in the proposed view.

There are a few scenarios where records are moved from one node to another, such as when:

  1. You add to the hierarchy by creating children under a parent.
  2. You move a record from one node to another.
  3. You delete a node.

Adding to Hierarchy

When you create a new rule based hierarchy (i.e. unique values or bucket based), the records are moved from the parent node to the child nodes.

Proposed View

State

From Node

To Node

in the Child Node

+Added

Parent Node

Child Node

👍

A Parent Node with Children

When a parent node has at least one child (other than the unassigned node), there will be NO records associated at the parent level anymore as all records will either be moved to the children or the unassigned bucket under that parent.

❗️

Missed By the Rules?

When a record at the parent level does not match a rule defined by the add hierarchy operation, those records are added to the "unassigned" node.

Add Custom Node

When you add the first custom node (i.e. not rules based), all records from the parent node are moved to the "Unassigned" node and the newly created custom node.

Proposed View

State

From Node

To Node

in the Unassigned Node

+Added

Parent Node

Unassigned Node

Moving Records From One Node To Another

  1. Select the specific source node where you want to move from in the hierarchy.
  2. Select the record(s) that you want to move from the source.
  3. Click on the "Move" button on the grid. This opens up a
    dialog box for you to select the destination node you want to move the records to.
    You can search for the node you want to move to in the search box.
  4. Search and/or navigate to the destination node.
  5. Next, select how to handle account families
  6. Click "Confirm".

When moving a record from one node ("Source") to another node ("Destination"), the proposed state the following is shown:

Proposed View

State

From Node

To Node

In the Source Node

-Removed

Source Node

Destination Node

Tn the Destination Node

+Added

Source Node

Destination Node

👍

Moving a Record to a Parent Node with Child Nodes

When you select a parent node as the destination for a move of a record, the record will be moved to the unassigned node under that parent.

📘

Initiating Move From Parent Nodes

When you view the data grid with a parent node selected, you will see all the records that are associated to all the children under that parent. This view does not impact the source and destination of the move. The "From" node will be the actual child node the record is associated to.

Moving A Record Multiple Times Before Commit

It is possible that as you fine-tune your go-to-market design that you might move a record multiple times before settling in on the right place to put it. In this case, the "Source" node will always be the last node where the record had a "committed" relationship. The "Destination" node can change as many times before the changes are committed.

For Example:

a. When moving a record from source node "A" to source node "B", the view is as below:

Proposed View

State

From Node

To Node

in Node "A"

-Removed

Node "A"

Node "B"

in Node "B"

+Added

Node "A"

Node "B"

b. You decided that node "B" was not the right place for this record and decide to move the record to node "C". When you do this, the proposed view will show the following:

Proposed View

State

From Node

To Node

in Node "A"

-Removed

Node "A"

Node "C"

in Node "C"

+Added

Node "A"

Node "C"

in Node "B"

nothing will be displayed here

Deleting Nodes

When you delete a node, the records are moved to the unassigned node under the common parent.

Proposed View

State

From Node

To Node

in the Unassigned Node under the same parent as the deleted node

+Added

Deleted Node

Unassigned Node

❗️

Last Child Deleted

When the last child is deleted, all the records are moved into the "Unassigned" node. You can only delete an unassigned node when there are no other children under a parent. When the unassigned node is deleted, the children are moved to the parent node.

👍

Tracking Changes

If you're wondering how to track the movement of accounts within the hierarchy, refer to Tracking Changes for more information.

Updated 5 months ago

Moving Accounts


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.