1. Are calculated fields not supported in field mapping rules?

The reason is that “calculated fields” can have different types (text, date, numeric, etc.) which are indeterminate, making them incompatible with mapping rule configurations.

2. Why doesn’t the owner mapping rule automatically populate the owning organization?

Currently, mapping rules support populating the owning department when mapping an owner, but populating the owning organization is not yet supported.

3. Mapping rules not taking effect/incorrect field mapping

Mapping rules only take effect at the moment of entering the create page. If mapped fields appear incorrect, it’s likely they were modified by users afterward.

1. If incorrect field mapping occurs when clicking the map button (reproducible):
   • First check if any UI event functions modified the data
   • For preset fields, also consider whether predefined logic might have reset the field
2. If the issue isn’t reproducible when clicking the map button (historical data): 2.1 Verify if the data was truly mapped:
   • In the modification records of newly created data, click the main Attribute
   • Enter the create snapshot view - if the source shows as “mapped”, it was indeed mapped

   2.2 Determine if incorrectly mapped fields were modified later: - Check modification records - if the snapshot shows correct values but details don’t, the fields were definitely modified

   2.3 Check if source data fields changed after mapping: - Also verify through modification records