Shape the future of FME with your ideas
Open ideas have been reviewed by our Customer Success team and are open for commenting and voting.
FME Workbench does not always prompt the user when an embedded transformer was updated in its fmx file. It would be useful to have an option to update embedded transformers manually. Maybe in a similar fashion as default transformers can be upgraded. How about right-click -> update to latest version -> bring up a dialogue to select the fmx file? I am aware that this is not required for linked transformers but in some cases it is more practical to use embedded transformers. Also see here.
I would like the option to view the entire job log on flow instead of have to click through pages using the navigation buttons on the job summary page
Currently you have to go directly to a remote engine job logs and log in to see job logs, It would be great to be able to see all logs from one place i.e the parent flow instanceIf a job runs on a remote engine, I would still like to see the logs in the parent flow instance
I would like to write out a DGN Microstation file and be able to set the display setting, so that when I open my data it will be displayed as zoomed to fit.Ideally, I would like to do this dynamically as I use a fanout of different areas to multiple Microstation DGN files. This would allow the DGN files to open with the view focused on the data in the area.
Currently you can filter Logs by severity level: Information/Warning/Error. I would love to have an additional filter that is user defined. For instance, I often use Loggers to write messages to the log that are used for debugging purposes, like “Token successfully fetched” or “45 Features written to DB”. Technically these messages should be categorized as “Information” but Information type log entries are hard to filter as most messages have this log type. On the other hand I don’t want to to use the Warning or Error type, as these messages should not be mixed with real errors. That’s why I propose a new Log Message type that could be called “User” or “Custom”. Like the other Log Types User Logs should be color coded and filterable on both Form and Flow.
See: In earlier versions of FME (for example 2023.2), the Bookmark Navigator was available as a toolbar option under Tools → FME Options → Toolbars. This feature seems to have been removed in 2024.2. I am not sure if it has returned in 2025, and the FME documentation does not clearly state which toolbar options are currently available or what they do.While bookmarks are still accessible through the Navigator panel, that is not an effective substitute for those who rely on the Bookmark Navigator toolbar. The Navigator is typically used for managing transformers, parameters, database connections, and other elements. In larger workspaces, bookmarks get pushed out of view and require vertical scrolling, which is not only annoying but also time-consuming. It is not a UI element with a fixed or easily reachable position.The Bookmark Navigator in the toolbar provided immediate, horizontal access and required very little screen space. If users choose to enable it, the impact on toolbar real estate is minimal. It was especially useful for jumping between major workspace sections and worked well in presentations or collaborative reviews.As a consultant working with various organisations, I found this feature to be a good motivator for adopting clear and consistent bookmark titles.Please consider restoring this option, or making it available as a configurable UI element in future versions.
In my experience, web service credentials and the base url for a web service go hand in hand. For example, if I have credentials for a sandbox instance of a service, that would go along with a sandbox base url (ex. https://sandbox.servicename/api/v2 or https://servicename/sandbox/api/v2 )But I have found that the pre-built web services do not prompt for a base url.I realize that I can add a prompt by creating my own Web Service, but how would I access my Base Url parameter within the Request URL in the HTTPCaller?My idea is:Prompt for endpoint base url by default in all Web Services (to be entered while creating a new Web Connection). In the HttpCaller transform, rename the “Use Authentication” checkbox to “Use Authentication / Web Connection” In HttpCaller, move Request Url below the checkbox If there is a non-empty endpoint base url defined in the selected Web Connection, Add a “« base url” marker into the Request Url textbox The user can then complete the endpoint (i.e. /employees )The benefit of this feature is that I can have multiple workspaces all using the same Web Connection, and if either the URL or the credentials change, I can modify this once in FME Flow without having to alter any workspaces in FME Form.
Hi there,I would like to be able to right click on my web connections in the navigator and reauthenticate, rather than having to go into the FME Option menu.E.g.
I would like the version of a custom transformer to be available as a parameter in FME so that it could be logged out for debugging purposes.This is helpful in the case there are many versions of a custom transformer.
From this question: Toolbar connections are stored separately to Web Connections. When you change to using FME Flow as your Web Connection storage you can’t separately manage your toolbar connections.I wonder if an approach could be that the toolbar connections are their own separate ‘connection type’ that shows regardless of you connection storage settings? Additionally this could then give you the option to copy to/from the toolbar and connection storage
It would be very nice to extract the DWG properties (the equivalent of the DWGPROPS command in AutoCAD) into FME. These are drawing properties and not feature properties.
ProblemFME is case-sensitive with attribute names. When users upload files (CSV, Excel, etc.) with inconsistent casing (Name, name, NAME), it causes: Schema mapping failures (e.g., in SchemaMapper or Joiner). Unexpected behavior when casing isn’t controlled. Extra complexity requiring custom Python for basic cleanup. Why It Matters Real-world data often has inconsistent field name casing. Makes reusable workflows brittle and error-prone. Slows down schema inspection and integration with metadata or APIs. Suggested Solution Add a reader or transformer option to treat attributes case-insensitively. Let users define a canonical case format (e.g., lowercase or PascalCase). Add case-insensitive matching toggles in SchemaMapper and AttributeRenamer. Impact Simplifies file ingestion, mapping, and validation. Reduces Python scripting for common cleanup tasks. Makes FME workflows more robust and user-friendly.
FME24 provides an overly simplified and bland user interface and experience. Even as a long time FME user I find it difficult to use and even train new users. Personally, I’m yet to find a single benefit of the change.E.g. Simple icon colours which categorise items in the navigator (Purple = Parameters) are gone.Similar to being able to select dark mode, I think it would be extremely helpful to enable users to select the theme and icon styles that improve their user experience.
***Note from Migration:*** Original Title was: When renaming an attribute, have the name-change propagate through the subsequent transformers automatically Often I find myself in need of renaming an attribute after I've built out complex transformations. If doing so towards the beginning of the workflow, there's the ripple-effect caused by breaking the subsequent transformers containing the renamed attribute, and it can be tedious to make the corrections in the downstream transformers. It would be super useful to have an option for auto-applying the rename downstream from the rename action.
It would be nice to be able to use ArcGIS web connection to authenticate processes when using the ArcPy library
A way to update downstream attributes following attribute renaming would be a really nice feature. It is already done for parameters so why not put in the work to extent it to attributes as well.For example a user has workspace which includes several attributes which are coming from a JSONFlattner - after creating several transformers downstream using the newly created attributes the user decides that he wants to add a prefix to the attributes. When adding this prefix the rest of the workspace breaks because none of the references have been updated to reflect the changes. Probably the more common situation is when an input data set gets an updated schema - e.g., Maybe “Layer” becomes “layerName”. If I update my reader then the rest of my workspace will break. At this point the author has two choices, either, rename all the attributes in the process to match the new names (probably good practice) or just add one AttibuteRenamer at the start of the process to rename the new names back to the old names so the workspace runs again. There are quite a few situations where I think having this kind of functionality would do a lot to improve workspaces readability with little effort on the authors part. For example often when building a workspace it’s pretty common to just reuse the out-out-the box default attribute names (e.g., _area). Then once you’ve finished the bulk of the work maybe you see that it’s unclear what “_area” actually is so you want to rename it so something like foorprint_area - only to find our you’ve used it in several places. Perhaps you decide you can’t be bothered to rename it.This kind of functionally can be used to help promote better readability and better practice with attribute naming. It would also make it a lot easier for AI to understand sections of workspaces as well - (footprint_area x building_height) is a lot easier for an AI to understand what is happening with some context. The way I see it happening would be either completely automatic (similar to User Parameters) or a prompt with a list of affected transformers and which ones to update.
Make it easier and faster to convert raster images to vector polygons.Improve performance of RasterToPolygonCoercer and add more options for customizing the transformation.FMEers, we are interested in knowing how important raster-to-vector conversion is to you. Please upvote if this is an operation you require, and comment to let us know what specifically you'd like to see. Any details you can provide on your use cases would be helpful.
SQL database in Microsoft Fabric is now in preview, we would like to be able to read/write to it with FME. Only Microsoft Entra Auth is supported - https://learn.microsoft.com/en-us/fabric/database/sql/connectPlease can the sql server readers/writers be updated to support this type of authentication.
Has FME ever thought about going into the business of creating web or desktop applications? This might be out of the FME comfort zone, but I thought I’d ask the question. Thanks!
***Note from Migration:*** Original Title was: Add the Ability to Generate Documentation (PDF, Word, Sharepoint, Web) from Workspaces I don't know if you are familiar with BizAGI (http://www.bizagi.com/). It's a tool to document "processes". After you described the tasks etc in the process you can generate documentation (PDF, Word, Sharepoint, Web, etc).I think it would be cool if it was possible to document FME Workspaces in a similar way. If it would be possible to write descriptions in the "transformers", bookmarks could be used to generate structure, different "chapters" in the documentation (in a PDF).Now I am sometimes using BizAgi to document FME Workspaces. Because FME Workspaces are very "process oriented" it would be nice to be able to generate documentation automatically. It would also force you be able to write even more "clean" workspaces :).
It's not always possible to print to a PDF, so it would be nice if you could export the entire workspace canvas as a graphic file for documentation purposes.
Hi.Would it be possible to add a simple yes/no (default: no) option to the "Workspace Parameters/Logging" that enables "versioned" log files ?It might be implemented simply by having FME append a timestamp (e.g. start of run) to the log file name (whatever that may be), so no previous log file is ever overwritten.The purpose is to enable checking log files from multiple runs against each other. Some times a translation is run multiple times before a comparison is warranted.The option to "append to log" file doesn't really work for this, and is a lot more complex to handle and administrate.Cheers
I would like to see the option added to log a 'SUCCESS' message. Next to the INFORM, WARN and ERROR messages, it would be helpful to filter LOG messages to see what is executed succesfully. There is a big difference between inform messages and SUCCESS messages. This would also allow for another use of the Logger transformer.
Make FME a supported true curve client, thus enabling better support for ESRI Utility Network.ESRI ArcGIS Portal Feature Services have a configuration setting to allow true curve updates by true curve clients only - this needs to be on/live to support features and analysis in Utility Network.FME Feature Service writer is not a supported client, so updates to curves fail/are not permitted - limiting FMEs capability to support UN.
FME Server has a good range of Rest api calls but they aren't all documented. For instance, named connections are avaliable by fmerest/v3/namedconnections/webservices, version control push by /fmerest/v3/versioncontrol/remote/push. It would be great if more of these calls could be documented
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.
