Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Hi!It will be great to use AttributeValueMapper on a list to avoid to have to explode it.Thanks!
When downloading data using Data Download service (e.g. from an FME Workspace App), a Zip file is created containing the output files. The zip file is automatically named something that looks like “FME_4B425D3A_1772473610895_13172.zip”. It would be nice if an option was implemented to allow customizing that name to something that is more user friendly. For example allow authors to specify what exact name the Zip file should have, or allow the use of parameters to create a string to use as file name. Even if the final filename has to have some extra characters at the end like 4B425D3A_1772473610895_13172, giving authors some customization capability would be beneficial.
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."
It would be helpful if FME Server 2017 had an SFTP Watcher. Currently the regular FTP Watcher does not support SFTP. I am aware that the Notification Service supports SFTP subscriptions but currently in 2017.0.1.1 there is no corresponding SFTP publication option.
I would like to propose an enhancement to FME Flow regarding administrative security.Although administrators are already authenticated when logged into the system, certain critical actions pose a significantly higher risk and impact. These include, for example: Creating or restoring backups Connecting or modifying Authentication Services Adding or deleting users Changing security-related configurations Other high-impact administrative operations To increase security and reduce the risk of unintended or malicious changes (e.g., in case of session hijacking, unattended sessions, or compromised credentials), I propose that FME Flow require administrators to re-enter their password before executing such critical actions.This additional verification step would: Strengthen security for sensitive operations Reduce the risk of accidental misconfiguration Align with best practices for secure administrative interfaces Provide an extra layer of protection without significantly impacting usability The re-authentication prompt should only appear for clearly defined high-risk actions to maintain a smooth user experience for routine administrative tasks.
DB connections in Flow, and corresponding Deployment parameters can become difficult to navigate and manage if you have more than a small handful of connections to keep track of.It would be really helpful if these could be stored in groupings, or subfolders, to make the list more manageable. For Deployment Parameters especially, this grouping would be very handy when listing in the Form navigator!
Hi there, I like to create hidden connections for larger workspaces to keep things tidy. However, so many times when I select and grab a group of transformers I end up accidentally selecting the hidden connection and removing it. It doesn’t help also that the hidden connection colour is too light when you select a transformer that uses it.
I often find in some scenarios it would be helpful to have annotations point to multiple transformers.In the scenario below, the annotation applies to both the AttributeExposer and the AttributeRemover, but I can only connect it to one An alternative way is adding it to a bookmark and annotating like below. I think a bookmark is overkill in this situation and having the annotation attached to both would be helpful
Hi there, I like the idea of being able to look at a workspace and seeing easily what transfomers change attributes, which change geometry, which filter etc. To do this, it would be nice to change the colours of transformers, so I could have say green transfromers are filter transfromers etc. I could add annotations to the top of these but it becomes a bit cumbersome. If you can rename transfomers, changing their colours should not cause any unintended issues.
It seems a lot of users are taking to using FeatureReader and FearureWriters in place of traditional readers and writers.I wonder if it’s time to give these two transformers a new color to help them stand out?
I would like to request the reactivation of the Workspace Viewer as it has been marked as obsolete and is no longer available on the platform.This tool was essential for my work, as it facilitated my understanding of the data transformation process and was very useful for debugging and optimizing my workflows.I would like to know if there is any possibility of recovering it or if there is an alternative that I could use.Thank you in advance for your attention
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!
For my current use case - a workspace app - I do not want users to see either option highlighted in the attached image and only wish to allow them to drag/drop or upload from their own machine. I attempted to try multiple file paths and uncheck the ‘Allow URL Path’ option within Form’s user parameter manager, which had no effect on the URL/path option showing, and see no option to disable browsing resources which has been asked about in the past:For simple file uploads by users not needing to provide a URL or browse Flow resources, I think disabling both should be possible.
Add option to hide "Browse Resources" button on FME Server App. It confuses some users and there aren't usually any files users need to access in the resources. We prefer to design the input parameters on our apps as simple as possible to avoid overwhelming users with too many input fields and options. Minimizing the upload functionality to only one one button will certainly make the input apps more compact and easy for users to use.
A minor bug I’ve possibly just discovered, though something in my memory is thinking I’ve heard about it before. If the FeatureMerger transformer is not connected to any data connections and you move the requestor port down below supplier then drag it to a connection, the connection goes to the uppermost port - in this case the ‘Supplier’ port. I would say the default most people would want is that it looks for the ‘Requestor’ port, regardless of whether it is the uppermost port or not. So this is a bit of a bug report and idea at the same time. Screen recording gif is attached to show current behaviour in FME(R) 2025.1.1.0 (20250730 - Build 25615 - WIN64)
This idea has come up in the 2016 thread (now released) about adding any output ports to FeatureWriter but the use case for Rejected features remains - e.g. some web-based format has a transient HTTP error, the failed features need to be retried after a wee delay, or a field overflows and can’t be written. @markatsafe @rylanatsafe you guys were on that thread. FeatureReader has a Rejected port, very handy for retry logic in a looping custom transformer, lets see it for FeatureWriter!There might need to be a Rejected port for each output port if you're going to loop it, or filter on feature type before looping to an input.
In Workbench's Visual Preview window it would be handy to be able to search/filter the table values by null, missing, empty. These null values are available in the Filter for the Graphics View, but not in the Table View search box. If available, this would allow a quick count of features that have missing values in a particular attribute field/column.This functionality would have come in handy during the Desktop Basic training for Best Practice - Exercise 1 during step 4 when you confirm that the CrimeValue attribute is missing values on some of the features. If you could filter the CrimeValue column using a '<missing>' value, then it would easily confirm the number of features missing a value (instead of sorting the column and scrolling down the table see which row numeric values start appearing).The same would apply to Data Inspector.
A function to enable|disable the Startup|Shutdown Python Script at once would be desirable.It is always very expensive if you have to comment out all lines just jor testing
In my use case I’ve got plenty of overlapping old aerial images, which I am stitching together.Many are too bright or too dark, so always using maximum or minimum data value for overlapping cells is not the best option. Averaging or summing doesnt make sense either, so my only option is something like this Calculate the median of overlapping pixel values from 24 input raster bands | Community + sorter + using ‘last’.So my suggestion is to simply add ‘Median’ as option:
With the advent of Data Virtualization it seems like a good time to improve JSON support in FME!It would be great if there was a simple way to convert a feature to JSON format so that all attributes on the feature become elements in the JSON object and all lists items are converted to arrays in the JSON object.The result should be output to an attribute.I know that it’s possible to do this currently using the JSONTemplater but it requires manually building the template and it would be nice to avoid that. Just do whatever cleanup of attributes is required using the AttributeManager, then have FME convert to JSON without requiring extra input. The JSONTemplater can still be used for more complex cases.(I know that it’s also possible to use the JSON writer to create a simple file from a feature but this does not support lists/arrays and requires writing out to the filesystem.)
Currently, FME Flow supports database connections via JDBC, but authentication typically relies on static credentials such as username and password. In modern cloud environments like Azure, using Managed Identity is a best practice for secure, secretless authentication.This idea proposes adding support for Azure Managed Identity including System Assigned and User Assigned identities for JDBC connections to databases such as Azure SQL Database, Azure Synapse, and other services that support token-based authentication.Why is this important?Eliminate hardcoded credentials: Reduces security risks and simplifies credential management. Cloud-native security: Aligns with Azure best practices and enterprise compliance requirements. Automatic token refresh: Improves reliability and reduces operational overhead. Flexibility: Support for both System Assigned and User Assigned identities allows organizations to choose the right approach for their architecture.How it could work:FME Flow detects it is running in Azure and uses the assigned Managed Identity. When establishing a JDBC connection, FME Flow retrieves an OAuth 2.0 access token from the Azure Instance Metadata Service (IMDS). The token is injected into the JDBC connection string or passed as a driver property (depending on the database/JDBC driver). Configuration options in FME Flow to select: Authentication mode: Managed Identity Identity type: System Assigned or specify a User Assigned identity (via client ID) Use Case Example: An organization runs FME Flow on an Azure VM with a User Assigned Managed Identity that has access to multiple Azure SQL Databases. Instead of storing credentials in FME Flow, the system automatically retrieves tokens for secure, passwordless connections. Security NecessityStoring static credentials in FME Flow or any application introduces significant risks:Credentials can be leaked through logs, backups, or misconfigurations. Manual rotation of passwords is error-prone and often neglected. Compliance frameworks (ISO, SOC, GDPR) increasingly require secretless authentication methods.By leveraging Azure Managed Identity, FME Flow can achieve zero-secret architecture, reducing attack surfaces and aligning with modern security standards.
You can download subfolders of /Logs but not the entire /Logs folder.
We would like to request support for Azure DevOps as a remote Git provider in the Version Control functionality of FME Flow. One of our clients recently upgraded from FME Flow 2024.2.1 to FME Flow 2025.1.2. In the previous version, they were successfully using Azure DevOps Git repositories to manage workspace versioning. After the upgrade, they are no longer able to push changes to their remote repository. The UI reports: “There was a problem communicating with the REST API.”And the backend logs show HTTP 500 errors when attempting to push.According to the documentation, only GitHub.com is officially supported. Azure DevOps is not listed, although it previously worked without issue. This limitation significantly impacts their ability to maintain version history and collaborate effectively. Could you please consider:Adding official support for Azure DevOps Git repositories in FME Flow Version Control. Providing documentation or configuration guidance for Azure DevOps integration. Ensuring compatibility with common enterprise Git platforms beyond GitHub.com.This feature would be highly valuable for organizations using Microsoft and would align FME Flow with broader enterprise DevOps practices. Please let us know if this request will be considered for a future release and if so, in which upcoming release. Thank you for your support! Kind regards,Joëlle Jansen-SoepenbergFME Consultant
Hi,When you select a date using the calendar in FME Flow UI the calendar persists until you click away. This is a bit counterintuitive and annoying for users . Our users would prefer it disappears on date click. date is chosen and calendar is still there. Thanks,Marc
The new DV functionality seems amazing, I haven’t tried it out yet, but I understand it as one has to provide workspaces for every api endpoint one is creating.Wouldn’t be great if one could easily, in the FME Flow interface, create CRUD (Create, Read, Update, Delete) functionality? This is all functionality that is available in reader/writers, one just have to specify required attributes, primary keys etc.
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.
