Static Field Mapping

The Static Field Mapping allows administrators to predefine default values for specific fields when new records are created from WhatsApp conversations.

These values are automatically applied during the record creation process, whether from a Questionnaire, a "Create To" action, or creating customer from chat UI, eliminating repetitive data entry and ensuring consistency across CRM records.

How to Configure Static Mapping:

Follow these steps to create a static mapping rule:

  1. Go to Configuration in WhatsApp4Dynamics.

  1. Click on Related.

  2. Select Static Mappings from the dropdown list.

  1. Click New Static Mapping to create a new rule.

  1. The Static Mapping Form will open.

Now, fill out the form:

Field

Action

Rule Name

Enter a name to identify the rule (e.g., “Default Contact Source”)

Target Table

Choose the entity where this rule applies (e.g., Contact, Case)

Target Field

Select the field to auto-fill (e.g., Source, Status)

Static Value

Enter the default value (e.g., WhatsApp, New) – input options change based on field type

Save

Click Save to activate the rule

Example: Autofill “Source” Field in Contact Creation

Once the static mapping is set up:

  1. Open a chat in WhatsApp4Dynamics.

  2. Create Customer or use a Questionnaire to create a new Contact.

  1. On the Contact creation form, the Source field is automatically filled with the value you configured (e.g., “WhatsApp4Dynamics”).

You can map only for the tables whose record types have been created or added inside the "Allow create to" field in Configuration.

Static Value Field Types

The input method for Static Value changes automatically based on the Target Field type. This ensures that only valid inputs are allowed and simplifies the configuration process.

Below are the supported field types:

1. Static Value (Text) If the Target Field is a Text or Number type, the system will display a multiline text box for entering the value.

2. Static Value (Single Select) For Single-select option sets (also known as dropdowns), the Static Value input will appear as a dropdown list.

3. Static Value (Multi Select) When the Target Field is a Multi-select option set, the input becomes a multi-select list.

Only the relevant control appears for a cleaner UI.

Note: These are the only supported formats as of now.

How It Works

When a user creates a new record from WhatsApp:

  1. The system checks if the selected entity’s record type is available or if it is added to the “Allow Create To” field in Configuration.

  2. It looks up any matching rules in the Static Mapping Table.

  3. Applies the static value to the target field.

  4. If both static and dynamic mappings are enabled for the same field, the static mapping will take priority.

  5. The new record is created with a mix of static defaults and dynamic values.

Examples:

Contact Creation from Questionnaire

Rule:

  • Target Table = Contact

  • Target Field = Source (Option Set)

  • Static Value = WhatsApp

Result: Every new Contact created via a Questionnaire will automatically have Source = WhatsApp.

Case Creation via “Create To”

Rule:

  • Target Table = Case

  • Target Field = Status (Option Set)

  • Static Value = New

Result: All new Cases created from WhatsApp chats will have Status = New, unless another status is provided.

Customer Creation from Chat UI • When a user creates a Customer record by clicking the Create Customer button in the Chat UI, the fields will be auto-mapped based on the configured static mapping rules.

Notes:

  • Static Mapping only affects newly created records.

  • Existing records in the system remain unchanged.

  • Input validation ensures that field types and values match correctly.

Last updated

Was this helpful?