Several of our integrations allow you to create custom mappings in addition to the default mappings. Note that each integration is slightly different regarding what can be accessed through its API.

It's also important to note that if you want to map a custom field within PreciseFP, it must exist in the dataset. Form template elements that do not yet exist in the dataset are not eligible to be mapped and must be created as dataset elements and then connected in your form template in order for the data from the form template to then be stored in the client profile. The client profile (the dataset elements) are what map over to the integrations.

To add to an integration mapper, click on Settings then integrations.

Click on an integration box that you have enabled and then click on the Open button (Note: if you click on an integration box and do not see the Open button next to Integration Mapper, this means that this integration does not allow for custom mapping)

Once open, you'll now see the mapper. This will show you all the dataset fields that map, along with where they map to. In this example, I'm using Redtail. The fields in blue are mandatory on both sides of the integration and cannot be customized or edited. On the left side, this indicates the field in Redtail that this maps to. In the middle column, this indicates the page, group, and field from the PreciseFP location that maps to the integration field. Along the far right are the different sections, which vary from integration to integration. Depending on the integration, these may also be referred to as objects. You can click on each section on the right-hand side to see the different mappings for this section. In some Integrations, you may even be able to add additional mapping sections.

In this example, I'm going to add a new field to map to under the Contacts section. I have already created a dataset field for it in PreciseFP and I have created a custom dataset element for this in Redtail. (Note: the ability to create custom fields in the integration varies from integration to integration.) Click on the + to add a new element mapping.

You'll now see a Field dropdown. These are the available fields you can select from the integration.

If you do not see the field you're looking for, it is not available via the Integration API and therefore cannot be mapped here. In this example, I have a field in my CRM called Designation that I will now select.

Once selected, I need to select a field from the Connection dropdown. These are my PreciseFP dataset elements. If you are unable to locate the element, it is not a dataset element. To avoid errors or issues, it is highly recommended to match the element types in your integration with those in PreciseFP. For example, if the element you created in the integration, or want to map in the integration, is a numeric field, but the dataset element you created in PreciseFP is a date field, this may cause issues during export/import. You do not have to input anything in the default value field. This only comes in handy when you do not set a connection and want a specific value exported, or when you want a default to apply if the client leaves the field blank.

Once you've made your connection, click on Save Changes.

You will now see this newly mapped field in the table.

If you now add this dataset element to your form template via import from the dataset or via element connection and the client inputs data into this field, the data from this element will store in the corresponding dataset client profile element. When you click export in a client's account, this data will now be exported to the mapped field in your integration.

In some cases, you may want/need to reset the mapper back to its default setup. To do this, visit Settings, then Integrations.

Click on the Integration box that you wish to restore, then click on the Open button.

In the top right you'll find the reset to defaults button.

You'll then be prompted to input your PreciseFP password.

!WARNING! This operation cannot be undone. By resetting back to defaults, you will lose ALL of your mapper customizations. Note that this does not delete any custom datasets you've created, nor does it delete any data. Any clients or prospects you have linked will be unlinked, so the next time you import/export them, you'll need to relink them.