Hi everyone,

From mid November 2026, changes on the Google Maps side will affect apps that use some functionality provided by OutSystems Maps. These changes come from Google, not by OutSystems Maps, and they might require action from you.

What is happening

Google decommissioned (removed) some features from the Maps JavaScript API:

You can find the details in the Google Maps deprecations page.

Why this affects your apps now

Google requires the script for rendering Google Maps functionality to always be loaded from their servers, and only limited versions of the Maps JavaScript API are available. 
Each quarter (mid February, May, August, and November) a new version is released and the oldest one is decommissioned. See the Google Maps versions page for more information.

When an app asks for a version that is no longer available, Google silently loads the latest available version based on your Google Maps Platform channel setting instead.

Up to version 2.4.0, OutSystems Maps loads Google Maps version 3.63, but since Google will delete this version in mid November 2026, from that moment your apps will load version 3.66 or 3.67 depending on your account settings, even if you don't update OutSystems Maps.

In these latest versions, the Heatmap Layer, KML Layer and the Drawing Tools no longer exist. If your app uses them, and references a version of OutSystems Maps < 2.3.1, those functionalities will stop working at runtime, in production, with no warning at design time.

What we did during the year

Each time Google announced a deprecation, we released a direct alternative in OutSystems Maps:

• OutSystems Maps 2.3.1(April 2026)
  • New HeatmapLayer block, powered by deck.gl, to replace the Google Maps Heatmap Layer. The old block is now DEPRECATED_HeatmapLayer.
  • Drawing Tools now use TerraDraw as the default provider, instead of the Google Maps Drawing Library.
    
    
• OutSystems Maps 2.4.0(July 2026)
  • KML Layer now renders with deck.gl and loaders.gl, instead of the Google Maps KML Layer.
    
    

What you need to do

1. Update your apps to OutSystems Maps 2.4.0 or later.
2. If your app uses DEPRECATED_HeatmapLayer, replace it with the new HeatmapLayer block. We can't do this for you, because it is a different block in your app. Once Google removes the feature, DEPRECATED_HeatmapLayer will not work anymore.
3. No action is required for the KML Layer or the Drawing Tools to work, since changes were made under the hood to seamlessly support the provider deck.gl and TerraDraw, respectively.
4. Test your maps, then publish to production.

Already using the latest OutSystems Maps version but haven’t changed the site property yet? Don't wait for our next release. After you complete the steps above, change the value of the GoogleMapsVersion site property to 3.66 right away, so your apps stop requesting version 3.63 before Google deletes it.

Not in time to push changes into production? Simply change the value of the GoogleMapsVersion site property to 3.64, which will enable the app to use the decommissioned Google functionality until mid February 2027.

Please do this as soon as possible. Mid November is close.

In either case, upon updating the version of OutSystems Maps to the upcoming release, we recommend resetting the value of the GoogleMapsVersion site property to its new default value.

What comes next in OutSystems Maps

In the next OutSystems Maps version, 2.5.0, we will change the Google Maps version loaded by default to 3.66, the new quarterly version.

We also looked at using version 3.64, which still includes these features. But Google will delete it in mid February 2027, so it would only delay the same problem by a few months. Moving to 3.66 gives you a stable base and the alternatives above are already available.

If you have questions or face any issue during the migration, let us know in the comments.

Thank you,
UI Components team