Skip to main content

We have several Database Connections for our workflows, and most of them are for our county ArcSDE geodatabases. Each one has a Default version and a Sync version for editing, and we have all of the connection strings saved with the Sync version.

We use FME through a Data Interoperability license, and after FME updated to 2025.0.0.0 (with the ArcGIS Pro update to 3.5 from 3.3) the Version Type is now set to ‘NONE’ for all of them instead of ‘Version from SDE Connection’ like it was before, and the Transactional Version is set to Default automatically. Plus, it seems to us that our connections strings have changed too. We found this the hard way, after changes were written straight to Default.

So I guess I’m writing to see if anyone else had this problem, or to see if we’re missing something - I haven’t found any posts or fixes in the changelog about it yet. And, are there tips for how we should be storing these database connections?

 

(I am aware it could just be a Data Interop issue - we’re working on getting on FME Form soon!)

 

Thanks!

Here is an article listening known issues https://support.safe.com/hc/en-us/articles/34243509378061-Known-Issues-in-FME. There are some listed from previous versions for Arcgis online and portal feature services, but I couldn’t see anything relating to SDE. 
Check the compatibility between FME and Esri versions align https://support.safe.com/hc/en-us/articles/25407724093837-Notes-on-FME-and-Esri-Versions-and-Compatibility

One possibly fix is to ‘upgrade’ all your readers… and their feature types. https://docs.safe.com/fme/html/FME-Form-Documentation/FME-Form/Workbench/Updating-Readers-Writers.htm

Upgrade to 2025.1 which is coming out next month. https://fme.safe.com/changelog/?_change_log_product=FMEFORM&_change_log_version=2022000002%2C2025010000 and use SDE keyword. 

  • there are various fixes 

     

Otherwise lodge to safe support https://support.safe.com/hc/en-us/p/Support