Customizable Field Mapping

Last synced 6 days ago by Jonas

The field mappings allow you to decide what contact data should be synced.
PieSync will give you a predefined list of field mappings,  the "Default Field Mapping". These are the default contact fields that correspond between the two apps of your choice.
You are also able to add your own mappings, the "Customizable Field Mapping". Both custom field mappings and default field mappings can be synced with each other.

Customizable Field Mapping is available from the Pro or Medium Plan and onward only.

You can set up customizable field mappings below the default field mapping in the configuration by clicking 'add field mapping'. You can add an unlimited amount of mappings and remove, enable/disable them anytime. 

If you've just added a field in your app and it hasn't popped-up yet in the dropdown list of available fields in PieSync, just press 'refresh field list' in the bottom right corner

Below you see an example. Of course, this is dependent on the apps you have connected and which (custom) fields you have available on both sides.

Changing the Default Field Mapping

As the default field mapping is a predefined list of mappings, some of the field mappings might not suit your use case.
In that case, you are able to change the specific default field mapping by disabling it.

This will make the specific contact fields available in the customizable field mappings. 

You can now match these previous default fields with other fields of your choice.

What are Custom Fields?

Custom fields are fields that are not part of the standard fields offered by the applications you are syncing. In most cases, they are added by the user.

You are able to amend the sync direction of your customizable field mappings according to your specific case. 

What is a custom mapping?

Two fields* (standard or custom) kept in sync, defined by the user.  

*Some standard fields are already synced in the default field mapping.

Are custom mappings always two-way? 

The custom mappings will sync in the direction you have set up in the configuration of your connection, so this could be either two-way or one-way.

However, there are some exceptions where a custom mapping can only sync one-way:

  • When certain contact fields are not allowed to be modified through a third-party integration such as PieSync.
  • When a field only allows some specific values.
  • When two mapped fields are of a different type.
Below is an example of a field that can't be modified through a third-party and therefore only syncs one-way (→). More in-depth information can be found here.  
Bear in mind that the general direction of the sync decides your syncing behavior. When you have your connection configured as a one way sync in the other way (←), following message will pop up.

IMPORTANT SIDE NOTES

Why are my (custom) fields not showing in the custom mappings dropdown OR  greyed out?

  1. Each field can only be mapped once.

  2. Fields that are used in the built-in mappings (default field mapping), cannot be used in the custom mappings.

  3. Fields in a custom mapping must be of the same or a similar type. You can’t sync a numeric field to a date field for example. When selecting fields in a custom mapping, the list on the other side will only show the fields that can be mapped, unavailable mappings are either not visible or greyed out. 

  4. Some types of custom fields (and app & integration dependent) are technically not mappable (drop-down, lists, multiple values)

  5. Fields with multiple values (see example below) can’t be synced in a custom mapping. In some cases, they are synced in the default field mapping. With multiple values, we mean fields such as emails, phone numbers and addresses where each value has a label to differentiate between ‘home’, ‘work’ and ‘other’ for example.

Why can't I set up any custom mapping? 

This could be caused by one of the following reasons: 

  • All standard fields were already mapped by default
  • There are no other (custom) fields available/left to map
  • There are no compatible fields left to map
Don’t forget to read our Blog Post about our Customizable Field Mapping feature! 

How did we do?