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.
Hi,the birds are chirping that Bentley is soon to phase out ProjectWise login via logical accounts. It would be nice if there was an option to connect to PW via IMS login as a transformer or an option to configure the connection in the settings
Currently, in FME Flow, when a user edits and saves an existing schedule, the scheduled job appears to run under the username of the last person who saved it, even though the ownership of the schedule has not changed. This behavior can cause issues when the last editor does not have the necessary permissions to access specific data sources or resources, leading to unexpected job failures.We request that schedules retain the original owner's execution context, regardless of who last modified or saved the schedule settings. Saving or editing a schedule should not modify the account under which the schedule executes unless the schedule's ownership is explicitly changed.
We would like to request support for Azure DevOps as a remote Git provider in the Version Control functionality of FME Flow. One of our clients recently upgraded from FME Flow 2024.2.1 to FME Flow 2025.1.2. In the previous version, they were successfully using Azure DevOps Git repositories to manage workspace versioning. After the upgrade, they are no longer able to push changes to their remote repository. The UI reports: “There was a problem communicating with the REST API.”And the backend logs show HTTP 500 errors when attempting to push.According to the documentation, only GitHub.com is officially supported. Azure DevOps is not listed, although it previously worked without issue. This limitation significantly impacts their ability to maintain version history and collaborate effectively. Could you please consider:Adding official support for Azure DevOps Git repositories in FME Flow Version Control. Providing documentation or configuration guidance for Azure DevOps integration. Ensuring compatibility with common enterprise Git platforms beyond GitHub.com.This feature would be highly valuable for organizations using Microsoft and would align FME Flow with broader enterprise DevOps practices. Please let us know if this request will be considered for a future release and if so, in which upcoming release. Thank you for your support! Kind regards,Joëlle Jansen-SoepenbergFME Consultant
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.
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.
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/
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.
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.
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
Hi everyone,I’d like to share an idea that could significantly streamline our workflows in FME Form, particularly when working with a lot of fields with the AttributeManager.Imagine this: an AI-powered enhancement that automatically detects and intelligently renames attribute fields based on your past workbenches or predefined naming preferences.🔍 Here’s how it could work:The AI would analyze field names like horizon_canopy_trees_percentage and suggest a cleaner, more intuitive name like CANOPY_PERCENTAGE. It could learn from your previous projects to suggest consistent naming conventions. You could set parameters such as: Use of capital letters or snake_case Abbreviation rules Context-aware naming (e.g., recognizing that “canopy” and “percentage” are key descriptors) Share an Excel file with fields name that the AI could associate with the fields in the AttributeManager.💡 Why this matters:Reduces manual renaming effort Promotes consistency across projects Makes workspaces easier to read and maintain Saves time, especially in large or complex datasetsI believe this could be a powerful addition to FME’s smart automation capabilities. I’d love to hear your thoughts, feedback, or any ideas to expand on this concept!
Working with readers that are either single merged feature types or datasets that do not expose attributes, e.g. CAD, XML, JSON or OSM PBF, as an author, I’d like to have as an option to be able to see attributes that are imported in the AttributeExposer to show the number of features that have values..Adding an option to show null, missing and empty values would be a nice feature too. When I import from cache, it would be nice to see the attribute value stats when Importing attributes. There’s room for columns to show the count for all.With this feature, the author can pick attributes that have values, keeping the destination cleaner. AI Assist recommends a Tester transformer plus counter to do this.The community hub transformer AttributeValueCounter was a good option to use for this but it does not work in FME ENGINE 2025.0.x. Just some random ideas, when Feature Cache is enabled for a workspace, during a translation run a background process can calculate the stats on the source feature types initially. Perhaps add that to the reading of the schema when a reader is configured to be added to the canvas.Get the unexposed attribute stats immediately optionally. Maybe just have a checkbox on the Import from Feature Cache or Import from Dataset dialog to allow the option.
In the Data Inspector and the Visual Preview pane, I would like to suggest a function that uses an LLM to automatically assign styling to the shown data layers (best effort), based on the name of the layers.This function should allow quick symbolization and automatically suggests fitting colors and symbols for vector layers. It should not replace the existing style dialog.The result should be predictable and reproducible layer styling between workspace executions on the same, or similar, datasets.
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.
