Shape the future of FME with your ideas
New and Open ideas are awaiting review or have been reviewed by our Product Management team, and are open for commenting and voting.
Probably most relevant for workspaces started through an app or webhook: Restrict the number of runs. I.e. if it's been triggered more than x times in y amount of time, or if there are more than x non-unique triggers, don't run the workspace.The main reason: one of the Flow's we're managing was recently hit by a DDOS attack, within the space of a few hours one particular workspace app was triggered about 4500 times. The workspace failed right away every time due to bad input, but it still took 1-2 seconds to do so, so that did eat up a big chunk of the capacity during those hours.Another reason would be to prevent a user from re-submitting a job if it's taking too long. They might think something is wrong so they try again, and again, and again.
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.
Currently a User Parameter of type Choice can be configured as a drop-down, and the user is permitted to edit the choice, or it can be defined as a list or tree and allow multiple selection. But it cannot be both multi-select and allow choice edit.I would like the ability for the user to add values to the tree view in multi-select mode.
I’m trying to write features to an esri feature service, but getting “fatal errors” from the feature service that is causing the entire FME workspace to fail. I should be allowed to decide what to do if a “fatal error”, much in the same way that I can choose how to handle rejected features (Terminate Translation or Continue Translation).FME should just “fail” that single request and continue writing features out. Examples of where this would be useful:
I submitted this question 5 yrs ago. Still not a solid solution for this issue. To date i have had to create 3 different systems (matching records) between, autodesk, esri, fme and trimble. And for some unexplained reason fme started obfuscating their naming system when you use CSExtractor to Coordinate System `_UTM83-13_0' parameters: CS_NAME=`_UTM83-13_0' CS_ORIGINAL_NAME=`UTM83-13' But the Idea is. Add a method of smartly matching the trimble projection found in the jxl to the fme espg, or esri or even autodesk projection. Find a way to standardize this. I know if i try to project something to the incorrect project it tells me outside of coordinates. It seems there are many ways to get these matched especially when there is an existing system name.https://docs.safe.com/fme/html/FME-Form-Documentation/FME-ReadersWriters/jobxml/jobxml.htm this indicates that coordinate systems are now supported in jxl. is that the case?
We are interested in the integration of the data format INTREST (=intermodal referencing system for traffic related data). Background is: traffic routing with FME. Thank you in advance
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.
In recent security audit, one of the concerns was with the FME Server log-in.As there is no limit on the amount of retries, the login can be brute-forced.Please add a toggle and a parameter for limited login-retries, just like 'Password Policy' in the system configuration.Perhaps also adjust the system-event to only trigger after a set number of attempts, and have the IP-address of the source as one of the keys.Kind regards,Martin
To connect to a PostgreSQL database, many tools allow to use a pgpass file (https://www.postgresql.org/docs/current/libpq-pgpass.html) or a pg_service file (https://www.postgresql.org/docs/current/libpq-pgservice.html).It could be great to use such files in FME with the postgresql reader/writer and the SQL executor.Three options :Use the selected connexion (current behaviour) Use the pgpass file, fme display a form to set infromations on the connexion and use the selected pgpass line corresponding to the data specified in FME (nothing = 1st line, host or host+port or host+port+user or host+port+user+db = 1st corresponding line) to get the required data to connect For pg_service file, fme display a “service name” input and use the configuration specified by the service name.
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..
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)
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.
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
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.
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
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.
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!
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).
While trying out a workflow in the support site I encountered an attribute that was markdown text.There is no syntax highlighting option for markdown text in the data preview pane when inspecting the cache, so let’s add one! The behaviour should be like the other syntax highlighting options, when you select the syntax option the data renders accordingly.Here is my example:Markdown text in an attribute
I would like to be able to attach a role to an API token rather than having to rebuild all the permissions directly on the token.
It would great and highly beneficial to see the exact processing time for each individual transformer directly on the transformer. This feature would allow users to easily identify bottlenecks and optimize workspace efficiency without manual benchmarking in the log.
When adding an Esri ArcGIS Feature Service reader the where clause text editor does not support access to the feature schema, but the schema is known so lets make it accessible.Compare this to (for example) geodatabase reading, a where clause may be constructed from the table schema.
Did you know that log message filter settings are stored at the workspace level, not as part of the engine configuration?Here's what the relevant section of an FMW file looks like:Without debug:LOG_FILENAME "$(FME_MF_DIR)none2none.log"LOG_APPEND NOLOG_FILTER_MASK -1With debug enabled:LOG_FILENAME "$(FME_MF_DIR)none2none2.log"LOG_APPEND NOFME_DEBUG MAPPING_FILE BADNEWS UNGROUPED UNCORRELATED DUMP_SCHEMA XSD_VERBOSE HTTP_DEBUG FTP_DEBUG FME_DEBUG STASHLOG_FILTER_MASK -1This setup makes sense, especially when publishing workspaces to FME Flow and needing consistent logging behavior.However, in FME Workbench, this configuration is set under FME Options, which seems a bit out of place. It's not an engine or Workbench setting; it's specific to the workspace you're editing.In FME 2024.1, there was a review of this area. Could we take it a step further and move this setting to Workspace Parameters? That way, it's clear and directly tied to the workspace itself.
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.
