Shape the future of FME with your ideas
New and Open ideas are awaiting review or have been reviewed by our Product Management team, and are open for commenting and voting.
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.
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.
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:
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.
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.
It would be nice to have FME Flow have file extension restrictions as to what types of files can be uploaded to the resource folders. The ability to restrict types of extensions, especially executable, would be a major safety addition to Flow. If this could be added by user/groups level, that would allow the sys admins to restrict or allow file types based on their groups. For example, some users only allowed to upload CSV files, others more privileged users can upload spatial datasets, others can upload anything except executable. This also will have the benefit of keeping the resources clean and not be a dumping ground for less experienced users not knowing what the intended purpose of that resource is.
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.
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.
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?
Hi,in the record information you can nicely see data types (uint8, buffer, date, time, varchar) for all available attributes when selecting an individual feature: However, when accessing these information in Python we only get the basic types: Would it be possible to also get the full list of data types in Python?In my current use case, I’m supposed to convert all date attributes to another format. Since it’s a generic workflow, I don’t know in advance which attributes are containing dates. When looking at the schema feature I can see that the data types have been recognized correctly by FME. There is just no way easy way to get that information for each feature.Kind regards,Dennis
Hi everyone,wouldn’t it be cool to have a list of favorite Transformers in the Transformer Gallery? Say, one has a number of Transformers that one uses for most of their workspaces. Instead of typing them in to Quick Add each time, it might be more convenient to have a list in the Transformer Gallery for those few Transfomers. It might also be the case that one does not remember the name of a often used Transformer. With a “list of favorites” it might be easier to add often-used Transfomers to Workspaces. But that would mean that there needs to be the possibility to mark a Transformer as a “favorite”.[Edit:Doesn’t have to be in the Transformer Gallery, a selection of favorite Transformers could also be useful after clicking on “Transformer”]Let me see your feedback on the topic. Is it something others would like too or is it just me?Cheers :)
Hi there, I’ve built workspaces for clients that I need to go over and show them. It is very helpful if I add annotations and bookmarks so the client can follow along with me. However, in a workspace a lot of secondary or unimportant transformers are used (things that are not useful for a client to see to understand the logic of a workspace - think things like attribute removers, csmapreprojectors, list exploders, area and gap overlap cleaners, etc.) It would be nice to have a tickbox inside a transformer to mark the transformer as important to the workspace. So then there could be a toggle to select that could, say, highlight all the important transformers (a different colour, a glow etc.), or it could generate a separate, collaborative workspace that you can use to go over with clients, that just show the important transformers that have been tagged, this can act as a sort of ‘pseudocode’ for FME Cheers,
Custom Transformers to automatically output a Rejected port which returns all Rejected ports from within the transformer
Instead of clicking the green magnifying glass, imagine "hovering" over a port to see a live sample of the data (schema and first 5 rows) in a pop-up, like in the picture below:
The SpatialRelator has the option to output the cardinality of the intersections. It would be really useful to also have the optional functionality to output the actual geometry of the intersection.
May be terribly niche, but I’ve just come across a situation where having a ‘counter’ that assigns sequential letters in alphabetical order starting at C through to J would have been useful. If it’s of use to anyone else, maybe the Counter could count letters...or gets a cousin called the Alphabetiser?
In Jobs; Completed I would like an extra filter option: Succesful jobs with errors. Could you add that one?
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.
Allows the user to be able to gracefully handle failures
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?
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
I can’t see an obvious way to do this already at FME 2024.2, but it would be nice to be able to set the “Out Fields” parameter on ESRI service readers.Often I only need a handful, or even only 1 field from feature classes with enormous schemas. It would be nice if that could be configured in the reader itself seeing as the rest endpoint handles this parameter.Something like this as an example:
I believe this was mentioned in a webinar, but being able to import an endpoint’s schema - from the dataset it is going to be accessing of course - without having to manually create every property would be a great thing to have. This could be from a local file, cloud source, anything. Beyond saving time, it should also ensure accuracy.
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.
