Shape the future of FME with your ideas
Open ideas have been reviewed by our Customer Success team and are open for commenting and voting.
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.
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.
Hi there,If you click on the log out of FME account menu item, then you see this dialog:There is no way to cancel this. I think it would benefit from a cancel button, in case you change your mind.Thanks,Marc
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 available system events is rather limited. Everything should be a system event! Here are several that I noticed are missing:Deployment Parameter published/created/updated/deleted Web Connection published/created/updated/deleted Resource published/created/updated/deleted Automation published/created/updated/deleted Schedule published/created/updated/deleted Stream published/created/updated/deleted Flow App published/created/updated/deleted Project created/updated/deleted
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!
If the information product you want to manage is a hosted feature layer view then at present you need to manually adjust its properties outside your ETL workspace, or tackle the job using the ArcGIS REST API via HTTP.Feature service views offer ways to leverage feature services other than simply as they were created.Here is an example of using HTTP calls to automate one property - swapping the source service for the primary layer..In addition to basic create views, add and remove layers, and delete views functionality for views you might want to adjust name, description, tags, visibility, extent, editing access, definition query, field visibility or layer order.The definition-adjusting REST calls (addToDefinition, deleteFromDefinition, updateDefinition are tricky to implement.Who would like this capability?If you have other requirements comment in this idea.
People love formatting excel documents so they're pretty and represent what they want, me doing it again for FME to understand, not so much.It would be great if the excel reader could pick up if a column was hidden and add it to the Schema details, and if there was a Format Attribute that could indicate if a row was hidden.Or actually an option to not read them at all would also be good.
I would like to propose a new feature for the Excel Writer in FME Form: the ability to automatically enable Excel’s built-in “Sort and Filter” functionality on the output file.This enhancement would allow users to generate Excel files where the column headers are immediately interactive, making it easier for end users to sort and filter data without additional formatting steps in Excel.Proposed Implementation:Add a checkbox option in the Excel Writer parameters (e.g., “Enable Excel Sort and Filter”). When enabled, the writer would apply Excel’s AutoFilter to the header row of the output sheet.Benefits:Improves usability of Excel outputs for non-technical stakeholders. Saves time by eliminating the need to manually apply filters in Excel. Enhances the presentation and interactivity of exported data.This small but impactful feature would streamline reporting workflows and improve the end-user experience.
See for example:https://knowledge.safe.com/questions/78116/excel-featurereader-reading-empty-row.htmlIt would be great to have an option in the Excel Reader to ignore any rows that are completely empty i.e. have no values in them. This option could be left un-ticked if you really want to read in rows from a named range or where there is formatting but no data.This would save having to spend time putting in a Tester or AttributeValidator to filter out the empty rows, or hard code ranges into the Reader when you need to be flexible.Merged Ideas:Add option to excel reader to only read 'non empty excel rows' by thijsknapen on February 20, 2021:When reading in excel files, I noticed that sometimes empty rows are read in. It would be nice if there would be an option in the excel reader, to only read 'non empty excel rows' in the excel sheet.This situation of 'empty excel rows' being read in, for instance occurs when an excel sheet contains cells that only contain formatting (but no value). However, also in the simple case where values are deleted in an excel sheet, the rows for that excel sheet will still be read.I often encounter this situation when I use a structured/formatted excel file as an input for a translation. As sheets are re-used, and not always the same number of rows are entered, there are different number of empty excel rows that are read in in the translation.
It would useful to be able to read password protected Excel files (encrypted workbook). The password could perhaps be set as a reader parameter.
I would love to be able to create hyperlinks when writing out to MS Word documents!
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.
It would be really cool if I can write output as a PMTiles (https://github.com/protomaps/PMTiles) file.PMTiles is a single-file archive format for tiled data. A PMTiles archive can be hosted on a commodity storage platform such as S3, and enables low-cost, zero-maintenance map applications that are "serverless" - free of a custom tile backend or third party provider.
The Tester and TestFilter transformers have five distinct Comparison Modes:Automatic Numeric Case Sensitive Case Insensitive Date/TimeAs well as the option to Specify Per Test.The FeatureJoiner and FeatureMerger transformers have three Comparison Modes:Automatic String (presumably the same as Case Sensitive, above, but I have not validated that and don’t see it specified in the documentation) NumericAnd the way that these transformers are designed, they are inherently “Per Test” or per “Join On” condition, as it were.The general Idea here is to make the Comparison Modes more consistent across transformers - there are likely other transformers that could be included in this, beyond the four mentioned above.Case Sensitive, Case Insensitive, and Date/Time could be useful in the Feature-type transformers, in addition to the Test-type transformers. There are other ways to achieve these, of course, but there may be value in having them readily available. The order in which Comparison Modes are listed could be consistent - this is a minor point.If the various types of Comparison Modes are already tailored to best match each class of transformer, then the idea may not have merit, but posing it in case others could see any value in the proposed change or a similar change.
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.
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.
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.
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.
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.
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.
