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.
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...?
Currently, FME Workbench allows users to define parameters in custom transformers or published workflows, but the ability to provide detailed guidance for each parameter is limited. I propose adding a new feature to User Parameters that enables authors to attach rich descriptions to each parameter. This would include:Formatted text (Markdown or HTML) Web links to documentation, tutorials, or external tools Images or diagrams to illustrate usageWhen a user runs the workspace, they would see an information icon next to each parameter (show it only if it has content). Clicking this icon would open a dedicated window or pane displaying the enhanced description, helping users understand the context, expected input, and any dependencies or external resources required. BenefitsImproves usability and user experience, especially for complex parameters. Reduces support requests by providing self-service guidance. Enables better documentation and onboarding for new users.
Optional input port for some transformers is a good feature introduced in FME 2025.2 :-)I think it would be better if the input port of these transformers could also be optional.DateTimeStamper ParameterFetcer HTMLExtractor HTMLToXHTMLConverterAre there any others?
using a shift or control (any key combination with left click-drag) to “turn off” autosnap to transformer ports, connection lines, etc while moving one or more transformers into an area where there may be one or more connection lines right where you want to place the new transformer.
I must not be alone in being driven crazy by the lack of the ability to center the run button in a Flow Workspace App. Everything else is center aligned and then the run button is out there on the left and it looks just awful!!
Currently, access to AGOL/Portal photo attachment information is available only thru a true reader when the option is enabled. It would be nice to have that option available when using FeatureReader transformers as well. I'm currently using Build 20264 (FME 2020) maybe this has already been released.Thanks!
Having user-configurable syntax highlighting colors to FME’s syntax highlighting (Python, SQL, Expression Editor), similar to how Visual Studio Code handles token-based color customization would be a nice addition.I find some of the default colors for JSON syntax highlighting to be difficult to read, so it would be great if there were some customizations for this.Text Editorhttps://code.visualstudio.com/api/language-extensions/syntax-highlight-guide
Please add Import from Feature Cache (Similar to AttributeFilter) where you can populate the right side or the left side from values. It would also be great to have some multi row copy/paste (drag drop) to be able to easily adjust the mappings withing the mapping editor.
Newer SDKs (v4/5/6) of the ECW image format supports a fourth alpha band. This seems to begin to occur for rasters from drones. It would be nice to include support for the new v4 (or even v5 and v6) of the ECW SDK in FME, as newer versions of ArcGIS Pro is able to open these files and support are arriving in AutoCAD Civil 3D as well, even though there still seems to be occasional issues with large four-channel ECW files in AutoCAD. The support for newer ECW SDKs in other GIS software, that FME often supports with data in many workflows calls for the inclusion of support for the newer ECW SDK version in FME too.Support for the newer versions would be desireable in both reading and writing.
When discarding an Automation, I’m having to locate the workflows, using Workspaces which were linked to it.Is it, therefore, possible to have an option to delete the “linked workflows” when deleting an Automation?
Currently we are only able to use standard connection to FME Flow within the FMEFlowJobSubmitter transformer. Since we migrated to SAML we cannot use FMEFlowJobSubmitter anymore. We are using very complex workaround to be able to run another workbench on conditions after another one.
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.
I have a need to send Kafka header information as part of a producer workflow. Currently header information is only available to receive as part of a consumer. Note that headers for sent messages are not available.
Hi,Right now it’s impossible to dynamically push a different Headers to the HTTPCaller. You need to already set all the Header names prior to using it.That will be awesome to be able to use, like a Json to push the Headers you want to use, like the Body section.
Currently there is not a connection, transformer or writer that connects FME directly to Azure Key Vault or other key vaults. This would be needed to access sensitive information such as Client IDs and Secrets for Web Connections (to Portal, ACC etc), stored on Key Vault, that we could then incorporate directly into our workbenches. As a company, security is becoming ever more important and this connection would greatly help us to manage sensitive data in line with corporate requirements. We recognise that the existing web connections have decent encryption in place, however there is a general push to have a more standardised approach to storing ids/secrets at a company level.
Hi there,If you click on the log out of FME account menu item, then you see this dialog:There is no way to cancel this. I think it would benefit from a cancel button, in case you change your mind.Thanks,Marc
Hello all,I regularly perform a merge (eg. FeatureMerger) where I am only interested in generating a list on the requestor from the supplier and don't want any attributes merged other than the list.In this case I usually set the Accumulation Mode to "Prefix Supplier" with a prefix of something like "_ignore_me" and then optionally use a BulkAttributeRemover to remove these merged attributes.It would be nice to have an Accumulation Mode option like "Do not Merge" or "Only use List" such that only the list defined under "Generate List" is added the requestor and no other attributes are mergedThis would also be useful in the other transformers that merge/accumulate attributes.
The available system events is rather limited. Everything should be a system event! Here are several that I noticed are missing:Deployment Parameter published/created/updated/deleted Web Connection published/created/updated/deleted Resource published/created/updated/deleted Automation published/created/updated/deleted Schedule published/created/updated/deleted Stream published/created/updated/deleted Flow App published/created/updated/deleted Project created/updated/deleted
If the information product you want to manage is a hosted feature layer view then at present you need to manually adjust its properties outside your ETL workspace, or tackle the job using the ArcGIS REST API via HTTP.Feature service views offer ways to leverage feature services other than simply as they were created.Here is an example of using HTTP calls to automate one property - swapping the source service for the primary layer..In addition to basic create views, add and remove layers, and delete views functionality for views you might want to adjust name, description, tags, visibility, extent, editing access, definition query, field visibility or layer order.The definition-adjusting REST calls (addToDefinition, deleteFromDefinition, updateDefinition are tricky to implement.Who would like this capability?If you have other requirements comment in this idea.
People love formatting excel documents so they're pretty and represent what they want, me doing it again for FME to understand, not so much.It would be great if the excel reader could pick up if a column was hidden and add it to the Schema details, and if there was a Format Attribute that could indicate if a row was hidden.Or actually an option to not read them at all would also be good.
I would like to propose a new feature for the Excel Writer in FME Form: the ability to automatically enable Excel’s built-in “Sort and Filter” functionality on the output file.This enhancement would allow users to generate Excel files where the column headers are immediately interactive, making it easier for end users to sort and filter data without additional formatting steps in Excel.Proposed Implementation:Add a checkbox option in the Excel Writer parameters (e.g., “Enable Excel Sort and Filter”). When enabled, the writer would apply Excel’s AutoFilter to the header row of the output sheet.Benefits:Improves usability of Excel outputs for non-technical stakeholders. Saves time by eliminating the need to manually apply filters in Excel. Enhances the presentation and interactivity of exported data.This small but impactful feature would streamline reporting workflows and improve the end-user experience.
See for example:https://knowledge.safe.com/questions/78116/excel-featurereader-reading-empty-row.htmlIt would be great to have an option in the Excel Reader to ignore any rows that are completely empty i.e. have no values in them. This option could be left un-ticked if you really want to read in rows from a named range or where there is formatting but no data.This would save having to spend time putting in a Tester or AttributeValidator to filter out the empty rows, or hard code ranges into the Reader when you need to be flexible.Merged Ideas:Add option to excel reader to only read 'non empty excel rows' by thijsknapen on February 20, 2021:When reading in excel files, I noticed that sometimes empty rows are read in. It would be nice if there would be an option in the excel reader, to only read 'non empty excel rows' in the excel sheet.This situation of 'empty excel rows' being read in, for instance occurs when an excel sheet contains cells that only contain formatting (but no value). However, also in the simple case where values are deleted in an excel sheet, the rows for that excel sheet will still be read.I often encounter this situation when I use a structured/formatted excel file as an input for a translation. As sheets are re-used, and not always the same number of rows are entered, there are different number of empty excel rows that are read in in the translation.
It would useful to be able to read password protected Excel files (encrypted workbook). The password could perhaps be set as a reader parameter.
I would love to be able to create hyperlinks when writing out to MS Word documents!
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.
