Skip to main content

FME 2025.2 - Feature Highlights

  • November 25, 2025
  • 14 replies
  • 466 views
SagitAtSafe
Safer
Forum|alt.badge.img+2

FME 2025.2 continues our momentum of innovation with a release focused on performance, compatibility, and developer experience. With new Delta Lake and Microsoft Fabric readers, system browser-based authentication, an IFC writer, official OS support for macOS 26 (Tahoe), and more, FME 2025.2 brings new power and reliability to every part of the platform, enabling teams to automate, integrate, and innovate with their data with greater confidence. 

Feature Highlights

Delta Lake & Microsoft Fabric (Onelake / Lakehouse) Reader: The new Delta Lake Reader connects directly to Delta Lake tables and reads and processes data from Delta Lake  environments. With SQL-like querying capabilities, users can easily integrate Delta Lake data into their workflows for analysis or transformation. The reader supports Amazon S3 and Azure Data Lake, with additional platforms planned for future releases.

Using the new Delta Lake Reader, FME can now connect to Microsoft Fabric’s OneLake as well, allowing direct reading from SQL Databases and Lakehouse data, including data stored on Amazon S3 and connected to OneLake via a shortcut. With Microsoft Entra ID authentication and ADLS Gen2 DFS API compatibility, data teams can automate and integrate Fabric OneLake data within FME—no manual exports or custom code needed.

Use Your System Browsers for OAuth 2.0 and Flow SAML Connections: FME Form now uses your system’s default browser (Chrome, Edge, Safari, etc.) for authenticating and authorizing FME OAuth 2.0 Web Services, and FME Flow SAML connections. This update delivers a smoother, more secure sign-in experience that aligns with enterprise IT standards.

 

New IFC Writer: Now out of beta, the IFC Writer aligns FME with the latest IFC 4.3 standards and BIMFitCheck certification. The upgraded IFC Writer simplifies BIM data export and improves interoperability with ArcGIS and other GIS/CAD tools, streamlining how AEC professionals move from design to operational workflows and digital twins.

Expanded Support For macOS 26 (Tahoe): FME Form now runs seamlessly on Apple’s latest operating system with full compatibility and performance. With proactive testing ahead of macOS 26’s release, customers can confidently upgrade and stay current with Apple’s evolving platform.

Additional Enhancements

FME Platform

Expanded User Parameter Support Across Platform: User parameters are more powerful and flexible across FME Form and Flow, making it easier to customize workspaces, build dynamic transformers, and create adaptable Flow Apps. New parameter types like Attributes to Expose and Encoding, along with expanded options such as Choice summaries and an improved interface for controlling visibility and baseline configuration, lets users design cleaner, more interactive user experiences without complex workarounds.

FME Form

Better Python User Experience — External Editor User Flow: The Python scripting experience is now smoother and more modern with direct VS Code and PyCharm integration. Users can write scripts using IDE tools like auto-completion, syntax checking, and debugging while retaining access to FME Objects. This makes scripting faster, more powerful, and more intuitive.

 

Updated Coordinate System Parameter: The Coordinate System parameter for datasets now only appears for spatial integrations and has been moved to the Parameters dialog, reducing clutter and improving consistency across workflows.

 

Optional Input Ports: Transformers can now run without a connected input feature, eliminating the need for adding placeholder features from a Creator. This reduces workspace and transformer parameter clutter. Existing workspaces remain unchanged, and transformers will still process the features you connect as before.

 

Required and Invalid Parameter Indication: The FME Form UI now follows industry best practices by marking required parameters with a red asterisk and showing invalid fields with a red outline only after edits have been made. The former red-filled fields did not always meet accessibility standards; the new approach provides clearer, calmer guidance instead.

FME Flow

Improved Developer Experience for Data Virtualization APIs: The Data Virtualization APIs now offer a better developer experience with optional long polling for reduced request overhead, flexible content-type handling for broader compatibility, and added support for JSON array schemas and modular schema referencing to simplify complex data modeling.

Parameter Pre-Loading for Flow Apps: Flow Apps now support parameter pre-loading, allowing values to be loaded dynamically before a form is displayed. Authors can pull parameters from external URLs, FME workspaces, or JSON configurations, enabling smarter, data-aware app experiences that reduce manual input and simplify multi-step workflows. An in-product guide helps users implement this feature easily. 

Refreshed Navigation in the Flow UI: The Flow UI has been refreshed with a new sidebar that delivers cleaner, more consistent navigation. Collapsible sections have been replaced with a simple, always-visible layout that aligns with FME’s updated design and improves usability.

