Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Cannot decode values in input field for above. Could the inclusion of extract parameters be added to a future release?
***Note from Migration:*** Original Title was: Apply "Max Feature to Read Per Feature Type" to all features listed in Feature Types to Read. Max Feature Types to Read applies to the feature types on the workbench canvas. So if you use Merge Feature Type (and only have one feature type on the canvas) then that will count as only one feature type. Say you set Max Feature Types to read to 2. If you use Merge Feature Type, only two features are read instead of two features per feature listed in the Feature Types to read parameter. Max Feature Types to Read should also be applied when Merge Feature Type Filter is used along with the Feature Types to Read.
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."
Please create an FME option to connect to GCP (Google Cloud Platform) using “Workload Identity Federation” method in addition to Service account (current option).Thank you!
I'm curious if there's a straightforward way to make FME lineage information accessible for data catalog systems. Have you all thought about enabling FME with OpenLineage? I’m not sure how that could work, but I’ve noticed that data catalog products are beginning to adopt this standard. Imagine how great it would be if FME could effortlessly share lineage info with popular data catalog tools like Microsoft Purview, Collibra, and Alation! This could be a game-changer for organizations that truly value solid data governance and tracking. What do you all think? Is this feasible, or are there other existing alternatives?
The FME Flow interface allows for custom System Cleanup Tasks to be created but there is currently no way to trigger these tasks to run manually. Instead, you need to wait for the automated scheduler to reach the time period defined for the Normal Conditions Task Interval, which is 1 Day by default: Being able to trigger a task manually would be very useful when creating a custom task as it would allow for rapid testing to ensure the task is correctly defined and working as expected.Please add the ability to manually trigger a cleanup task.
Trying to find/clean up duplicate connections. Would be cool to have a list of workspaces that are using/have recently used a database connection on FME Server when you select the connection
As a follow-on from my question and the response from @zoe.forbes after we upgraded to 2026.1 and I found the info icon and blue banner in workspace apps have been removed for message-type user parameters. The icon and banner were useful and I think important aspects of the message parameter and outlining information in workspace apps. I haven’t found any requests to remove them and I think it is well worth restoring them.
I would want to be able to retrieve information about automation schedule.I see several similar requests in Ideas, and it looks like it was possible to do with FME Flow v3 API using schedules endpoint. I’ve tried <FME_URL>/fmeapiv4/schedules?limit=100&offset=0&includeAutomations=trueThe API call didn’t fail, however it returned only schedules and no scheduled automations. The v4 API documentation doesn’t have includeAutomations param, so I am rather surprised the call didn’t fail.The automations endpoint has nothing about triggers or schedules either.In general, it would be helpful to be able to retrieve information about automation trigger and, if the trigger is a schedule, information about the schedule. One of the use cases for this would be administration of an FME Flow hosting multiple projects and used by many users/teams. Somehow, midnight seems to be the most popular choice when scheduling automations. As a result, there is a long list of automations triggered at midnight, and if one of them gets stalled… there is a surprisingly long queue with time sensitive jobs in it in the morning. If I was able to retrieve schedule info, I would create a dashboard to monitor scheduled triggers distribution
Hi,It would be a nice feature to add support for SLD files. They're XML files, so it ought to be fairly straight forward.Some sort of cross-format support to input/output styles handled by the various style transformers, so I could e.g. read an SLD at designate it to output as MapInfo styles directly, or e.g. output an SLD file based on MapInfo styles, would also be very neat. This is nice-to-have though, and may be a little more complicated.Note that there may be version issues to consider.If this can be achieved by packaging some templaters etc., that's great too.Cheers.
Currently FME Server is routing jobs to available engines with the round robin circulation. One of the main benefits of dynamic engines is that job can use these (only) if there is peak demand. Currently jobs can also be assigned to dynamic engines if a standard engine is available but the circulation system decides to use the dynamic engine.My suggestion is to have FME Server 'see' dynamic engines differently than standard engines to be able to only assign jobs to dynamic engines if no standard engine is available.With this we don't have to pay for standard engines that are idle most of the time, can use dynamic engines only when needed and we don't lose credits on using dynamic engines when a standard engine is available.See also discussion here.
Enable a feature that allows user to view the workspace (either as an image before you open it - like Windows) or by opening the workspace in View only model. When editing is required, a license is checked out. Not a money spinner for Safe (!), but would allow users to check logic/undertake basic QA without checking out a production license.
Hi there, Sometimes in a large workspace, I need to zoom out and select a large area of transformers (to either create a bookmark, select them to move or delete, etc.), however at a certain zoom level I don’t have the granularity to control exactly what I’m selecting (I might be selecting things that I don’t want to select, then I need to zoom in and unselect these things). It would be helpful, at a certain level of zooming out a workspace, to show a little pop up window when you start clicking and dragging the cursor to select things, so that you can see where in the workspace the cursor is and then control what is being selected. Cheers
I wondered, maybe Safe could add an option to the Sampler to drop unsampled data, instead of sending it out of the unsampled port.Why?Because when I run a workspace with caching turned on, it’s using up resources caching unsampled data that I don’t need. This is especially true since I was set up to sample only the first feature. Having obtained that single feature, I really don’t need the Sampler to carry on storing other data. In fact, I don’t really need it to carry on processing at all!
Our customers are asking for this, when creating APIs with FME Server's REST. At the moment REST API Service only uses tokens for authentication and not OAuth.
FME currently does not provide a native way to control compression of raster overviews (pyramids) when generating outputs such as GeoTIFF or COG, limiting the ability to optimize file size and performance.In real-world workflows, especially when handling large raster datasets, overview compression is essential to ensure efficient data access and reduced storage requirements.At present, achieving this requires the use of external tools, which breaks the native FME workflow and adds unnecessary complexity.Request:Add native support for overview compression (method, quality, predictor, etc.) in raster writers or transformers.This would enable fully native workflows within FME and significantly improve efficiency in production environments.
Currently you have to go directly to a remote engine job logs and log in to see job logs, It would be great to be able to see all logs from one place i.e the parent flow instanceIf a job runs on a remote engine, I would still like to see the logs in the parent flow instance
If a user changes the Connection Storage to FME Flow some challenges need to be solved.Every time the user wants to add a new (Web) Connection which FME Flow doesn’t know, it can’t be added because the Service Definition need to be uploaded first.For example, on a completely new FME Flow only three Web Services are available. If the user wants to add a Dropbox Connection it is not possible at all and the Web Service dropdown stays empty [1].For now to upload the Service Definition the user has to change the Connection Storage back to Local Storage and choose one of the following wayscreate a connection for this type and upload it to FME Flow upload just the Service Definition to FME Flow via FME FormAfter that the user needs to change the Connection storage back to FME Flow. Idea:Add the functionality toupload the Service Definition if it doesn’t exist on FME Flow directly in the creation process for a new Connection, so that if a new Connection will be created it will automatically upload the Service Definition in the backgroundorstore the details in the background and upload these during the Publishing Wizard if it will be necessary for the process to run on FME Flow[1]
When inspecting features, particularly identifying point geometries, I find myself wanting to visualise the Identifier attribute for alot of points, sometimes along lines and centre of polygons. Obviously desktop GIS have this functionality…. but I’m asking to build on the Mark location option which already has a Label option. Can this same code be added under the Display Control, where users edit the styling of each dataset/layerData Inspection lacks functionality to add simple labels for a point dataset/layerA workaround in workbench is to use LabelPointReplacer transformer to create text geomSo the updated UI will need Label section in the drawing style… and as pictured belowability to select the Attribute Value column and make this the label text the font and colour would be nice label size (replacing font size?) may also be of assistance, though projected coordinates are likely needed to display in metresDisplay Control drawing styles to include a Label
At the moment, it takes some effort to figure out what Python install is used by FME Form and what Python install is used by FME Flow. This becomes a problem once additional libraries need to be installed on FME Form and FME Flow, especially if they are installed on the same physical machine or AWS instance. I would like to propose some changes which will improve user experience:making Python install locations more obvious during FME install; having the same default location for FME Form and FME Flow Python installs; exposing Python install(s) used by FME Form in Utilities > FME Options; somehow exposing Python install(s) used by FME Flow in FME Flow WebUI; making repointing FME Form/FME Flow to the preferred Python install… well, effortless.
Can FME add support for Vulcan files (by Maptek): .00t, .isis, .isixIf anyone else is interested, vote for this idea and add a comment about what transformations you envision performing in FME with the Vulcan files.
As noted here, it would be nice to have the ability to write additional components such as Classification, Intensity etc, with our Cesium writer.
Currently, when transferring projects between different environments (e.g., TEST to PROD) in FME Flow, it is necessary to use the same “global” encryption key across those environments.From a security standpoint, reusing the same encryption key across multiple environments is not considered best practice.It would be great to have “project-level” encryption keys, allowing each project to be encrypted independently of a global system key.
Add a 'Case sensitive' option to the Joiner. Sometimes capitalization of attributes differs between source and target attributes. It would be nice if you could just use an option to take this into account or not.
I’m downloading bulk CSV data from an open data site, each download is gigabytes, I would like to set the output filename to a .zip file, to save space.
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.
