Open ideas have been reviewed by our Product Management and are open for commenting and voting.
With the upcoming release where a Python IDE will be integrated with FME, the next, and most important logical steps is to pass cached data into the IDE for the purposes of debugging calculations and logic flow. I do not know how the integration with the Python IDE will be released but being able, at design time, to open the IDEA in debug mode is a powerful way of seeing how cached data flows into the PythonCaller, through the python logic, and then back out again.
PDF/Word documents have the ability to create form fields for users to fill in. Looking for the ability to auto-populate some or all of these fields from a database record. Ideally, the writer would accept a template .docx or .pdf and allow the field from the database to write to a field in the form.
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:
Currently, we can only set the default layer color in the DWG Writer using a color index. Various CAD standards also work with layer colors based on RGB values. I would like to see this expanded so that it can be set using both color index and RGB values.This will avoid having to create templates with thousand of layers manually (extensive cad standard).
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.
Hi FME Server Team,I would like to request an enhancement to the FME Server REST API.API Endpoint:/transformations/jobs/completedEnhancement Request:Currently, it is not possible to filter completed jobs by their finish time using this endpoint. I would like to request support for querying completed jobs by finishTime, in addition to filtering by repository and workspace.Use Case:For monitoring and automation purposes, I need to programmatically retrieve jobs that have successfully finished within the past 5 minutes, filtered by a specific repository and workspace name.Example Query:repository: <repository_name>workspace: <workspace_name>completed successfully (completedState: success)finished within the past 5 minutes (finishTime >= <timestamp>)Having the ability to query by finishTime (ideally with support for both a start and end range, or a relative time based on current time eg. last 5 minutes) would greatly streamline our integration workflows.Thank you for considering this request.
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.
Further, it would be convenient if the description and Workspace/Transformer Help would be synchronized automatically, for published parameters.Add Description field to Add/Edit User Parameter dialog (below).For published parameters, link the Description and Workspace/Transformer Help. If you edit Description of the parameter, apply it to the Help automatically, vise versa.
FME Flow currently has columns in the Jobs Completed screen like the workspace, source, date/time, engine, etc.What happens for bulk dynamic data replication is you need to run the same fmw multiple times with differing parameters. e.g. a SQL Server to SHP Downloader that runs on a single table at a time.Whilst yes you COULD run the workspace only once (reading hundreds of thousands of features), this not only adversely and unnecessarily affects server resources but means a single error affects all data. Instead, it’s best to run the workspace multiple times (once per SQL Server table) via say a FMEFlowJobSubmitter.In FME Flow this means you get the Jobs screen full of hundreds of the same workspace with a differing date. There’s no way to tell at a glance what parameters caused the 10 out of 200 jobs of the same workspace to fail.I’d like to see a parameter exposed in the Jobs screen so that I can see at a glance that Table ABC and XYZ failed. Not that Workspace123 failed 10 times with unknown parameters. Yes, I’m aware you can click into each job manually and that yes we could setup a log-reader workspace to do this. Or that we could setup a postprocessing task. I have setup such before - but it’d be nice out-of-the-box in the Jobs screen.This could be a standard parameter or a FME Flow parameter that can be set by the author (e.g. linked to a Published Parameter).Thanks.
Hi there,In this article (Configure user attribute mapping with Azure AD SAML Provider – FME Support Center), a group claim can be setup to pass an AD group name which aligns to a role in FME Flow. As a group claim could be based on a search criterion and many AD groups could be returned which is a common method of Enterprise group membership in ArcGIS Enterprise software. I was wondering if this could be used to grant several roles to a user?Looking at controlling access to repositories, who can view workspace and who can run a job, etc via AD group assignment.Thanks
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.
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.
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.
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.
The FME Sharepoint reader and writer support a boolean "attachment" field, but can't read or write attachments themselves. It would be great if FME added support for attachments so that they can be downloaded or uploaded via the Sharepoint reader/writer.
There are times where I would like to store more complex data as a parameter, I have resorted to json or comma-separated text (multi-line text parameter). This is mostly private parameters that specify data source, configuration or possible some initial data. In nature this data is tabular, most of the time.Maintaining json/text in a parameter dialog today is cludgy Getting the data into features requires multiple transformersNow, wouldn’t it be nice with a table parameter type? Using a parameterfetcher could possible read the table into a list, that one can just explode/expose. Maintaining the data in a dialog set for a table would also be easier… !
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 :(
As an FME Flow User, I want to be able to redirect jobs from one queue to another so that it may run on a different engine while another job is occupying the originally intended engine. At this time, the only relative alternative is to cancel the job and resubmit using advanced drop down and selecting a job queue. The problem with this solution is that this interrupts an automation’s natural flow.
Data Virtualization is a great tool to share functionalities and data translation results standardized. One great thing is the automated creation of an interactive Swagger UI documentation, which enables also non FME users, as one part of the target group of Data Virtualization, the accessibility to translations. Comparing the Flow Rest API with an automated Data Virtualization, it would be great to have the opportunitiy to authenticate with a token. Missing field for token in Data VirtualizationToken field in Flows REST API (v4)
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.
