Integration field mapping for required fields, data types and picklist values
Key Takeaway
An inbound record saves only when every universally required field has a value. When the source system can't send one, give the field a default value or fill it with an auto-launched flow that makes before-save updates.
When an external system sends records into an Agentforce Financial Services org through the API, the settings on each target field decide whether the record saves. Before you finalize the integration field mapping, check four things. Find out which fields are universally required. Check whether the field types match and whether the picklist values exist. If the org uses multiple currencies, check how its currency fields work.
Universally required fields
The rule covers saves through the Lightning Platform API, so an inbound integration that sends no value for one of these fields can't save the record. Data imports follow the same rule. You must include universally required fields in your import files, or the import fails.
- Standard fields cannot be universally required, so the fields to check are custom fields.
- Universally required fields are required across all record types.
- Records that existed before a field became required may have a blank value in it. When a user updates such a record, the user must enter a value in the required field before saving. An integration that updates an older record meets the same rule, because the requirement applies to API saves too.
A field that's required in the source system but isn't required in your org doesn't need to be mapped.