In the Field Settings, you can see the option to "Conditionally Update Values."  This allows you to select the option to "Assign When" or "Do Not Assign When" so that you can customise whether or not a field is populated based upon another field.



When using this function, you can opt to create your condition on several choices including blank, not blank, equal to, not equal to, less than, more than and matches the regex.



A few examples:

  • You might want to add "No Valid Address" code to a record that does not have an address:

  • You may want to not add a field, if another field is equal to a specific value

  • You might only want to add an attribute if an incoming field contains/does not contain a specific set of values. 

In this example, the incoming Field contains the values Opt1, Opt2 and Opt3. By applying a Regular Expression, the attribute in question will now only be added when the field value equals Opt1 or Opt2


Another way of looking at it, with a real -life example, if your incoming fields contains different values such as Communication Preferences like 'Newsletter', 'Annual Report', 'Fundraising', 'Brochure', and you only wanted to apply an Attribute if the Field contained 'Newsletter' and 'Brochure', then your Regex would look like this 'Newsletter|Brochure'


A Note about Key Fields

In some cases, a user may want to apply a Conditional Update Value to fields that happen to be 'Key Fields'. Things like email addresses/Phone Number or Attributes. Key Fields are special fields that have an extra bit of intelligence behind them and are often linked to the activity of an associated field. For Example, if the incoming value for an Email Address/Phone Number is blank, then Importacular knows not to add the Phone Type, because both fields are Key Fields. This means that you do not need to a Conditional Update Value to the Phone Type to not add the field if the Phone Number is blank. It will do that automatically. 


Likewise, when it comes to Attributes, if the incoming value is blank on the Attribute Description, or you have a Conditional Update Value in place that will make the incoming value blank, then you do not need to apply a Conditional Update Value to the Attribute Category as well, because both the Category and Description are Key Fields.