Custom fields for addresses

If your Salesforce object uses regular custom fields to store the address rather than employing standard Salesforce Address fields (including the new Custom Address Field) you will need to carry out some additional configuration to enable address validation of these fields. This is achieved through configuration of Touchpoints.

1. Click on App Launcher. Type EDQ Global Settings in the Quick Find box, and select it.

2. Select Touchpoints from the left-hand menu.

3. Click the New button found in the top right to create a new Touchpoint configuration for your Salesforce object.

   

4. Set the Touchpoint type to Address and the Address type to Custom then select your Salesforce object from the dropdown.

5. Set the optional destination field for the validation status. By default the validation status is stored in a separate EDQ Log object, which happens in a trigger after the object is saved. If action needs to be taken based on the validation status before saving, then we offer the option of storing the status in a destination field on the record itself. Refer to the EDQ Log custom object guide for details on the possible status values.

6. Give your Touchpoint a useful name to help identify it in the list.

7. Activate the optional Passive validation feature should you wish to use it.

8. You can then map each address element to a custom field of your choice.

   • The first mapped field is where our 5 field address validation component will show up in your layout. If the remaining mapped custom fields are present on the active layout, these will be hidden and instead appear as part of the address validation component.
   • Note that you can have 1, 2 or 3 street elements which can be configured by clicking the + icon next to the street field. Street 2 and Street 3 are optional.
   • Custom fields of type Text are supported for all address elements with fields of type Picklist also supported by the State/Province and Country elements.

Multiple street elements

Depending on the number of street custom fields used, the address lines in our API response will be applied in different ways and make use of the concatenation separator configured in the global settings:

• Just Street element mapped: The 3 address lines in our API response will be applied to the single chosen street custom field, separated by the configured separator.
• Street and Street 2 elements mapped: The first address line in our API response will be applied to the first street custom field. The second and third address lines will be applied to the second street custom field, separated by the configured separator.
• Street, Street 2 and Street 3 elements mapped: The three address lines in our API response will be applied to the equivalent street custom field.

Handling of fields missing from the Page Layout

In order for the custom fields configured in a Touchpoint to be transformed into a set of EDQ validated address fields on the page, all of the custom fields must be present in the Page Layout. If any fields are missing from the Page Layout the Touchpoint will fail to initialize and the EDQ Record Detail component will fall back to displaying the standard Salesforce fields. In addition, an error message will be displayed in the browser console indicating that this has happened and what field(s) are missing. Here is an example: