Mapping Custom Fields to Bynder Metaproperties
TL;DR
When you publish a file from Wrike to Bynder, Wrike automatically maps custom field data to matching Bynder metaproperties if the field titles match and the field types are compatible. Some field types, like duration and people, aren’t supported, and publishing won’t work if Bynder has a required metaproperty with no matching Wrike custom field. Supported mappings include text, single select, number, percent, currency, and date fields.
Table 15. Availability - Legacy plans
| Availability: Business, Pinnacle, Apex. ; Unavailability: Free, Team; |
When you publish a file from Wrike to Bynder, information from Wrike custom fields is automatically added to their matching metaproperties in Bynder.
Custom fields and attributes are automatically mapped if:
- They have the same title.
- Their types are compatible (see the table below).
Note
- You can’t publish a file to Bynder if there's a required metaproperty in Bynder and no matching custom fields in Wrike.
- Duration and people custom field types can’t be mapped to Bynder properties.
| Custom field type | Bynder metaproperty type |
|---|---|
| Text | Text, unique ID |
| Single select | Drop-down/text* |
| Number | Number-decimal, number-integer**, unique ID |
| Percent | Number-decimal, number-integer** |
| Currency | Number-decimal, number-integer** |
| Date | Date/time |
*If there's a matching metaproperty with drop-down options in Bynder, the information is added as is; if not, the information is added as text.
**For custom fields that have zero decimal places.