Mapping reasons
Airdrop uses transformation methods to map data from one data model to another. These methods operate at the individual field level, transforming data field-by-field rather than entire records at once. Each transformation method has specific requirements regarding the field types and data formats it can work with. If the source data field does not meet these requirements for a particular transformation method, that mapping option is not available for selection during the mapping configuration process.
There are several reasons why some mappings might be unavailable:
- A common reason is mismatch of types. For example, if a DevRev field is expected to be
rich_text
, but the field is set astext
mapping to some fields is unavailable. Refer to the supported types section and the general DevRev documentation for more information. - Only references can be mapped to references. Ensure that source system fields are correctly mapped to reference fields in DevRev.
- Support for the
struct
type is limited. Marking a field as a struct in the metadata schema will make it unavailable for mapping outside of using the custom jq transformation method. Refer to the metadata tips for more information. - Links are supported only on works and conversations.
Transformation methods
The following tables outline the available transformation methods categorized by their applicable field types: