The Location property allows users to record and view the location of an object through an address field, pins on a map, or both, on a standard configurable form. Through this feature, users can visualize where events or incidents are occurring to help identify high-risk areas.
When both the address field and map are displayed, entering an address automatically places a pin and vice versa. Relationship and reference form elements can also be configured to display location information as a map or table.
For instructions on adding and configuring this property on a form, see the following articles:
For instructions on adding, viewing, or importing location data, see the following articles:
In addition to collecting and displaying location data on an object, this property can be used with the following:
- Relationships and References: Shows the locations of relationship and reference objects on a map. Clicking a pin on a relationship or reference map will display additional object information in a palette. See the Show Location Data in a Relationship or Reference for more information.
- Preferred Language: Allows end-users to search for and select addresses in the language chosen in the user's profile or browser settings (preferred language). Note that:
- If your preferred language is not supported, English will be displayed by default.
- Users can view location data on an existing object in a language other than English provided both the location data and the user's preferred language match. For example, if the location data was recorded in French, a user with Russian as a preferred language would only be able to view it in English.
- Map tooltips with additional address details are displayed in the language used when the data was recorded, provided the preferred language of the user who recorded the data and the user currently viewing the tooltip match.
- Location data on reports and relationship maps are always displayed in English.
- Concatenation: Pulls location data to display complete or partial address information in a plain text field or in the Name and/or Description properties on an object type, using address components as variables (i.e., House Number, Street, City, etc.). Note that:
- Map rendering in concatenations is not supported.
When Country is used as a variable, it's displayed using the ISO 3-character code (e.g., CAN for Canada).
When State is used as a variable, it's displayed using the ISO 2-character code. If there is no 2-character code, 3 characters are used (e.g., Australia uses 3 characters for states/provinces, but North America uses 2).
Repeatable Forms and Tables: Displays address details as text in repeatable forms (including their PDF exports) and report tables (including their PDF, Word, and Excel exports). If no street address is assigned to an object, coordinates are displayed. Map rendering is not supported.
Search Filters: Global search results can be narrowed down by applying Location filters, which include:
By House Number
By Zip Code
Users can enter 3-letter ISO codes (e.g., searching for CAN or Canada will return all results for Canada). Searching by coordinates is not supported.
- Required Components: Prevents an object from moving to the next workflow state until an address is selected. When marked as required, the address search bar is highlighted in yellow. If the property is configured to display as Map Only, the map border is highlighted in yellow.
- Pull Data Values Workflow Action: Copies location data between two objects using the Pull Data Values workflow action; however, both object types must have the Location property added to one or more forms.
- BI Connectivity: If BI connectivity is enabled for your organization, location data can be reported on using a BI tool.
- Imports: Imports location data via JSON file or the Data Import feature; however, addresses and coordinates are not verified as accurate or complete. See the Import Location Data article for more information and requirements.
- This feature does not currently support:
- Rendering on data visualizations or their components (i.e., data export report and data grids), except repeatable forms (including their PDF exports) and tables (including their PDF, Excel, and Word exports).
- Map rendering on any reports, including repeatable forms or tables.
- Due to Chinese legislation, addresses and locations within China are not searchable through this feature.
- If location sharing is enabled on your browser, auto-complete suggestions are provided in the address field, and the map is centered based on your current approximate location. As such, it's recommended location sharing is enabled on your browser for more accurate results. Note that a slight delay may occur when the form is initially loaded after sharing your location.
- Core will ask users to share their location once, unless their browser is configured to always ask or their settings are later modified. For more information on enabling location sharing, see the Share your location article on the Google Support site for Chrome.
- Maps should not be displayed on form sections smaller than 33% in width.
- Due to the amount of canvas space required to display the map on a form, this display option should be used sparingly and under specific circumstances (e.g., to visualize the distance between multiple related objects or if the location does not have a known address).
- Location sharing should be enabled on your browser for more accurate results when searching for or selecting a location.
- When importing latitude and longitude coordinates, 6 decimal places should be used for consistency (e.g., 54.123793, -113.127389).
- Clicking location data in a relationship or reference table will open a palette that displays the address field, map, or both, depending on its configuration. For more complete information when viewing the palette, it's recommended that the map or map and address information is configured to be displayed.