Skip to main content
Solved

Workaround for geometry parameter basemap bug

  • March 12, 2026
  • 4 replies
  • 107 views
nordpil
Enthusiast
Forum|alt.badge.img+12

Hi all, we are on Flow 2025.2 and we use Geometry Parameter for quite a few ws apps. Now we are living with the bug FMEFLOW-26285

Changes to the default basemap of a geometry user parameter under the Parameter Defaults when creating/editing a Workspace app do not get applied to the Workspace app. Users accessing the workspace app will see that the default basemap is unchanged. 

Any tips for a workaround? Can one change the default using javascript in the webpage possibly?

Best answer by zoe.forbes

Hi ​@nordpil, sorry for the delayed response. The workaround is below, but please note:

  1. This isn’t officially supported and might have unintended consequences. To reduce the risk, make a copy of the edited file (to restore if anything goes wrong), and make a backup of your Flow instance.
  2. This workaround won’t persist when Flow is upgraded or reinstalled.
  3. As far as I can tell, this changes the default basemap everywhere across the Flow instance.

Here’s the workaround:

  1. On the machine hosting Flow, navigate to <Install Dir>/Utilities/tomcat/webapps/fmeserver/dist/angular-frontend/. <Install Dir> is set during installation and is C:/Program Files/FMEFlow on Windows by default.
  2. Find a file with name main.*.js. For example, this could be main.643h2jw8830y1jea.js. Open the file with admin permissions to allow editing.
  3. Find and replace as follows. There should be only 1 match:
  4. Save the .js file. Verify the changes have taken effect. If they haven’t, first try clear the cache, then try restart Flow.

Please let me know if you have any questions about this!

    4 replies

    zoe.forbes
    Safer
    Forum|alt.badge.img+6
    • zoe.forbesSafer
    • Safer
    • March 17, 2026

    Hi ​@nordpil,

    I had a look into this, and unfortunately a fix isn’t currently on our roadmap. I’ve updated our internal ticket though to let the relevant Product Manager know the impact this is having. Our best supported workaround remains asking users to update the basemap URL manually, each time the app is opened.

    I had a look into this myself though, and did find a unsupported workaround which updates the default basemap globally across FME Flow. This means changes would apply to every Workspace App, the Run Workspace page, and anywhere else Geometry User Parameters appear.

    The workaround requires changing Flow configuration files and is unsupported because small mistakes can lead to components of Flow breaking, requiring a full backup/restore to fix. It would also need to be reinstated every time Flow is updated.

    Let me know if you’d like details of this.

      nordpil
      Enthusiast
      Forum|alt.badge.img+12
      • nordpilEnthusiast
      • Author
      • Enthusiast
      • March 18, 2026

      ​@zoe.forbes Yes please, it would be interesting to look at this workaround!

      zoe.forbes
      Safer
      Forum|alt.badge.img+6
      • zoe.forbesSafer
      • Safer
      • Best Answer
      • March 25, 2026

      Hi ​@nordpil, sorry for the delayed response. The workaround is below, but please note:

      1. This isn’t officially supported and might have unintended consequences. To reduce the risk, make a copy of the edited file (to restore if anything goes wrong), and make a backup of your Flow instance.
      2. This workaround won’t persist when Flow is upgraded or reinstalled.
      3. As far as I can tell, this changes the default basemap everywhere across the Flow instance.

      Here’s the workaround:

      1. On the machine hosting Flow, navigate to <Install Dir>/Utilities/tomcat/webapps/fmeserver/dist/angular-frontend/. <Install Dir> is set during installation and is C:/Program Files/FMEFlow on Windows by default.
      2. Find a file with name main.*.js. For example, this could be main.643h2jw8830y1jea.js. Open the file with admin permissions to allow editing.
      3. Find and replace as follows. There should be only 1 match:
      4. Save the .js file. Verify the changes have taken effect. If they haven’t, first try clear the cache, then try restart Flow.

      Please let me know if you have any questions about this!

      nordpil
      Enthusiast
      Forum|alt.badge.img+12
      • nordpilEnthusiast
      • Author
      • Enthusiast
      • March 25, 2026

      Thanks, I think the instructions are clear, but I’ll hold off a bit on trying that...

        Community Stats

        32,431
        Posts
        123,238
        Replies
        40,557
        Members
        Terms & ConditionsCookie settingsAccessibility statement
        A product of
        Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.