10,745
edits
Important: Deprecating old WebView — Publish failed error
Releases/Spring 2022: Difference between revisions
Jump to navigation
Jump to search
→Mapping of status fields
| Line 141: | Line 141: | ||
You can map external lookup fields to local lookup fields. This includes support for composite lookups, i.e., situations where a lookup is composed of multiple fields. | You can map external lookup fields to local lookup fields. This includes support for composite lookups, i.e., situations where a lookup is composed of multiple fields. | ||
=== Mapping of status fields === | === Mapping of status/option set fields === | ||
You can map the external status field to a local field, and you can also map the individual values (statuses). If the value mapping for imported/exported value is not defined, the Integrations tool offers 3 different handling options: use a specific value, use the default value, or throw an exception. | You can map the external state/status/option set/picklist field to a local field, and you can also map the individual values (statuses/options). If the value mapping for imported/exported value is not defined, the Integrations tool offers 3 different handling options: use a specific value, use the default value, or throw an exception. | ||
=== Mapping of external date-only and time-only fields === | === Mapping of external date-only and time-only fields === | ||