Hi Phil thanks for the info we have the first customer case reported this morning on V15.2 and V15.4

Glad I’m working  remote! Most of my Dispatch Console users live by the map.

Thanks @Phil Seifert for the information. 

We have a temporary workaround which can be used for ONLY the Dispatch Console maps.

The issue relates to the version of the Google Maps used and by following these instructions on EACH of the servers hosting Alliance, this should allow the maps to work for a limited time until Google disables this version.

If you have access to your Alliance servers, please following these instructions:

The workaround will be available only until next Google Map Api release.

See instruction below for fixing the issue:

1. On the web/applicaton servers open the file \website\Maps\Astea.GIS.Services.GoogleMaps.GoogleApiServices\initialization.js
2. remove the read only from the file
3. change the GoogleMapVersion to 3.46

function LoadGoogleMainScript() {

    try {

        $('#destination').hide();

        var MapBaseURL = window.external.getMapBaseURL();

        var key = window.external.GetMapKey();

        if (MapBaseURL == null || MapBaseURL == undefined || MapBaseURL == "" ||

            key == null || key == undefined || key == "") {

            window.external.MapErrorHandler("1071", "");

            return;

        }

        var googleMapsVersion = "3.46";

        var libreries = "&sensor=false&libraries=geometry,places";

        var MapURL = MapBaseURL + "js?v=" + googleMapsVersion + "&key=" + key + libreries;

    4. clear cache (on all user clients)

     5. Open Dispatch Console map

For our hosted customers, we will communicate when this change is made on your servers after which you can clear the client cache and work with Google Maps.

Kind regards,

Phil

Any idea when Goggle may update API again. and is IFS working on a permenant fix?

file can be found at location: C:\Program Files\Astea Alliance 15.0\WebSite\Maps\Astea.GIS.Services.GoogleMaps.GoogleApiServices\MainMap\initialization.js

We didn’t clear the cache and it works. What cache do you mean?

@AnthonyCentric   How to clear browser cache

Please be aware, the file locations do differ between v15.3 and v15.1 for example the initialization.js is located:

v15.1

\Program Files\Astea Alliance 15.0\WebSite\Maps\GoogleMaps\MainMap

v15.3

\Program Files\Astea Alliance 15.0\WebSite\Maps\Astea.GIS.Services.GoogleMaps.GoogleApiServices\MainMap

Any idea of the location or filename for version 12.0??

We have the location \Program Files\Astea Alliance 12.0\WebSite\Maps\GoogleMaps\MainMap but there is no file called initialization.js!

Thanks.

@ktolkacevic 

Yes IFS R&D is working on a more permanent solution.  Unfortunately when Google may discontinue this version is not known to me.

@MMallinger

That is correct, the file is different in v12 than in v15.  What I am told is for V12 the name of the file is GoogleMap.htm and not initialization.js

Located in folder \website\Maps\.GoogleMaps\MainMap\GoogleMap.htm

The basic instruction is still the same, update the googleMapsVersion to 3.46

Also make the same change in the Website\Maps\GoogleMaps\MiniMap\GoogleMiniMap.htm file.

There doesn’t appear to be any reference to the googleMapsVersion in the MiniMap file.
 

Thank you Phil, this has worked.

@MMallinger, what @Andrew D'Antonio  was referring to is this for v12.5

website\Maps\.GoogleMaps\MiniMap\GoogleMiniMap.htm

var MapURL = MapBaseURL + "js?v3.46&client=”  MapClientID+ libreries;

This is a change to allow the minimaps to work (the ones you see in service orders, etc.) and not for the DC Maps.

Got it. Thank you Phil.

HI Phil for our V15.1 or 15.2 we have applied the fix for the DC but we still have an issue on the address finder it’s not working we have an error and can’t use it. Do you have a workaround for this module ?

A document has been created as there were different instructions how to implement the changes for the work-around across different Alliance versions with instructions per version.

Also included in this document are instructions for a work-around involving the address finder.

Updated document to correct path for v14.

Thank you @Phil Seifert for documenting this, I’ve encountered this error while QA testing a customer, and this was very useful.

Thank you Phil I just encountered this issue with another customer. This post is really useful. 

Please note:

After applying this change and then later deploying or reinstalling a HF release prior to the latest HF releases for the respective versions, it is important you check the configuration change as they may revert.

If in doubt, please contact IFS Alliance support teams for your local area for inquiries.

The instructions attached above are only for earlier versions of googlemap versions.to configure as 3.46.

If your map version after updating to a later HF is now 3.47 or higher, do not revert back to a lower number or make changes to the files.  If you have an issue with maps, please contact your local Alliance support team.

The Alliance versions with the new control are the following:

• V14 HF27
• V15.1 HF12
• V15.3 HF5 - will be released next month with the new control
• V15.4 SU2

Therefore do not use the attached instructions with this topic for these versions or higher.