OpenField to VAN/EveryAction Mappings

Configure mappings for an existing pipeline

To sync data between OpenField and VAN/EA for a given client, Bluelink needs to know how survey questions, contact types, and contact results in OpenField map to the client's VAN/EA setup. You can use the Bluelink mapping UI to input these mappings for each client.

Getting started

Click on the OpenField to VAN/EA pipeline.

Click on the MAPPING tab under the pipeline's name.

You will need to fill out the mappings for all 3 mapping types described below. Use the "Select mapping" dropdown to switch between the 3 types.

Canvass Contact Type

Canvass Contact Type is how the person was contacted, such as Phone, Walk, or Email. Different VAN/EA instances may have different possible available values so these need to be mapped per client. Add a mapping by selecting an OpenField value and corresponding VAN/EA value in the "Add Mapping" section. Different OpenField values may map to the same VAN/EA value. Map all OpenField values until no more are left in the "Select OpenField value" dropdown.

Canvass Result Type

Canvass Result Type is the result of the contact when the person was not successfully contacted. Examples are Not Home, Wrong Number, and Left Message. Different VAN/EA instances may have different possible available values so these need to be mapped per client. Add mappings the same way as described above. Map all OpenField values until no more are left in the "Select OpenField value" dropdown.

Survey Questions and Responses

Map survey responses one at a time by choosing a question and response from OpenField and then the corresponding question and response from VAN/EA.

Only True/False and Multiple Choice questions will show up in the OpenField question list. Once an OpenField response is mapped, it will be removed from the list of choices.

You only need to map questions + responses that should be synced to VAN. Any unmapped responses will be skipped during the sync process.

Related articles