Mapping Fields
Mapping Fields
NOTE: Mapping fields are only available as a paid add-on feature. Contact your representative to inquire about getting these fields.
Mapping fields use Google Map APIs to map locations on aerial maps. You can map an area, location, route and more. Some of the maps require a Latitude / Longitude pair to be able to map. Acquiring the LAT/LON values form addresses may be possible using the Call REST API action if you have a REST endpoint you can call. There are several services available such as Google.
View Map - Shows a map of a specified Latitude / Longitude. This map is made to show locations without any pins or specific points of interest
Address Map - Shows a map of a specific address and its general area. This map is made to a pin to specify one address on he map.
Directions Map - Shows a map of the route from one to address to one other address. It only supports a single FROM address and a single TO address.
Search Map - Shows a map with locations based on a human readable description. For instance, using a search criteria of "hotels in lincoln ne" will show hotels in the Lincoln, NE area.
Locations Map - Shows a map with multple Latitude / Longitude coordinates. This map is used to map multiple locations on a single map. This does not support routing - just mapping. You can manually program the locations into the E-form or you an use DMGETOPTIONS to fill locations based on Records. It also supports a click event that can show a pop up form or can trigger other fields in the E-form. See Locations Map Notes below for detailed information.
Locations Map Notes:
The locations that you can add to the map can be manually added or can use the DMGETLOCATIONS variable which returns locations from the data in searched Records. It works just like DMGETOPTIONS but is optimized to work with locations.
Sample DMGETLOCATIONS to get Record data as locations:
[DMGETLOCATIONS(123|0||RecordID|LatLon|Title|Description)]
See the DMGET variables sections for a complete breakdown of the DMGETLOCATIONS variable.
* The normal use case is to read the map locations from Records in the system using the DMGETLOCATIONS variable. However, there are other options to load the map locations. They require more low-level configuration so contact support if your needs are not met using individual Records as locations.