Shape the future of FME with your ideas
Exciting Updates to the Ideas Page! Learn more about the recent changes we’ve made to bring more transparency, ease of use, and a clearer view of how your ideas are progressing.
Open ideas have been reviewed by our Customer Success team and are open for commenting and voting.
It would be helpful if the List option could include basic file properties, such as the last modified date, name of the person who modified it, etc.Additionally, it would be helpful if the Download option could also include attributes showing the original name, URL, URN, last modified date, name of the person who modified the file, etc.
The usage of deployment parameters greatly simplifies switching between test and production environments.When workspaces are used in automations, which reference deployment parameters in transformers, it is not possible to get the information from the corresponding “Run a Workspace” action whether deployment parameters are used and what values they have. The workspaces must first be downloaded and opened in FME Form to see, if deployment parameters are referenced in FME elements.Is it possible to use a symbol in the action to indicate that deployment parameters are being used and to include an overview of the parameters with values in the “Parameters” tab ins the action details (for example like in my sketch)?Thank you very much.
In AutoCAD you can choose if it should display your MText with or without text frame and with or without text background color. Wouldn't it be nice if the dwg writer would offer/accept such format attributes like i.e. autocad_text_frame <yes/no> or autocad_text_background <color> to define the MText appearance?Even better, when the dwg styler can set these attributes.
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.
FME can read AutoCAD Civil 3D, it would also be great if FME could write to AutoCAD Civil 3D as well.
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
I love feature caching. It makes for a smooth and flexible development process.However, there’s one quite painful stone in this shoe.Whenever I have a workspace reading files from a ZIP, the embedded files are copied to a temporary location, to be read/used from this location.The problem is that FME always deletes these files as soon as it stops running, also after a partial run, rendering use of feature caching impossible in this case. One always have to start from the beginning.How about keeping and NOT deleting the created temporary files, until either a new complete run is performed or the workspace/FME is closed ?It does use a little more resources, but will facilitate the feature caching approach.Still works as described in 2025.2 beta.
This is purely just an organisational/visually pleasing feature and has nothing to do with the function of FME, but it would be cool to have an option when you right click on a item on the canvas, and under the “size” drop down, have 2 options call “expand to grid”, and the other as “shrink to grid”. The expand option would snap the corners to the outer boundaries of the intersecting grid polygons, and the shrink would do the same but to the shorter (inner) boundary. I think it would also make the grid easier to use in terms of spacing items evenly on the interface. This is the defaults I get when adding items to the canvas: Items just slightly off filling up the grid polygons. I usually have to manually expand these out to make organising the workspace easier.Keen to know if this has been suggested before or contradicts logic of sizing transformers? Michael
As noted here, it would be nice to have the ability to write additional components such as Classification, Intensity etc, with our Cesium writer.
It would be great if loading spinner is displayed while streaming is in process. Current way of displaying two sentences is not as intuitive as spinner like in this examplehttps://getbootstrap.com/docs/5.3/components/spinners/
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.
My idea is to enable published parameters to be passed to an FME Server app via the URL, in the same way as can be done for executing a workspace via the URL when shared.In my current use case, I have created a PowerBI report which the user will interact with and filter data into a single record - in this case it is a list of calls that the user will make to residents. I want them to record the outcome of each call, so have created an FME Server App which contains published parameters for each field in the database table I'm logging into, which provides them with a form with the relevant parameters and configuration options.What I'd like to do but cannot, is pre-populate some of the parameters in the FME Server App, but leave others for the user to select from/populate.
Please enhance the Rejected port logging. For example, with SQLExecutor and DatabaseQuerier, right now we only see one line from the error logging: “An error has occurred. Check the logfile above for details.”More detailed, actionable errors (as requested for FeatureReader) would remove the need for complex in-process log streaming with dynamic queries.
I love the redirect, but please move this to user preferences instead of being saved with the workspaces. It is way too easy to forget to turn redirect off before saving a workspace and sending it to production. Also, it doesn’t appear that the Redirect option is discoverable by using the FMW Workspace reader. We have 100s of tools, and would be convenient to have ability to search for workspaces that have Redirect turned on.
Since FME 2025 removed the dedicated canvas toolbar zoom buttons which zoomed a reliable 10%, it’s time to fix the only button which we have now.The zoom in/out tool current zooms in/out by 10% relative to the current zoom level. It multiples by 90% to zoom in, and multiplies by 110% to zoom out. This should be changed to a x 90% to zoom in and a divide by 90% to zoom out.Current behaviour → 90%, zoom in goes to 81%, zoom out goes to 89%.Desired behaviour → 90%, zoom in goes to 81%, zoom out goes to 90%.If you zoom in and then out again, it should return to the same zoom state.There are bad zoom levels which cause issues in text rendering, which I’d like to avoid. Multiple zooms in/out will drift the zoom level from the starting point onto a poor number where the text is misshapen or extra bold.
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.
The Hexagon Geomedia SQL Server Warehouse does not allow for displaying the list of databases dynamically within the server/instance the way that other SQL readers do, i.e. Microsoft SQL Server Spatial. Can this functionality be added?
It looks like that either the Postgres Reader and Writer doesn't support multiple column / field constraints. See discussion:https://knowledge.safe.com/questions/78765/multiple-column-key-constraint-is-wrong-interprete.html?childToView=78768#answer-78768If you ask me it's a shortcomming that should be fixed!
Make ProjectWiseWSGConnector able to retrieve and download specific file version and attributes
AttributeExploder: By default the AttributeExploder adds fme_attributes to exploded features. Sometimes you would like this, but in many cases they are unnecessary and must be filtered out. Is it possible to do one of the following options:1. Add an option to choose (or not to choose) whether fme_attributes should be added in an Explode.2. Is it possible to integrate a AttributeExposer to the AttributeExploder in which you can set which (un)exposed attributes should be added and if none are selected none will be exploded.
It would be great if there was a list of all transformers (and their version) and in which version of FME each one was released
Hi there,Depending upon their source Coordinate Systems in FME may or may not have EPSG codes matched to them.For example if our user picks NZGD2K.MountEden from the list I can use the CoordinateSystemDescriptionConverter transformer to extract the EPSG code and use it in the workspace. However if they choose MOUNT_EDEN_2000 then there is no EPSG code associated with it and the CoordinateSystemDescriptionConverter returns nothing.Would it be possible to sync the various coordinate systems so that all available information is available to FME no mater which CS version they choose? I am not able to limit the end users choice in the Server app as I need to cater for all possible coordinate systems.I understand the different coordinate systems have different "metadata" with them, depending upon their source, however this can lead to an inconsistent experience for the end user.Regards,Marc
When adding components to an FME Server project sometimes it can be that I want to add just specific files - e.g., 3rd party python dependencies which are in the root python3.XX folder. 9 times out of 10 its fine to have just the folder, however, if I add the python311 folder to my project because I was just one file from the folder then I end up with all of the other stuff in the folder. Then if I choose to delete the project (and all of it’s contents) then all of the files in that python311 folder are gone too. The same is true if I have just a file sitting in the $(FME_SHAREDRESOURCE_DATA) folder. The fix here is easy enough - just put it in a folder, however, that then requires changing the workspace which may use that file which might not always be that easy or my have knock on effects.
[A Message from Product Management at Safe Software] This idea has been refined from its initial posting. The original description is preserved below for reference.The built-in “admin” user account in FME Flow lacks support for modern multi-factor authentication (MFA), including 2FA or passkey-based login. This poses a security risk, especially in environments where organizations rely on local accounts as a fallback when identity providers like Microsoft Entra ID (formerly Azure AD) are unavailable.This idea proposes adding support for MFA/2FA/Passkeys to FME Flow’s local system accounts. This is critical for scenarios where SAML, LDAP, or Entra ID integrations fail or are temporarily offline, leaving only the local admin account as an option for access. Dear All,I would like to see FME Flow provide native built-in feature to allow users to run FME Schedule or default Dashboards -→ JobHistoryStatisticsGathering.fmw use Microsoft Entra SSO (FME) SAML-based admin accounts.We purposefully disable local “admin” users, since FME Flow doesn't provide 2FA/MFA option for local users but set it up to use Microsoft Entra SSO (SAML) with mandatory 2FA.Your support is appreciated :)Cheers,Reno
Innovyze, now part of the Autodesk Group, have a number of hydraulic software packages which are used world wide. The InfoAsset and ICM suites are used by the majority of UK water companies to manage asset survey data and model their clean and wastewater networks. The software utilises a proprietary database format, across the suit of software. The spatial data held within the database can we exported from within the application to a variety of standard data formats shp, tab, csv etc although there would be a significant benefit if data could be manipulated without the using the software directly
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.
