Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
An option in the BulkAttributeRemover to remove Unexposed attributes only would be useful.Some transformer eg.: JSONFlattener or JSONFragmenter create all new (potentially unknown) attributes, even though usually the exposed ones are used only - which may be excessive. Now the exposed attributes must be (bulk) renamed before bulk removing the unexposed, but prefixed attributes.An alternative way would be adding a “create Exposed attributes only” option in these transformers, so they wouldn’t even create unnecessary attributes..
To Clear the entire feature cache a user has to go to the first transformer, right click it and select clear data cache. Or start and stop the translation quickly.I’d like the option to clear the entire cache when I right click anywhere in the canvas and additionally a clear cache button in the toolbar would be nice.This would help speed up the development process and improve user workflow for a feature that already exists but could be improved.
I’d like to suggest FME exposes the Database Spatial Tolerance in the Feature Information window, alongside the projection, dimension, min/max extents etc.This information is critical when understanding spatial filtering, and can account for features being inside or outside specific areas of interest when using a spatial filter within a Reader/FeatureReader, and gives context to the features being retrieved.In Oracle, this would mean reading the sdo_metadata table in the database, but other database types would require differing tables to be read. It would also be useful for FME to perform a simple calculation using the projection and the tolerance together, and write a warning message in the translation log if the tolerance (on the ground) is of a large distance - especially useful when spatially filtering data.Thanks,
The Readers now give out more warnings than before, it’s becoming an issue for some when monitoring from FME Flow or when someone who isn’t a daily FME user needs to run a workflow.A way to tone down those types of warning would be a great addition, because sometime the warnings are actually meaningfull and we don’t want to have look at all the jobs or remember that X numbers of warning for this specific workspace are meaningless. Two examples are these: Spatial and Non Spatial Reader/Writer got merged together, if you don’t have a spatial component it warns you about it each time, but it’s useless.Oracle Reader: Username and Password in lower case cause a warning that can be interpretted as an error (copied the error from an older post)
In the Autodesk AutoCAD DWG/DXF-writer (and in the other DWG writers too) it would be good if you could choose an attribute for Layer Description, Default Linetype, Default Color and the states: On, Frozen, Hidden, Locked, Plottable. It's not so usable right now when you need to hard code these values which makes all layers look the same.
I’m interested in using FME Flow for Connection Storage in FME Workbench.We have a single FME Flow instance that does not have redundancy. I’m concerned that if Flow is unavailable, that FME Workbench will effectively also be rendered unusable if I use Flow for connection storage, based on what I’ve read in the documentation.Further, FME Form provides me a sort of redundancy at the moment - if Flow is unavailable or if the engines are consumed, I can run my processes locally, as a last resort. In my understanding, moving my connections to Flow would remove this redundancy and leave me more vulnerable to network/infrastructure/system issues.If the above is true, would it be possible to maintain a local cache of connections, similar to the default Personal Database Connection Storage, where it prompts for and perhaps even requires connection and syncing to Flow, but has some sort of fail-back mechanism in the event of failure?I could keep an export of connections locally, or a Shared Database copy, but this will go stale and defeats the purpose of the FME Flow option, I imagine.Thanks for any thoughts or corrections on the above.
As I have many jobs running and a lot doing well, I frequently is called on Failed jobs that are deep in the line and I happen to have a message of the server telling me“Error: The log file for job ID ‘290047’ does not exist”I don’t want to give more space to my logs in general but would appreciate to have the logs of jobs which raised errors (and maybe warnings) longer. FME Flow can destroy logs for OK jobs and keep the error ones longer.
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
In >2026 to connect to AGOL or Portal enterprise from FME, we utilise the “unified” Esri ArcGIS Enterprise OAuth (Template)(safe.esri-agol) web service ARCGISFEATURESERVICESWorking with Esri ArcGIS Feature Services in FME – FME Support CenterThe article perhaps fails to mention how to handle the web service Loopback Interface Redirect or Proxy Redirect Strategy, as the Embedded Browser is deprecated in FME Form 2025.2The arcgis registered application needs to have http://localhost as redirect URIWhat about FME Flow redirect URI?My suggestion is in Connections & Parameters - FME Flow for any given safe.esri.agol newest Esri web service in Flow >26It needs a default Redirect URI of “ self “?
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...?
I've noticed that the Safe Software YouTube channel has recently started publishing more short tips, tricks, and workflow videos, which is great to see. I really appreciate the effort to create more educational content for the FME community.I do have a few suggestions that I think could make these videos even more engaging and effective.1. Audio qualityThe biggest issue, in my opinion, is the sound quality. It often sounds like it was recorded with a fairly basic microphone and includes noticeable background noise. Since audio quality has a huge impact on viewer retention, investing in a better microphone, cleaner recording setup, or basic audio post-processing would make a significant difference.2. Editing and pacingMany videos feel longer than necessary. Tips that could often be explained in 30–60 seconds are sometimes stretched to 3–5 minutes. Today's audiences are used to concise, information-dense content, so tighter editing and faster pacing would likely make the videos more useful and easier to watch.3. Overall production qualityThe videos would also benefit from a more polished production style. A simple screen recording is useful, but adding zoom-ins, highlights, annotations, quick cuts, clearer structure, or occasional graphics would help viewers focus on the key points.If video production is not a primary focus for the internal team, it might be worth collaborating with someone who specializes in educational video production, YouTube content, or short-form technical content. Even a small improvement in production quality could make the videos feel more professional and help present FME in the best possible light.The technical content itself is valuable. I simply think that better audio, tighter editing, faster pacing, and a more polished presentation would help these videos reach a wider audience and make them more enjoyable to watch.Thanks again for creating more content for the FME community. I hope you'll continue publishing more videos.
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.
When writing PDF it would be good if I could choose to write PDF/A version of the files. PDF/A is an ISO standard specialized for the digital preservation of electronic documents and in several cases it's a requirement when delivering PDF-files to a customer.
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
The 'NoFeaturesTester' custom transformer currently out on FME Hub is powerful. However, we're getting pushback from IT from using it in our production workspaces in FME Server. We've benchmarked their work-arounds, and it slows down the workspace significantly (2 seconds with NFT vs. 2.5 minutes with their suggested alternatives). My idea: Harden this transformer and turn into a standard transformer.
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.
The web connection/webservice features have been around for a few years and it needs some improvement in the UX, especially to help new users. Here’s a few suggestions:1. once a web service is created by a user, services, templates and connections are all mixed up in the drop downs or that long list of templates and web services. Some type of separation or categories between user created services from web services templates either on the long list in FME options or the drop downs in the connectors.2. The Add Web Connection drop down from the transformers is confusing to new users, when the web connection is not a simple token or key or the web service is not created yet. 3. On the MCP Caller (Beta) web connection from FME Options, I have to type the MCP URL and API key three times before I can use it. Once the URL is configured from the template ans applied. Once applied, the URL should persist in the drop down when I Test the web service and create with Add my Web Connection.
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.
add webservice definitions to FME Flow roles, so we can control who can access them, it seems if you use FME Flow as connection storage for FME Form, connections are controlled by roles, but anyone can see and use any webservice definition. If I am wrong about this, then this idea can be dropped.
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.
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.
