Removing a custom offer field dependency dissolves the relationship between parent and child custom offer fields, but keeps both fields in your organization.
Archiving a custom offer field removes the field from your organization and often dissolves the relationship between the two fields. Archiving a custom offer field that is part of a dependency will impact the integrity of any dependencies.
Archive child custom offer field with a dependency
Archiving the child field in a standard dependency
If the archived 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.
Example: Archiving the Equity field removes the relationship between Benefits and the (archived) Equity field. The Benefits field will still exist.
Archiving the child field in a nested dependency
A nested dependency contains more than two layers of hierarchy. For example, if your Hourly Pay Rate field is dependent on the Payment Type, which is dependent on the Employment Type, it is considered a nested dependency.
If the archived custom offer field is the last option in the list, any configured dependency between the child and its immediate parent custom offer field will be dissolved.
The dependency between any higher levels of the nested dependency will be preserved.
Example: Archiving Hourly Pay Rate will dissolve the relationship between Payment Type and Hourly Pay Rate, but keep the relationship between Employment Type and Payment Type.
Archive a parent custom offer field with a dependency
Archiving the parent field in a standard dependency
If the archived 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.
Example: Archiving Benefits will dissolve the relationship between the Benefits and Equity field. However, the Equity field will still exist.
Archiving the parent field in a nested dependency
If the archived custom offer field is a parent in a nested dependency, the entire nested dependency will be dissolved. However, any subordinate fields will still exist and can be assigned to new hierarchies.
Example: Archiving Employment Type dissolves both the relationship between Employment Type and Payment Type, as well as the relationship between Payment Type and Hourly Pay Rate. However, both the Payment Type and Hourly Pay fields will still exist.