Dispatch Console: Google Maps Error

on our side we have changed the following code “var googleMapsVersion”  from 3.46 to 3.47 in initialization.js of the Map foder to avoid this error. Waiitng for the official fix

What is status for resolution? We have extrem tight SLA. 

November is over two months away. I have HF12, and it will take 3-4 weeks to test before I would even consider installing in production. Plus the know bug with the Dispatch Console included in the release.

Important message for all Alliance Customers that use “maps” in modules other than Dispatch Console. It is the same change that was done in February, whereas the Maps API version was changed to 3.46. Now it needs to be changed to 3.47.

Below are the changes for customers working on V14 and V15 that include changes in the DC and also in other modules:

Dispatch Console Maps
 
website\Maps\Astea.GIS.Services.GoogleMaps.GoogleApiServices\initialization.js
 
Change function LoadGoogleMainScript()
 
var googleMapsVersion = "3.47";
 
Address Finder Maps
 
\website\form_asp\google_address_finder.htm
 
Change function LoadGoogleMainScript (comment first line with // and paste other three lines below this line)
 
//script.src = m_googleApiUrl + "js?&key=" + m_apiKey + "&libraries=places&callback=initMap";
 
var googleMapsVersion = "3.47";
 
var libreries = "&libraries=places&callback=initMap";
 
script.src = m_googleApiUrl + "js?v=" + googleMapsVersion + "&key=" + m_apiKey + libreries

For customers that work on versions below V14 the following are instructions:

Address Finder Maps

\website\form_asp\google_address_finder.html:  

function loadGoogleMainScript() { 

            setFieldText();

            parseRequestArguments(window.location.search.substring(1));

            if (m_apiKey === "") return;

            var script = document.createElement('script');

            //script.src = m_googleApiUrl + "js?&key=" + m_apiKey + "&libraries=places&callback=initMap";
var googleMapsVersion = "3.47";
 
var libreries = "&libraries=places&callback=initMap";
 
script.src = m_googleApiUrl + "js?v=" + googleMapsVersion + "&key=" + m_apiKey + libreries

            document.body.appendChild(script);
        }

Dispatch Console Maps

\WebSite\Maps\GoogleMaps\MainMap\GoogleMap.htm

  function LoadGoogleMainScript() { 
                try {
                    $('#swapDiv').hide();
                    $('#textDiv2').hide();

                    var MapBaseURL = window.external.getMapBaseURL();
                    var key = window.external.GetMapSignKey();
                    if (MapBaseURL == null || MapBaseURL == undefined || MapBaseURL == "" ||
                        key == null || key == undefined || key == "") {
                        window.external.MapErrorHandler("1071", "");
                        return;
                    }

                    var googleMapsVersion = "3.47";

                    var libreries = "&libraries=geometry,places";
                    var MapURL = MapBaseURL + "js?v=" + googleMapsVersion + "&key=" + key + libreries;

                    //check if the Google URL is accessible
                    var IsUrlValid = window.external.CheckMapConnectivity(MapURL);
                    if (IsUrlValid != "true") {
                        window.external.MapErrorHandler("1086", IsUrlValid);
                        return;
                    }

                    updateUStats(RequestTypes.DynamicMapLoad, "OK");
                    BuildGoogleMainScript(MapURL, 'LoadGoogleScripts');
                }
                catch (err) {
                    window.external.MapErrorHandler("1086", ErrLoadGoogleMainScript);
                }
            }
 

Are the symptoms of this problem the same ones that we could expect to see in November if we do not or cannot install the latest patches? (Currently on v11.5 and weighing our options. Upgrading by November is not one of them.)

Phil, just so I’m clear going back to my user team, Suggest SA will still offer recommendations, but the map will not be shown. Is that correct? The potential loss of Suggest SA functionality is a major issue for our dispatch team.

Hi @Luis Aguero 

Do we have a solution for customers in 15.2 ? (I didn’t see this release in the list)

Regards

anthony 

Hi @Phil Seifert 

Ok thanks for your explanation. 👍

To be sure, could you confirm that without the fix a customer couldn’t validate an address for a customer site in the transaction “Customer Center”  ?
The impact on the fix concerns not only the usage of maps in the console dispatch but also the feature of geocoding addresses (employee, warehouse, customsier site, etc..) ?

Thanks for your help.

Regards

anthony

Hi Phil @Phil Seifert 

Thanks you very much for your test. Very Useful 👌

anthony