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.
If you have ArcGIS Pro installed on your machine then you have access to the arcpy.geocoding module with its Locator class, which can be serverless. This puts geocoding in the hands of anyone with (say) a file-based locator.
The Tester and TestFilter transformers have five distinct Comparison Modes:Automatic Numeric Case Sensitive Case Insensitive Date/TimeAs well as the option to Specify Per Test.The FeatureJoiner and FeatureMerger transformers have three Comparison Modes:Automatic String (presumably the same as Case Sensitive, above, but I have not validated that and don’t see it specified in the documentation) NumericAnd the way that these transformers are designed, they are inherently “Per Test” or per “Join On” condition, as it were.The general Idea here is to make the Comparison Modes more consistent across transformers - there are likely other transformers that could be included in this, beyond the four mentioned above.Case Sensitive, Case Insensitive, and Date/Time could be useful in the Feature-type transformers, in addition to the Test-type transformers. There are other ways to achieve these, of course, but there may be value in having them readily available. The order in which Comparison Modes are listed could be consistent - this is a minor point.If the various types of Comparison Modes are already tailored to best match each class of transformer, then the idea may not have merit, but posing it in case others could see any value in the proposed change or a similar change.
In our standard FME Flow training course we have one excercise where Workspace A does some checks on user parameters and if they are succesful it runs Workspace B through an FMEFlowJobSubmitter.One of our trainees accidentally set up the FMEFlowJobSubmitter to run Workspace A instead and when he published it to Flow he made a recursive loop: every time Workspace A ran, it queued Workspace A again. I was busy helping somebody else at that time so when I got around to his question I noticed it had ran 17000+ jobs in a matter of minutes. These were low-impact jobs, so it wasn’t an immediate problem, but it’s safe to say that this has the potential of completely overwhelming an FME Flow setup.After talking to Safe we decided to post it as an idea here to see if others have come across this as well or have opinions about it.The big question would be:Should FME be able to detect these recursion risks?And in a broader sense: have you had this happen to you? Or something similar that you think FME should be able to detect and warn you about?
When I have a job that runs for 5-15 minutes (and this is with a subset of data) it would be nice to be able to sneak a look at the cached features at any point during the running workbench. I could click on the green loading box and see what features have loaded so far. This way I can be QC-ing output before the workbench has even completed running.
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.
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.
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!
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.
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.
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.
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.
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.
With libraries like DuckDB in your Python environment, as is the case where you either have ArcGIS Pro or Enterprise on your FME machine, or you’re using ArcGIS Data Interoperability, then it is easy to retrieve potentially millions of features from an S3-API compliant object store or other web source in seconds, but it’s a bottleneck to send them on into the workspace one by one.I would like to see performance like reading CSV files brought to PythonCreator.There is a possibly related existing idea Introduce a Python Dataframe Creator/Transformer but I don’t want to confound using dataframes with this idea, which is fundamentally about performance.Dataframes might be how this idea is implemented, but my guess is that would be a heavy lift for Safe, another way might be a way to output an aggregate feature.
When we create a Web or FME Server connection in a workbench it automatically gets prefixed with myname. And then when published to Flow we get the same…. is it possible to create these connections with a more generic name, I’m not connecting as “robert.mcpherson” and it doesn’t seem to matter but this is an enterprise system and I will be for ever named in the system. I guess it doesn’t matter but it doesn’t seem a very “enterprise” thing
It would be really useful to have the option to install FME Flow with no pre-installed workspaces, no inactive automations/schedules, no topics/publishers/subscribers, and no AR App. Just the bare minimum: the Admin user and the default roles (fmesuperuser/fmeadmin/fmeauthor/fmeuser).All the other utilities and example content could instead be made available through FME Hub for download as Flow projects when needed.On a related note, I also question the usefulness of the default “Temp” resource connection, since it isn’t required by the system and isn’t automatically cleaned up. For new users especially, its presence can be confusing.
To my surprise, there is no option to add headers to an HTTP request in Automations. We need this option. In the meantime, I'll go back to Workbench :(
All the grids in FME servers are not sortable by users, sorting is the very basic function expected by all users from any software these days.Please allow users to click on any column header to sort ascending/descending/removing sort for a given column. The user should be able to hold the shift or control key to choose multiple columns to sort. The sort function should work for all supported data types in the column, e.g. Number, text, date, user, etc.
In an Automation email action, we would like to use deployment parameters to set the following parameters:SMTP Server SMTP Server Port SMTP Account SMTP Password Connection security (less important)Motivation: we have clients with an important number of automations that use the “Email (send)” external action. When the smtp server settings change, e.g. between DEV and PROD environments, it’s a significant amount of manual and error-prone work to change these settings consistently in all the automations. It would be a big help if these settings could be set using deployment parameters:
On FME Server flag out Workbenches that are Part of an(one or more) AutomationWould be more comfortable in case of editing the Workbench or in organizing between Repositorys.
Sometimes you only realize after a while that you need some followup action after a writer. This results in deleting the writer and inserting all the necessary information into a new FeatureWriter.I think it would be helpful if you could convert a normal Reader or Writer to a FeatureReader/ FeatureWriter.
Currently the JSONValidator only validates syntax, whereas the XMLValidator allows for Syntax only or Syntax and Schema.The Schema can defined as per http://json-schema.org/documentation.html
Idea: cancelling a job will rollback the whole transaction of all features for Snowflake WriterObserved behavior: cancelling a job in FME Flow will stop additional features from being written, but features that have already been written to Snowflake are already committed without any rollback of the transaction. There is inconsistency between “Features Written’ as recorded in the job log and actual features written according to Snowflake logs. The job log records zero features written while there have been many features written to Snowflake despite job being cancelled.Desired behavior: cancelling a job in FME Flow will stop additional features from being written and rollback any partial changes the job has just done. Outcome: improved management of jobs.
It is really handy to set multiple presets in 2019 and this makes life a lot easier but i'm missing the ability to share these settings/presets with my colleagues. I would really love to see an export/import button or even a linked button so when changing some of the settings in the given preset it also changes everywhere else.
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.
