Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
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
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.
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.
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.
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!
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
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.
The following improvements to Role Based Security would be useful:1.Increased Granularity for Job Viewing and Job Management PermissionsI need the ability to allow users to see specific other user’s jobs and logs rather than all jobs and logs. We use different service accounts for different enterprise projects and currently I am having to share all jobs/logs with users so they can monitor their processes. Since not all groups need to see each other’s jobs this is not the best solution. (Thank you Safe for new search options in 2019 as they slightly help with this issue.)Likewise, in the current Role system being able to view all jobs requires job management permissions which let users cancel jobs in the queue or terminate running jobs. This puts me in a difficult position regarding how we implement SOX compliance. It is preferred users be locked out from managing running production processes. If the ability to view all logs but not manage jobs was made available that would be a move in a positive direction. If the option to say kill queued jobs but not running jobs was an option that may also be useful.2. Additional Options on Database ConnectionsHaving a Read option alongside the Full Control option for database connections would be excellent. I am seeing issues when I grant users access to connections without giving them full control over a connection. Since we have many processes using the same named database connection it is not ideal to grant users management access since one incorrect change by any user with access could disrupt jobs for all users using the connection. Something similar to how the Notification items are broken out would be amazing.3. Automatic Content Sharing with Administrator AccountsIt would be helpful if FME Server automatically shared user created content with members of the Super User role. If this could be an option for the FME Admin role that would also be appreciated. I have a plethora of users creating content and when they ask for help it is cumbersome to have to share their content with myself and my fellow Admins before I can help troubleshoot.
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.
I would like to have a selectable profile/configurable setting that is saved in the workspace to have the following: Set Feature Caching enabled in Development mode and off in Production mode instead of a general default setting for the Form product.
I am forever accidently closing the Data Inspector after I inspect some data. Please can you add an FME Option to bring up a “Are you sure you want to exit?” dialog box when you click the top right X close button. Thanks.
Hi,I noticed that the GeoTIFF and COG writers in FME do not expose a visible option to define the TIFF predictor (PREDICTOR), equivalent to the GDAL option:-co PREDICTOR=2or-co PREDICTOR=3This option is very useful when using compressions like LZW, DEFLATE, or ZSTD, since it can significantly improve compression efficiency, especially for continuous rasters or floating-point data.For example:PREDICTOR=2 for integer data PREDICTOR=3 for Float32/Float64 dataIt would be very useful to have this option directly available in the writer interface, similar to compression, tiling, or block size settings.I think this would be a valuable improvement to make GeoTIFF and COG optimization easier and more accessible in FME.Thanks.
This enhancement will allow full automation of attachment backup workflows using ESRI ArcGIS feature services or geodatabase attachments being backed up to ArcGIS feature services.Currently, even with the ESRI ArcGIS package, you need to manually configure the feature service feature URL on a FeatureReader so that the features’ featureID can be passed to the ArcGISAttachment connector.Implementation would be sinmilar to the Publish Action item of the ArcGISOnlineConnector which exposes the _webservice_url
StringPairReplacer has been deprecated at FME 2025.2.However, there are use cases where StringPairReplacer would be farther convenient than StringReplacer.For instance, sometimes we have to replace multi-byte alpha-numeric characters with single-byte ones. In StringPairReplacer, it's easy to set replacement pairs, as in:Ａ A Ｂ B Ｃ C Ｄ D Ｅ E Ｆ F Ｇ G Ｈ H Ｉ I Ｊ J Ｋ K Ｌ L Ｍ M Ｎ N Ｏ O Ｐ P Ｑ Q Ｒ R Ｓ S Ｔ T Ｕ U Ｖ V Ｗ W Ｘ X Ｙ Y Ｚ Z ａ a ｂ b ｃ c ｄ d ｅ e ｆ f ｇ g ｈ h ｉ i ｊ j ｋ k ｌ l ｍ m ｎ n ｏ o ｐ p ｑ q ｒ r ｓ s ｔ t ｕ u ｖ v ｗ w ｘ x ｙ y ｚ z ０ 0 １ 1 ２ 2 ３ 3 ４ 4 ５ 5 ６ 6 ７ 7 ８ 8 ９ 9How can you perform the same replacement with StringReplacer? Not impossible but you will have to define 62 replace strings rows. Too tedious!I strongly hope StringPairReplacer will be back! [Addition] Alternatively, it would be great if StringReplacer would have "Replace String Pair" mode, in order to perform the pair replacement with this setting.Text to Replace: ０ １ ２ ３ ４ ５ ６ ７ ８ ９ こんにちは！ さようなら。Replacement Text: 0 1 2 3 4 5 6 7 8 9 Hello! "Good Bye."
Due to the way decimals get stored one dataset may, for example, contain 1.7 and another 1.700000003. I can tell by looking that they’re the same as the data has no more than 4 decimal places. It would be nice if the ChangeDetector had a tolerance for numbers. If I used 0.00001 for the above, as the difference between them is less than that, it would treat the data as unchanged.
Trying to find/clean up duplicate connections. Would be cool to have a list of workspaces that are using/have recently used a database connection on FME Server when you select the connection
As a follow-on from my question and the response from @zoe.forbes after we upgraded to 2026.1 and I found the info icon and blue banner in workspace apps have been removed for message-type user parameters. The icon and banner were useful and I think important aspects of the message parameter and outlining information in workspace apps. I haven’t found any requests to remove them and I think it is well worth restoring them.
I would want to be able to retrieve information about automation schedule.I see several similar requests in Ideas, and it looks like it was possible to do with FME Flow v3 API using schedules endpoint. I’ve tried <FME_URL>/fmeapiv4/schedules?limit=100&offset=0&includeAutomations=trueThe API call didn’t fail, however it returned only schedules and no scheduled automations. The v4 API documentation doesn’t have includeAutomations param, so I am rather surprised the call didn’t fail.The automations endpoint has nothing about triggers or schedules either.In general, it would be helpful to be able to retrieve information about automation trigger and, if the trigger is a schedule, information about the schedule. One of the use cases for this would be administration of an FME Flow hosting multiple projects and used by many users/teams. Somehow, midnight seems to be the most popular choice when scheduling automations. As a result, there is a long list of automations triggered at midnight, and if one of them gets stalled… there is a surprisingly long queue with time sensitive jobs in it in the morning. If I was able to retrieve schedule info, I would create a dashboard to monitor scheduled triggers distribution
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.
