How can we help you?

Delete Custom Offer Field in Dependencies

2_line.png

Unlike removing a custom offer field dependency, which dissolves the relationship between parent and child custom offer fields, deleting a custom offer field deletes the field from your organization. Despite this difference, deleting a custom offer field that is part of a dependency will impact the integrity of any dependencies your organization has configured with that field.

In this article we will cover the various situations and outcomes that can arise when deleting  a custom offer field that is part of a dependency.

 

Delete Child Custom Offer Field in Dependency

In Parent/Child Dependency

If the deleted custom offer field is a child in a parent/child dependency, any configured dependency between the parent and child custom offer field will be dissolved.

Screen_Shot_2020-01-29_at_1.16.35_PM.png

In Nested Parent/Child Dependency

If the deleted custom offer field is the last child in a nested parent/child dependency (i.e. grandparent/parent/child), any configured dependency between the child and its immediate parent custom offer field will be dissolved. The dependency between the first two levels of the nested dependency (i.e. grandparent/parent) will be preserved .

Screen_Shot_2020-01-29_at_1.18.19_PM.png

 

Delete Parent Custom Offer Field in Dependency

In Parent/Child Dependency

If the deleted custom offer field is a parent in a parent/child dependency, any configured dependency between the parent and child custom offer field will be dissolved.

Screen_Shot_2020-01-29_at_1.21.52_PM.png

In Nested Parent/Child Dependency

If the deleted custom offer field is a parent in a nested dependency (i.e. grandparent/parent/child), the entire nested dependency will be dissolved. This happens because the deleted custom offer field dissolves any link between the primary and tertiary custom offer fields (i.e. there is no pathway from the grandparent to the child custom offer fields).

Screen_Shot_2020-01-29_at_1.22.13_PM.png