Hello all, just wanted to share this with the FSM community
if your instance is on the yokohoma release, some OOTB map settings might not be working as expected.
- If you create new Google API keys after March 1, 2025, you must enable the new APIs from Google Console and upgrade to a supported release version to ensure compatibility Google Maps APIs for Field Service capabilities
- this KB tells you where to add the keys, but it's outdated Geocoding Latitude and Longitude not updating and throwing referrer restrictions error - Support and...
- you need to add the server key in 2 places (see screenshot below), else your BR get_lat_long will not populate cmn_location records lat/long.
- also, if the location records existed before you've added the keys, you need to ''update'' the record, else it will not trigger the BR. I suggest you run a background script to bulk update.
2. now, in yokohoma you'll notice that if you uncheck these 2 properties, it just removes the arrows. that's because the new API is not fully supported in Y.
To enable using the new google API for Route Optimization. Please change the property
'work.management.travel.calculation.route_optimization.mode'
from 'DP' (out of box) to 'Greedy'.
The original mode relies on java layer of API change and it is not fully supported in Yokohama release. By switching to 'Greedy' mode, we will fully adapt the latest javascript google Route API integration instead of using the deprecated Directions API from java side.
