Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
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
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."
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’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.
https://knowledge.safe.com/questions/38771/can-i-use-a-feature-merger-to-merge-partial-names.html https://knowledge.safe.com/questions/39153/merge-features-by-attribute-that-contains-string-f.html?childToView=39163#answer-39163
Hi,some formats (such as the Text File reader) have fixed schemas that will never change. In the case of the Text File reader the only attribute in the schema is the text_line_data attribute.For these fixed-schema formats, I would like to request an enhancement to the FeatureReader to have the schema automatically exposed, even when the Generic output port is configured. Currently, the schema attributes are only exposed for named output ports.For context, I refer to the following Community question: And to my own support question (to which James Cheng provided a very comprehensive reply):https://support.safe.com/hc/en-us/requests/64419I have reproduced James’ reply below, as it so clearly explains the situation:Thank you for raising this. I understand the frustration as I share the same thoughts and can see why you'd expect the text_line_data attribute to just be available when reading a Text File through the FeatureReader. The behavior you're seeing comes down to how the FeatureReader's generic output port works. This port is a catch-all that merges everything into a single stream, designed to handle any format and feature types with varying schemas. Because of this, it doesn't commit to any schema at authoring time, it doesn't make assumptions about which feature types or attributes will be present, so all attributes come through unexposed by default, even for predictable formats. By contrast, when you use a named output port (or a standalone Text File Reader), the schema is known at authoring time, so the attributes like text_line_data are automatically exposed. In essence, by using the Generic port, the trade-off is flexibility over schema awareness, it can handle anything but at the cost of not pre-committing to any specific attributes. However, as you've rightly pointed out though, the Text File Reader always produces a predictable fixed schema with a single attribute, text_line_data, no matter which files/feature types are being read. So there's a reasonable argument that the FeatureReader could recognize this and auto-expose it on the Generic Port since there's no ambiguity what the output will be. Currently, the Generic port doesn't differentiate between fixed schema and variable schema formats as it applies the same "unexposed by default" behavior uniformly across the board. That said, I think this is a genuinely good candidate for a product enhancement for the generic port. I'd encourage you to post this as an Idea on the FME Community, specifically requesting that the FeatureReader auto expose known attributes for fixed schema formats like Text Files on the Generic port and describing your use case. Community support helps the development team gauge interest and prioritize ideas for future releases, and we can link this ticket to the Idea to keep it on their radar. In the meantime, it's worth noting for this specific format, the feature types are all fixed to text_line, so using the default One per Feature Type output port setting will also route all text file features through a single text_line named port, similarly to the Generic Port, which will expose the text_line_data attribute automatically. If your workflow requires the Generic port, then the only available options are manually setting the Attributes to Expose parameter on the FeatureReader or placing an AttributeExposer downstream. regards,Nic
This idea is a specific use case of the more general:This idea exists simply to assist people searching specifically for information regarding exposing the text_line_data attribute on the Generic port of a FeatureReader when reading Text File data.
In the Autodesk AutoCAD DWG/DXF-writer (and in the other DWG writers too) it would be good if you could choose an attribute for Layer Description, Default Linetype, Default Color and the states: On, Frozen, Hidden, Locked, Plottable. It's not so usable right now when you need to hard code these values which makes all layers look the same.
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.
The current customization options for FME Flow Apps is quite poor. FME Flow Apps have the potential to be a centralised focal point/application for organisational/enterprise level ETL; however, they currently allow for minimal flexibility and design when it comes to styling.The lack of flexibility and options for design improvements mean that even with greatest graphics/design eye in the world, FME Flow Apps are often left looking nothing more than a data dropzone, workspace runner or ‘Click to Download’ link.Expanding the options for image customization and editing, greater flexibility in text design, or incorporating HTML would greatly enhance the visual appeal of FME Flow Apps. This would increase visibility and improve perceptions to none FME users who are given access to a Flow App.Documentation could also be created in the form of a technical article on ‘Designing and Styling an FME Flow App for your Organization’ to support this process.
White Box Tools is an open source geoprocessing package made by the University of Guelph.Its key benefit is its extreme speed, being able to process tools between 5 and 50 times faster than ArcGIS Pro. It would extremely beneficial if FME included an WBT transformer which could allow users to pass FME data to WBT and allow the user to select which WBT to run (there are hundreds). This would greatly expand the raster capabilities of FME, and include some functionality which is currently lacking in FME (viewshed)Whitebox Geospatial
On FME Flow you can filter failed jobs. It would be great to be able to filter by error message. This way if you’re trying to troubleshoot an error that is occurring you can easily see which scripts have been impacted.
If we are logged into the community can the webinar registration form be auto-populated or just accept the registration from an existing member.It is a little annoying having to constantly fill in the registration form to watch a webinar, especially as I am an existing member of community and all the details are part of my profile.
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.
Enhance Extruder transformer to have the option to extrude geometry along a complex path similar to the way AutoCAD does to create 3D lines, surfaces, and solids.
Currently the VariableSetter/Retriever can be used to set/retrieve just one global variable. It would be more convenient if multiple variables could be set/retrieved at once.
Is there a way to have feature writer (PNG format), to generate .pgw instead of .wld file?For feature writer (JPEG format) it has option to change .wld to .jgw Just wondering if it would be possible to do that with PNG as well? Currently I change the .wld to .pgw manually. I know there’s a way to use SystemCaller to make it change the file extension. But it would be helpful if we can just skip that entirely because it may not work as expected when we Publish workspace in FME Flow. JPEG Format PNG format
It would great and highly beneficial to see the exact processing time for each individual transformer directly on the transformer. This feature would allow users to easily identify bottlenecks and optimize workspace efficiency without manual benchmarking in the log.
When you add a "file" manual key to an automation which get run by an automation app, the option is to choose a file already in the resources of FME Flow. It would be nice to have an option for a user to upload a file like what's already available in workspace apps. For a User Parameter "File" the user is able to upload a file which gets used by the workspace the workspace app runs. The same would be ideal for automation apps.
***Note from Migration:*** Original Title was: Option to use @Value(AttributeName) in the AttributeRenamer for New Attribute Names Add the option to use @Value(AttributeName) in the AttributeRenamer for new attribute names.
I would like the ListSorter to support multiple sort-by criteria, similar to the regular Sorter. Example:Currently (FME 2018.0.1) you cannot use multiple ListSorters to accomplish the same thing, since the ListSorter doesn't preserve the existing item order on duplicate sort keys (PR83992).
Either as a new transformer or as an option in the StatisticsCalculator transformers (standard, raster, pointcloud...list?)
***Note from Migration:*** Original Title was: Add Support for Aggregate Geometry Type (Esri ArcGIS Online (AGOL) Feature Service Writer) Add support for writing Aggregate features with the Esri ArcGIS Online (AGOL) Feature Service Writer.Currently this is not supported: https://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_ReadersWriters/arcgisonlinefeatures/quick_facts_arcgisonlinefeatures.htmExample of community discussion of this feature: https://community.safe.com/s/question/0D54Q000080hRcE/cannot-write-to-esri-after-using-aggregator-mutipart-geometry?t=1619549337262
Would be great to have a Search Filter In the dialog which is handy when there are several workspaces in the same repo.
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.
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.
