Fields Dependencies help keep your data accurate and provide a customized experience. As your company grows, it adds relevant field connections and flexibility while providing data consistency. 

Note: Data integrity still requires your attention, based on your Dependencies’ rules, to recognize any conflicting data. While Fields Dependencies can assist with inputting correct values, they cannot guarantee the data alignment inside an Employee record.

How to set up a dependency between two employee fields

Note: Before you begin, make sure you Set up employee fields.

Step 1: Details

  1. From the left menu, select Settings > Employee fields.
  2. Select the Dependencies tab.
  3. Click + New dependency.
  4. From the Parent dropdown menu, select a field, then click Apply.
    The Parent field anchors the dependency.  
  5. From the Child dropdown menu, select a field, then click Apply. Options are derived from the Parent field’s category or table.

    Note: Each Child field can only be linked to one Parent field. 

  6. Click Next. 

Step 2: Value mapping 

  1. Click the pencil icon to the right of the row. 
  2. Search or scroll for the Child values. 
  3. Select the Child field values that will correspond with each Parent field’s values, then click Apply. Only the selected Child values will appear when using the field in the EE profile or in flows.
  4. Click Finish

Each time you select a value for the Parent field, the Child field will be filtered automatically according to the values set.

Note: If you move a field between categories, and that field is a part of a dependency, the dependency will be revoked when you move the field to another category. 

How to delete a dependency 

  1. From the left menu, select Settings > Employee fields.
  2. Select the Dependencies tab.
  3. Click the row of the dependency you’d like to delete, and the page will open.
  4. From the Actions dropdown menu, select Delete

Note: If you delete a dependency, it will remove the logic that defines how the values of the child list depend on the parent field. However, the fields and existing data won't be affected or deleted. If you delete/archive a field, all the dependencies that depend on the deleted field will be revoked. If you archive and then unarchive a field, you’ll need to define the dependency again.

How to edit a dependency 

  1. From the left menu, select Settings > Employee fields.
  2. Select the Dependencies tab.
  3. Click the row of the dependency you’d like to delete, and the page will open.
  4. From the Actions dropdown menu, select Edit
  5. Make the changes required and click Finish.
    If you change/rename a value on a list, the dependency will remain the same. If you add values to a parent list, all the values in the child list will be applicable by default. If you add values to a child list, the value won’t be mapped to any parent value unless the parent value is set to All values in the child field. 

Note: If you edit a list, and the list is part of a dependency, and you don’t have permission to manage dependencies, you won’t be able to update the list. Decide if you want to allow non-Admins to edit lists. For non-Admins, editing lists that are part of a dependency is impossible. 

FAQs

What type of field can a parent or child field be? 
Both fields can be List—a list with preset options that you define.

When is a dependency between two fields valid?
A dependency will be valid from the moment it's defined. If there’s information in the Employee profile that doesn't align with the dependency, it will remain as is until the information is edited. Example: An Employee profile has “Job title X” and “Department Y.” An Admin then defines a new dependency where “Job title X” is only applicable to “Department Z.” In this instance, no changes will be made in the Employee profile. 

However, if the Admin tries to update data in the Work table in the Employee profile, it won’t be possible unless the Job Title or the Department are changed to ensure that both data points are in sync with the new dependency.

Which fields can be dependent on each other? 
In order for two fields to be dependent, they need to be in the same category, either both in or out of a table.

Can I create a dependency between fields from different categories? 
No, you cannot create a dependency between fields from different categories. However, If you want a dependency between a field in the table and a field outside a table, you can create a custom field inside the table and create the dependency with this field.

Can I create a  loop of dependencies? (field X depends on field Y and field Y depends on field X)
A loop of dependencies is impossible, and you won’t be able to select a field as a child field if it already controls the parent field. A field can be dependent on only one parent field, and when selected, the child field can only be a field that hasn’t yet been selected.

Can I create a chain of dependencies?
Yes, this functionality is supported and is relevant to both existing and custom fields. Example: Job Title depends on Department, and Department depends on Site. 

Does the import tool or other integrations take dependencies into account?
Integrations are unrelated to field dependencies. You can import any value into a child field regardless of the value imported for a parent field.

Can we use field dependencies in the Mobile app?
Currently, field dependencies aren’t available on Mobile but will be in the future.