Defined Value and Token in Actions allows you to update a destination field using the value from a source field.
How It Works
- Add the Change CRM Account and Person Data action.
- Complete the following:
- Account Field: The field to update (destination field)
-
New Field Value: The field to copy from (source field)
- Defined Value: Value you enter manually.
-
Token: Value copied from the source field.
Important: Token copies the value the moment the action runs. It does not continuously sync or update data.
When the action runs, Demandbase:
- Identifies the records that meet the selector criteria.
- Copy current value from the source field.
- Updates the destination field with that value.
- If the source field is blank at runtime, the destination field is updated with a blank value.
Account vs. Person Actions
- Account action updates an Account field.
- Person action updates a Lead or Contact field.
Field Requirements
When using tokens, both the source and destination fields must meet the following requirements:
- Be active in Demandbase.
- Not be a Marketing Automation-only field.
- Be editable by the sync user in the Demandbase-CRM integration.
- Be from the same data source:
- Example: Salesforce → Salesforce
- Be the same object type:
- Account field → Account field
- Person field → Person field
- Be compatible field types:
- String fields can accept values from date or integer fields.
- Date fields can only accept values from another date field.
- Not be a multi-select picklist or formula type field in CRM.
- Do not use the same field for the destination and source fields.