Restrictions on Effective Start and End Dates for Territory Nodes

For many situations, good practice is to keep all the end dates the same (or blank) for the territory nodes in your hierarchy.

There are various restrictions related to start and end dates on territory nodes. These restrictions are designed to:

• Maintain data integrity by not allowing expired nodes to be edited or deleted

• Prevent orphan nodes by not allowing parent nodes to expire before their children

Some of these restrictions are:

• You can only edit a record if the end date is in the future.

• You cannot delete active or expired territory nodes. You can only delete nodes where the start date is in the future.

• You cannot set a parent node to expire before its children. The end dates for the children are automatically changed to match the parent’s end date.

• You cannot have two nodes for the same territory with overlapping dates. The start date for second node must be on or after the end date of the first node.

For information about configuring start and end dates for nodes, see Configuring End-Date Behavior for Territory Nodes.