Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Hi,We have a large SharePoint deployment. The site dialog does not have a search button. The document library does. I suggest you add search to the site dialog. Thanks,Marc
Some general improvements for the Terminator transformer I am thinking of:The ability to terminate with a FME_FAILURE or ABORTED or maybe even a new TERMINATED status (relevant for Server). An FME_FAILURE happens when FME crashes or experiences some other problem (e.g. missing transformer). When the Terminator caused the workspace to quit, this typically happens because of a "user handled exception", which might also be interpreted as a cancellation, but now it's always FME_FAILURE as well. Either way, it gives me better insight in what went wrong if this status type could be changed.The ability to set custom data that should be sent upon failure, which can then be used as the "Data To Post" for notification topics. Upon failure, nothing gets written to the "Data To Post" writer, but it would be nice if we could at least get something back. In this case, that would be the custom data that was set in the Terminator.I would like the error message that I specified in the Terminator to stay exactly the way it is. When a job terminates on Server, it passes the Termination Message on to the statusMessage attribute from the job result. Just like in workbench, it always prefixes this message with "<Transformer Name>: Aborting Translation as directed by mapping file. Message is ...". I would love to see that prefix removed, because now I need to remove it myself since it is confusing to an end user who is not familiar with FME. Might as well officially integrate the functionality of the MessageLogger by 1Spatial.Any other suggestions...?
The FME ArcGIS Online writer should expose a time zone setting that allows you to set the time zone of your data when publishing or appending data. By default, ArcGIS Online assumes all data is stored in UTC but when publishing directly to ArcGIS Online through the UI or using the ArcGIS Python API the time zone can be set to the time zone of your data. This setting in the writer would allow dates to be published and updated accurately.
In the current situation + Finland & Sweden joining NATO there is more demand to support Nato Vector Graphics (NVG) -format. Just read a RFP where it’s a must and waiting for more similar RFP’s to come. It’s not just the military people who ask for it, it’s also e.g. border control and who ever is providing services for them.
Please vote for this format if you think it should be in FME: https://www.geonovum.nl/uploads/documents/220405-JSON-FG.pdf https://docs.ogc.org/DRAFTS/21-045.html
Currently the Esri ArcGIS Server Feature Service transformer does offer a handful of authentication types, but non of them offers the use of a web connection.It would be so easy...
I'm interested in reading the new Esri Utility Network.I wonder if others are? What systems are you going to? What is most important to you?Maybe writing is more your thing? Vote and give feedback for writing the Esri Utility Network here.Note: The reason for a new format is as a result of the Utility Network being completely Services-based. As such, the underlying Geodatabase is inaccessible apart from accessing it via the Feature Service.
Differentiation of user created web services from web services template that come out of the box or from newly insatalled FME Hub packages would be nice and make it easier for users to manage their own web services.
It would be super nice if I can compress 3D Tiles data (glTF) with DRACO (https://google.github.io/draco/). File sizes get super small and rendering will be faster. I want to have an option in the 3D Tiles writer!
It would be great to have for ZIP files a Reader similar to the "Directory and file pathnames" one, so you could see the contents of a ZIP file without opening it. For doing so now I had to use the Python zipfile library.
Current situation: FME Flow’s Git integration relies on broad‑scope personal access tokens, which many security policies prohibit.Why fine‑grained: Fine‑grained PATs were created to align access with what really matters—specific repositories, operations, and lifetimes—enforcing least‑privilege and reducing risk. This will make it easier to implement version control because current organizations like ours don’t allow broad scope.Request: Add native support for GitHub fine‑grained PATs in FME Flow version control so teams can adopt it while meeting modern security policies.
It would be nice if FME Flow could be set up to communicate with other servers like Autodesk Construction Cloud and Sharepoint using OAuth2- client_credentials. Currently most integrations are based on user authentication which requires users to validate their password once in a while.It could be documentation is not complete for these types of flows or packages are not yet prepared for this. But every integration documentation should have a chapter: how to integrate the client_credentials flow.
For Security in FME Server , it would be nice to include job queues as items that can be associated to roles. For those of us running distributed engines, this would allow us to control what jobs can go to what engines by FME server role, and we could set up engines with different service accounts, so that they would have different permission on things such as the enterprise file system.
In many organizations, FME Flow is managed centrally and engine resources are shared across different teams or departments. However, FME Flow currently does not offer any permission control on engine queues.At the moment, when a user/author has access to view queues, they can see all queues defined on the FME Flow instance. This can be problematic in environments where engine usage needs to be compartmentalized. Example use caseThe IT department is allowed to use 2 specific engines/queues.The GIS team is allowed to use 3 different engines/queues.However, because queues are not permission-restricted, any user can select any queue when creating schedules, automations, or running workspaces if they have access to the advanced part. Suggested ImprovementAdd the ability to control which engine queues a user or role can see and use.This would allow administrators to:Restrict access to specific queues based on user roles or groups. Prevent users from unintentionally using engines they are not supposed to access. Improve resource isolation and governance in multi-team or multi-department FME Flow environments.
Following a helpful and enlightening conversation with some Safe staffers I learned that Safe is working on some upgrades to the FME software update process and I was encouraged to add my thoughts as an Idea. I’m sure other feedback would be welcome as well!In our case, we have a client who is restricted to an older Esri software version due to various dependencies but this means they are now also restricted to a maximum FME version of 2025.2.x as 2026.x does not support their older Esri software.It would be a significant help if the FME upgrade process could be made more modular so that, for example, core functionality (e.g. transformers, reprojection, etc.) could be updated while older readers/writers could be retained for backwards compatibility.Safe have started down this path with the concept of packages for certain functionality but it would be great if this could be extended to provide even more flexibility in the upgrade process.Upvote and add a comment if you have specific use cases which would be helpful for you!
The current web interface for managing resources does not allow for renaming files and folders. On FME Server you generally will have other access to the filesystem (at least an admin would have), but on FME Cloud this is not the case and renaming a file would mean removing it and re-uploading it under a different name. So an option to rename files and folders through the resources interface would be very useful.
I have some workspaces that are large and have too many lists/tables etc. These will not run with Feature Caching enabled - as they will use 20+ hours. Without it, its done in less than 1 hour. Other workspaces I like to have Feature Caching enabled, and I easily forget to switch back.Make a parameter - similar to Rejected Feature Handling - that is "per workspace". For instance:Feature Caching: Enabled / disabled
When inspecting geometry details on the View of Data Inspector, need to see previously viewed extents in some cases. The user can go back and forth quickly if there were Undo/Redo functionality for the View window (tool buttons and menu commands).
At the moment DI's Orbit mode rotates around the view window origo. Better way to rotate a 3D dataset, is to orbit around mouse click and not around the view window origo. That way you don't need to first zoom/pan and then rotate to navigate in large 3D datasets.
Expose an OpenAPI document for FME Server Webhooks.We are increasingly using FME Server Webhook as a method for creating REST API endpoints for third-party developers to build against. It would be very powerful for FME Server webhooks to expose OpenAPI specifications.
We use Azure Entra ID to log in FME Flow. The only user that uses the username/password option, is the admin-user.My idea:move the option for the admin-user to login to a different url. add the option to make this “admin url” only available from a local network (or add some other security to limit access to this url). This way external users can never log in as the admin user. add the possibility to remove the “username/password” login from the login-page. When a user is already logged in via the browser with the users Azure Entra ID, this will cause the user to automatically login to FME Flow.Benefits:more secure users don't have two login options which is confusing for my users. They tend to use the username/password-option (which does not work for them), while they only have to click the “Sign in with Microsoft”-button Better user experience: automatically logged in, without having to click an extra button.
The Hexagon Geomedia SQL Server Warehouse does not allow for displaying the list of databases dynamically within the server/instance the way that other SQL readers do, i.e. Microsoft SQL Server Spatial. Can this functionality be added?
Official FME Flow API v4 documentation does not show the latest Openapi specification 3.01. OnFME 2026.1 the following OpenAPI specification is available: "openapi": "3.0.1", "info": { "title": "FME Flow REST API V4", "description": "FME Flow REST API V4 is our stable REST API.", "contact": { "name": "Safe Software Inc.", "url": "https://www.safe.com/" }, "version": "4" }, "servers": [ { "url": "https://***/fmeapiv4", "description": "Generated server url" } ], But the public documentation shows version 3.0.1 alphahttps://docs.safe.com/fme/html/fmeapiv4/docs/schema/static.json { "operationsSorter": "alpha", "tagsSorter": "alpha", "docExpansion": "none", "openapi": "3.0.0", "info": { "title": "FME Flow REST API V4", "description": "FME Flow REST API V4 is our stable REST API.", "contact": { "name": "Safe Software Inc.", "url": "https://www.safe.com/" }, "version": "4" },
Transforming lidar data to buildings or other simple objects is currently difficult with PointCloudSurfaceBuilder and other FME tools. Would it be possible to add CGAL Polygonal Surface Reconstruction to its construction modes to make it easier?
In-depth courses for all FME skill levels.
Explore our extensive collection of how-to guides and tutorials.
Log an issue with us. Our support team is ready to help.