FME Realize

Straight Line Calibration: A new compass calibration method improves directional accuracy in augmented reality experiences. Simply walk in a straight line to help the app precisely align compass and orientation data. Users can either follow the prompt to calibrate, decide to skip it, or redo calibration at any time to ensure reliable AR model placement, even in challenging environments.

Transformers

StringReplacer Now Supports Multiple Replacements: The StringReplacer transformer now allows multiple replacement types in a single transformer using a new table-based interface. This update simplifies workflows and replaces the need for StringPairReplacer, which is now deprecated.

Snapper and AnchoredSnapper — Add 3D Support: Snapper and AnchoredSnapper transformers now support 3D snapping for End Point and Vertex snapping types. A new Snapping Dimension parameter lets users include Z values in snapping calculations, improving precision in 3D workflows. 

Note: Support for Segment Snapping 3D is coming soon.

New and Updated Integrations

Microsoft Fabric (MS SQL and Warehouse on Fabric) Reading / Writing: FME now connects directly to Microsoft Fabric’s SQL Databases using the Azure SQL Database (JDBC MSSQL) reader/writer with Entra ID, MFA, and Service Principal support. It also supports reading data from Warehouse on Fabric, helping IT teams integrate Fabric data securely and efficiently.

Snowflake Native OAuth Support: FME 2025.2 adds support for Snowflake’s native OAuth authentication, giving users a secure and simplified way to connect without relying on external identity providers. This update aligns with Snowflake’s shift away from single-factor password logins and ensures continued compatibility with their latest security requirements.

PostgreSQL Vector Support: Initial support for pgvector enables FME to read and write native PostgreSQL vectors, enabling similarity searches and AI-driven data processing directly within FME workflows.

DropboxConnector Now Using New SDK: The DropboxConnector has been upgraded to the latest SDK to maintain secure, reliable connectivity ahead of Dropbox’s API and certificate updates in 2026.

Excel Reader and Writer Enhancements: FME now supports true Excel tables that automatically expand to include new data, plus improved handling for hidden sheets, built-in number formats, empty cells, and merged features, ensuring smoother, more accurate Excel integration.

Native Geo Parquet Support: Native support for geometry and geography types under the Parquet Geo specification allows direct storage of CRS and geospatial metadata, improving performance and compatibility for geospatial datasets.

Database Performance Improvements with "Max Features to Read Per Feature Type" Option: Database reading is faster and more efficient with optimized handling of the “Max Features to Read per Feature Type” setting, which stops reading once limits are reached. This applies across major databases, improving performance for large datasets.

 

14 replies

vlroyrenn
Enthusiast
Forum|alt.badge.img+14
  • Enthusiast
  • November 25, 2025

So these optionnal input ports make the likes of SQLCreator and PythonCreator obsolete, if I understand correctly?


charry
Supporter
Forum|alt.badge.img+5
  • Supporter
  • November 26, 2025

When will 3dtiles 1.1 be upgraded?


redgeographics
Celebrity
Forum|alt.badge.img+62

So these optionnal input ports make the likes of SQLCreator and PythonCreator obsolete, if I understand correctly?

No, I think they still have a very useful purpose. But it would remove the need for a separate Creator before, e.g. triggering a HTTPCaller to read from an API.


alexapi
Participant
Forum|alt.badge.img+6
  • Participant
  • November 26, 2025

So these optionnal input ports make the likes of SQLCreator and PythonCreator obsolete, if I understand correctly?

Yes, that’s how I understand it too — these were already the “no‑Creator” versions of SQLExecutor and PythonCaller.
 


ebygomm
Influencer
Forum|alt.badge.img+46
  • Influencer
  • November 26, 2025

I’m not sure my brain will be able to cope with optional input ports, especially if reviewing a workspace developed by someone else. 


alexbiz
Influencer
Forum|alt.badge.img+30
  • Influencer
  • November 26, 2025

I’m not sure my brain will be able to cope with optional input ports, especially if reviewing a workspace developed by someone else. 

 

Yeah, I’ve always liked having a Creator as a universal starting point. I’m a bit worried this could impact readability.
For example, I often review workspaces that aren’t very clean or are still in progress, where enabled but unconnected transformers are left behind from previous tests. Until now, it was clear to me that anything without an initiating feature wouldn’t run and could safely be ignored. With optional input ports, I’m afraid it may become harder to distinguish what’s actually part of the workflow from what’s just leftover test logic.

On top of that, I’m not really a fan of “multi-task” transformers in general... I prefer keeping operators unitary and clearly focused. It helps maintain clarity, especially in larger workspaces.

 

Regarding the expanded User Parameter support across the platform and parameter pre-loading in Flow Apps, I’m really curious to explore what has been done. It’s great to see improvements happening on the user-parameter side!

 

And I fully support the change made to the Coordinate System parameter. It’s rarely used, and I usually recommend avoiding it altogether in favor of explicitly using a CoordinateSystemSetter when needed.


redgeographics
Celebrity
Forum|alt.badge.img+62

I’m not sure my brain will be able to cope with optional input ports, especially if reviewing a workspace developed by someone else. 

Yeah, I think I’m the same. I would argue for clear documentation of course.


PierreAtSafe
Safer
Forum|alt.badge.img+8

So these optionnal input ports make the likes of SQLCreator and PythonCreator obsolete, if I understand correctly?

Yes ​@vlroyrenn, that’s the goal! It was a pretty confusing concept especially for new users. We are trying to get rid of Creators and the like when not necessary.


deanatsafe
Safer
Forum|alt.badge.img+6
  • Safer
  • November 26, 2025

When will 3dtiles 1.1 be upgraded?

Thanks ​@charry for asking about 3DTiles. I agree this update is long overdue. This is one of the highest priority updates for our team, and is on the roadmap for FME 2026.x. This work will include both the update to the latest released version of the OGC 3d Tiles standard, and significant improvements to our current writer.


hkingsbury
Celebrity
Forum|alt.badge.img+65
  • Celebrity
  • November 27, 2025

External Python editing!! Yay!


charry
Supporter
Forum|alt.badge.img+5
  • Supporter
  • November 27, 2025

When will 3dtiles 1.1 be upgraded?

Thanks ​@charry for asking about 3DTiles. I agree this update is long overdue. This is one of the highest priority updates for our team, and is on the roadmap for FME 2026.x. This work will include both the update to the latest released version of the OGC 3d Tiles standard, and significant improvements to our current writer.

I hope to update soon, I have been waiting for a long time. FME is indeed lagging behind in 3D. Did you see that you used OpenSceneGraph at the bottom and switched to VulkanSceneGraph? Or call Blender? I don't quite understand


martinkoch
Supporter
Forum|alt.badge.img+22
  • Supporter
  • November 27, 2025

Very enthusiastic about enhanced Microsoft Fabric and GeoParquet support!


antoine
Enthusiast
Forum|alt.badge.img+7
  • Enthusiast
  • November 27, 2025

I’m not sure my brain will be able to cope with optional input ports, especially if reviewing a workspace developed by someone else. 

 

Yeah, I’ve always liked having a Creator as a universal starting point. I’m a bit worried this could impact readability.
For example, I often review workspaces that aren’t very clean or are still in progress, where enabled but unconnected transformers are left behind from previous tests. Until now, it was clear to me that anything without an initiating feature wouldn’t run and could safely be ignored. With optional input ports, I’m afraid it may become harder to distinguish what’s actually part of the workflow from what’s just leftover test logic.

On top of that, I’m not really a fan of “multi-task” transformers in general... I prefer keeping operators unitary and clearly focused. It helps maintain clarity, especially in larger workspaces.

 

Regarding the expanded User Parameter support across the platform and parameter pre-loading in Flow Apps, I’m really curious to explore what has been done. It’s great to see improvements happening on the user-parameter side!

 

And I fully support the change made to the Coordinate System parameter. It’s rarely used, and I usually recommend avoiding it altogether in favor of explicitly using a CoordinateSystemSetter when needed.

You need a clear UI to see if it is just a part of “not used process” vs a starting point. It depends on the implementation. Give a chance to the product.  


deanatsafe
Safer
Forum|alt.badge.img+6
  • Safer
  • November 27, 2025

When will 3dtiles 1.1 be upgraded?

Thanks ​@charry for asking about 3DTiles. I agree this update is long overdue. This is one of the highest priority updates for our team, and is on the roadmap for FME 2026.x. This work will include both the update to the latest released version of the OGC 3d Tiles standard, and significant improvements to our current writer.

I hope to update soon, I have been waiting for a long time. FME is indeed lagging behind in 3D. Did you see that you used OpenSceneGraph at the bottom and switched to VulkanSceneGraph? Or call Blender? I don't quite understand

Hi ​@charry . Are you referring to Data Inspector? I believe we still use OpenSceneGraph. I have not heard of VulkanSceneGraph in the context of FME. We also have enhancements for 3D support in Data Inspector on our road map. I cant point to a specific milestone, but I can certainly add your comment as a reference / vote.