Skip to main content
All CollectionsField Types And App Designer SettingsUser Defined Fields
How do Address fields work?
How do Address fields work?

Captureing addresses and having them auto-populate on the mobie apps.

Mike Meesseman avatar
Written by Mike Meesseman
Updated over 2 weeks ago

The Address field allows you to capture a full street address, without having to have separate fields inserted for each element of an address. 

To edit an address field, the user can tap on the address field and make adjustments to the individual components that make up the address field.

Addresses in exported data

When exported, the address field data results in several data columns, separated for convenience and flexibility. The field's data name will be first, address in the example below, followed by an underscore and then the part of the address field that the data came from. There will also be an additional column that contains the full address without any parsing.

  • address_sub_thoroughfare - Address number

  • address_thoroughfare - Street name

  • address_locality - City

  • address_sub_admin_area - County

  • address_admin_area - State / province

  • address_postal_code - Postal or zip code

  • address_country - Country

  • address_suite - Unit / suite number

  • address_full - All the above fields together in a single property (good for reporting)

Placing Address Fields into a Calculation Field

You can use a calculation field to display only a portion of the address in your app. To do this, you need to have an address field on the form. If you don’t want to show the entire address, you can hide this field.

  • All Fields Together: SETRESULT($address.full)

  • Address Number: SETRESULT($address.sub_thoroughfare)

  • Street Name: SETRESULT($address.thoroughfare)

  • Unit / Suite Number: SETRESULT($address.suite)

  • City: SETRESULT($address.locality)

  • County: SETRESULT($address.sub_admin_area)

  • State / Province: SETRESULT($address.admin_area)

  • Postal or Zip Code: SETRESULT($address.postal_code)

  • Country: SETRESULT($address.country)

Importing data into the address field

When you are importing data into the address field you will want to break up the address just like it is broken down in the exported data file with the exception of the full address column. 

If you use a column header with the data name of the address field and _element  of the address field you wish to import into the system should auto map the column to that element of the address field. 

For example, if your address field has a data name of home_address and you want to import into the address number part of the address field then your column header would be home_address_sub_thoroughfare .

You can also manually map the column to the various parts of the address field during the mapping step of the importer.

Auto-population functionality

For the auto-population functionality, Fulcrum leverages the device's reverse geocoder to auto-populate the address field. The ability to auto-populate the address from the coordinates is only available on the mobile apps. The web app does not have support for this functionality.

Note

  • There are times where the location of the record will result in the device's reverse geocoder not being able to return an exact address and may provide a partial address, an address that it believes is associated with the location, or a range of addresses (address numbers) that could possibly be associated with the coordinates. Due to this, it is always best to confirm that the address field has auto-populated correctly.  When this does happen, the user will either need to manually edit the address so that it is correct or they will need to reposition the pin. Typically placing the pin over a structure on the property will yield the best results.

Did this answer your question?