Skip to main content
Question

Communicate breaking changes in packages more clearly to the user

  • February 12, 2026
  • 2 replies
  • 89 views
mgg_beca
Enthusiast
Forum|alt.badge.img+17

Hi there,

In Esri ArcGIS Connector safe.esri-agol version 3.17.0 a number of changes were made to the way the Esri writer handles global IDs.  Some of these changes resulted in previously published workspaces no longer functioning after the package on Flow was updated.

This is an admin nightmare, as unless we prevent all publishers from uploading packages, we cannot prevent them from deploying a new version of a package that may break existing workflows.

I have two suggestions:

  • Please put the latest changes of the package at the top of the description in the FME Form Dialog box. Currently the user has to click a link to go to the item in the Hub and then find the version in the History.
  • Please clearly indicate any changes that are more than bug fixes, and that may impact previously published workspaces.

Thanks,

Marc

      2 replies

      jamatsafe
      Safer
      Forum|alt.badge.img+17
      • jamatsafeSafer
      • Safer
      • February 13, 2026

      Hi ​@mgg_beca,

      I’m sorry to hear the package updates are causing workspaces to stop working. Thanks for raising this and for the suggestions on improving visibility of changes, they do make a lot of sense. As we look into this, are you experiencing the global ID issues on AGOL or Enterprise Portal or both? Do you recall which package version you were you using previously? 

      Please submit a support ticket with a minimal repro workspace and any relevant logs/error messages so we can reproduce and document the behavior clearly. Given the impact, having a concrete example like this is especially helpful for ensuring it’s reviewed by the appropriate team. Alternatively, I also recommend submitting an FME Idea and outlining your use cases. This makes it easier for others to upvote, raise visibility to our developers, and help us gauge broader interest for potential future improvements.

       

      ebygomm
      Influencer
      Forum|alt.badge.img+46
      • ebygommInfluencer
      • Influencer
      • February 17, 2026

      Since the process to update a package on FME Flow suggests you need to uninstall the previously published package

      Introduction to FME Packages – FME Support Center

      Then I don’t think you should be allowed to upload a package from FME Flow if it already exists.

      Community Stats

      32,329
      Posts
      123,141
      Replies
      40,359
      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.