Map-Only Sources

Overview

You likely have records you'd like to see on the map regardless of what date range you're viewing on the calendar. These might be your customers who don't have a current service appointment or the current location of each of your service vehicles.

You can map these records (Salesforce objects or FileMaker tables) into DayBack much as you'd map events or appointments. But for these map-only entries, your date and time fields won't be required, but your location fields will be.

These map-only sources are "calendars" that don't show up in the calendar; they only show up on the map. Whereas regular calendar events will show up in both the calendar and the map, provided they have a geocoded location.

Calendar Info for Map-Only Sources

Once you create a new calendar, you'll find two settings that will turn it into a map-only source. For most map-only use cases, you'll set both of these to yes.

For Map Only: When set to yes, records in this source will not show on the calendar. Even if records in this "calendar" have dates and times, they will not show in the calendar view—they will only show on the map. (A date and time field might still be used for something like the last service date for this customer.)

Query On Geocode: When set to yes, the date and time fields become optional, and your GeoCode field is required. "Yes" here means that DayBack will fetch an item only when its location is within the visible map bounds. When set to No, DayBack will still require date/time field and will only fetch an item when its date is inside the calendar's date range AND its location is within the visible map bounds. This behaves like a regular event with a location, except that it will be excluded from the calendar, and only show the map.

Field Mapping for Maps and Distances

Field mapping is largely the same as it is for regular calendar sources. Read more about that, including details about each of DayBack's standard fields here.

The map, route, and distance features in DayBack use a location field and a geocode field described here: Mapping Location and GeoCode Fields.