back to knowledgebase

How do I set up conditions for use with custom fields? How can I add conditions to standard fields?

Updated: 30 September 2022 13:19:37 OpenCRM::Settings::Custom Fields

There may be occasions when you need to display a field or make a field mandatory only when specified conditions on another field are met. In this FAQ we will give you a quick outline of the step you need to take, followed by a real world example.

 

Conditional Field Show/Hide

To set up the condition for determining when a custom field will appear:

  • Click Settings
  • Under Studio click Custom Field Conditions
  • Click the New Type button
  • Select the Module to get a list of fields you can use
  • Enter a Type Name - This is the name that appears in the Condition drop-down when creating custom fields
  • Select the field you want the condition to be based on
  • Enter the value the field needs to be for the condition to be met.  Please note that this is case sensitive
  • Save the custom field type

An Example

In this example you'll see how to add a custom field to allow you to enter a "Reason for lost" on the Leads module when the Lead Rating is set to "Lost".

The Rating field on Leads is a standard drop-down field on the system:

Setting up the Rule

To begin with we need to create the Rule which will trigger the new custom field. This is done by going to Settings, then under Studio click Custom Field Conditions. This will take you to a screen that looks like this:

Click on New Type to build the Condition.

Firstly select the module on which you want to use the condition. Once you have done this, the screen will refresh to update the field selector.

Then enter a Type Name, which will appear when you create the custom field under the Condition drop-down.

Next select the Field to match the condition against. Please note that the field names here will not necessarily correspond with the field labels, and that custom fields will display as their field ID e.g. cf_377.

When you are happy with the rule you have set up, click Save. Be aware that you cannot edit a conditional rule, but will need to start from scratch if you wish to make any changes.

 

 

Mandatory Conditional Field

Mandatory Custom Field Conditions allow you to set up conditions under which a custom field can be made mandatory. These conditions can then be applied to custom fields when they are created. 

For example, you may only want to record an "area of interest" if the contact or company type is "Customer". 

This differs from conditional custom fields which will show/hide extra fields depending on other values. This instead will make fields mandatory dependent on other values. 

 

Important: For this to work, you need to have the setting to display conditional fields dynamically enabled. 

To switch this on:

  1. Go to Settings and navigate down to the Configuration block.
  2. Click on Additional Settings (last option)
  3. Click the option for Interface Settings
  4. Tick the button next to: "Fields that are set with a conditional type will load automatically when the conditional field meets its value"
  5. Click save

 

To set up a new mandatory conditional field:

  1. Go to Settings and navigate to the Studio block
  2. Click on  "Custom Fields Mandatory Conditions"

You then choose the module for this condition, give the condition a name so you can find it in the list, select a field for the condition to be based off and then enter the value that field should match for the condition to apply. 

In the example below, the condition is for any Contact with the mailing city set to London. This could be used to make a "district" or "sales region" field mandatory to split up the city into areas.

 

Adding the Condition to a Custom Field

You can do this either when you first create your custom field OR add a condition to an existing custom field.

Adding to a New Custom Field

You can now add the custom field as you normally would do in OpenCRM (click here for an FAQ on creating custom fields).

Go to Settings - Custom Field Settings and select the module where you want to add the custom field, so in our example Lead Custom Fields, and select New Custom Field.

 In the screenshot below, we have created a new picklist field, and use the Condition box at the bottom of the screen to specify that this is a conditional field.

Hit Save to finish the set up.

Adding to an Existing Custom Field

To add a new condition to an existing custom field, simply to go Settings > Studio > Custom Fields and select which module you created the original custom field in.

Then click the "edit" option next to the field in either the Condition (red) and Mandatory Condition (purple) column.

Once you have selected your new condition from the dropdown menu, click save. Easy as that.

Adding the Condition to a Standard System field

The above options are only applicable to custom fields, as you can access those via the Custom Fields settings pages. You can apply a Condition or a Mandatory Condition to a system field by going to Settings > Default Organisation Field Access > select the relevant module. From this screen, you can use the Edit option in the Condition and Mandatory Condition columns to add the Condition. Note that you will need to create the condition first before you can apply it.

Trying out the conditional field

When creating or editing a Lead, we can now see an additional "help" icon beside the Rating field.

If we select the value of "Lost" in this field, this will trigger the conditional field we have created.

If you change the value again, from "Lost" to any other value, then this conditional field will once again be hidden.

 

As you see in the above example, conditional fields can appear as soon as you populate the trigger field. This has to be enabled. Go to Settings->Additional Settings->Interface Settings and tick to enable the setting.

 

 

Multiple Conditions

Additionally, you are able to have multiple conditions operating on the same field. 

To enter multiple conditions, simply type each conditional value followed by a comma. You do not need to use a space after each entry (i.e. "London, Leeds, Liverpool" will work the same as "London,Leeds,Liverpool")

For example, if you needed to be able to identify the general area (i.e. North, South, etc.) of certain cities for delivery purposes, you could have a condition set to run whenever the Mailing City was set to one of these cities. Your custom field would then appear when any of these cities was entered. 

In this example, we have used the cities London, Leeds, and Liverpool to trigger the Which Area conditional field. 

If the Mailing City field is set to Leeds, the custom field Which Area will appear. The Which Area field will be visible when either London, Leeds or Liverpool is selected as the Mailing City, but will not appear when another value is entered:

Rate This Article
  • 1 star
  • 2 star
  • 3 star
  • 4 star
  • 5 star
Feedback and Comments
captcha code  


You may also be interested in: