TGIF is here — and no, we don't mean the weekend (well, maybe a little). Welcome to Thank Goodness It's FME, your new Friday destination for tips, tricks, and everything you love about FME!
Each week, our team dives into a topic they're passionate about — whether it's a hidden gem in the Knowledge Base, a behind-the-scenes Q&A, or a feature that'll change the way you work.
We'd love to hear from you too — drop your ideas in the comments and help shape what's coming next
FME 2026.1 Release Highlights
We are all super excited about our FME 2026.1 release earlier this week! If you haven't had a chance to check it out yet, please take a moment to look at the new features.
Our team has taken some time to highlight some of their favourite new features and changes. Take a look below!
Data Caching in FME Form
Live data caching in FME Form 2026.1 gives users real-time visibility into their data, even while a translation is still running. Instead of waiting for a workspace to complete or terminate, users can inspect caches as they're generated, spot issues early on, and keep authoring without breaking the flow.
Want to learn more about this feature? Watch our short demo video here.
Multiple Geometry Improvements in FME Form
FME keeps making multi-geometry workflows smoother — here's what's new:
No table? No problem. The Microsoft SQL Server (ADO) Writer can now create multiple spatial columns from scratch. Just define them in the Geometry Definition table and FME matches everything up by name.
More control in your transformers. GeometryNameSetter, GeometryRemover, and GeometryExtractor can now target specific geometry columns. Plus, a new GeometryCopier lets you duplicate a geometry under a new name in seconds.
Merge streams, keep your geometries. FeatureMerger and FeatureJoiner now preserve separate geometry columns when combining data — no more choosing between joined data and organized spatial info.
Want to learn more about this feature? Watch our short demo video here.
Data Virtualization Enhancements
In the 2026.1 release, asynchronous Data Virtualization endpoints support a callback URL parameter, allowing external systems to receive a direct notification upon job completion rather than repeatedly polling for results. When a DV request finishes, Flow automatically posts a structured payload, including the request ID, status, and result URL, to the callback target. This enables fully automated downstream orchestration, eliminating manual intervention between your DV workflow and the systems that depend on its output.
Want to learn more about this feature? Watch our short demo video here.
Automatic SSL Certificate Import in FME Flow
Since the 2025.1 release, users have been able to automatically configure FME Flow for HTTPS by providing a valid PFX certificate to the installer. However, when using a self-signed certificate, manually importing the certificate into FME Flow’s trusted cacerts was often required for Flow to function properly.
In 2026.1, this additional step happens automatically! This means that users can skip this manual step going forward, and start submitting jobs successfully immediately after installing FME Flow.
Coming up next…
Next week, we're diving into Service Accounts in FME Flow — a game-changer for how you run and manage your workflows. You won't want to miss it! In the meantime, drop a comment, share a thought, or just say hi. We'll see you next Friday. Thank Goodness It's FME! 🎉