Field and group dependencies

What are dependencies?

A dependency is created between two elements when one needs the other to function properly. In your account, some features like dynamic groups, templates, drafts, campaigns, forms and scenarios may be dependent on custom fields and groups.

Here are some examples of dependencies:

• A dynamic group is dependent on a custom field that is present in the group’s criteria.
• A subscription form is dependent on the group it’s linked to.

There are two types of dependencies: major and minor.

Major dependency

Major dependencies are links that cannot be broken, otherwise the dependent features will stop working in a significant way. If we take the example of the dynamic group: if a custom field used in the group's criteria no longer exists, it can no longer update and list the contacts properly. It is therefore impossible to delete custom fields and groups with major dependencies. You will need to resolve the dependency first before you can remove these items. Learn how to eliminate dependencies>

Custom fields have major dependencies when they are found in:

• the criteria of a dynamic group
• an active scenario or a scenario under construction (marketing automation)

Groups have major dependencies when found in:

• the criteria of a dynamic group

• an active scenario or a scenario under construction (marketing automation)

• a subscription form

Minor dependency

There can also be minor dependencies between custom fields and certain features. For example, when a custom field’s variable is inserted into the body of an email it’s considered a minor dependency. Unlike major dependencies, it is possible to delete a custom field with a minor dependency, as the consequences will be less significant. If you choose to delete the field, a warning will appear to display a list of all the dependencies. You can review the items listed before confirming your choice.

Custom fields have minor dependencies when:

• their variable is inserted into: a template, a draft, a scheduled campaign or a campaign that is part of a marketing automation scenario
• they are added to a subscription forms (hosted or iframe)

How to view the dependencies of fields and groups

For groups

Open the Groups menu. Groups that have dependencies* have a link icon at the right-hand side of their row. Click on the icon to find out which element, or elements depend on this group.

* All group dependencies are major.

For custom fields

Go to Icone Settings > Custom fileds.
Custom fields with dependencies have a link icon to the right of their row. Click on the icon to find out which element or elements depend on this group and whether the dependencies are major and / or minor.

How to remove a dependency

To remove dependencies you can:

• Modify the dependent element
  For example, to be able to delete a custom field present in a dynamic group’s criteria, you must first modify this group and remove this as a criteria.
  
  Click on the links below to learn how to edit:
  a dynamic group >
  a template >
  a draft >
  a scheduled mailing >
  a subscription form >
  a scenario >
   
• Delete the dependent element
  For example, if you want to delete a group linked to a subscription form that is no longer being used. You can delete the form first, which will remove the dependency. You can then delete the group.
  
  Click the links below to learn how to delete:
  a dynamic group >
  a template >
  a draft >
  a scheduled mailing >
  a subscription form >
   
• Archive the dependent item

  Since you cannot edit an active scenario, the only way to undo a dependency between the scenario in question and a custom field or group, is to archive it. It's also possible to remove a dependency with a scenario under construction the same way.

  Learn how to archive a scenario >