Frequently Asked Questions

1. Do calculated fields support field-mapping rules?

Calculated fields can be of different types (text, date, number, etc.) and their exact type may be indeterminate. For that reason, calculated fields cannot be configured in field-mapping rules.

2. The mapping rule mapped the Owner — why didn’t the associated Department auto-fill?

Currently, mapping rules support mapping the Owner and then auto-filling the associated Dept. Auto-filling the higher-level organization (Department hierarchy beyond the Dept. level) is not supported yet.

3. Mapping rule not taking effect / mapped fields are incorrect

Mapping rules only apply at the instant the New record page opens. If a mapped field’s value is incorrect, it is likely because the user modified it after the mapping ran.

1. If clicking the Map button reproduces the incorrect field value, first check whether any UI event handlers modify the data. If the field is a predefined Attribute, also consider whether built-in logic resets that field.

2. If clicking the Map button does not reproduce the issue (the problem exists on historical records), do the following: 2.1 Verify the data was actually produced by mapping: in the record’s creation change log, click the primary Attribute to open the New-record quick view. If the source shows “mapped,” the value was indeed filled by the mapping rule.
   2.2 Determine whether the incorrectly mapped field was subsequently modified by users by reviewing the change history: if the New-record snapshot is correct but the record detail is not, the field was modified after creation.
   2.3 Check whether the source record’s field changed after mapping by inspecting the modification history of the source field.