Open ideas have been reviewed by our Product Management and are open for commenting and voting.
I’d like to suggest FME exposes the Database Spatial Tolerance in the Feature Information window, alongside the projection, dimension, min/max extents etc.This information is critical when understanding spatial filtering, and can account for features being inside or outside specific areas of interest when using a spatial filter within a Reader/FeatureReader, and gives context to the features being retrieved.In Oracle, this would mean reading the sdo_metadata table in the database, but other database types would require differing tables to be read. It would also be useful for FME to perform a simple calculation using the projection and the tolerance together, and write a warning message in the translation log if the tolerance (on the ground) is of a large distance - especially useful when spatially filtering data.Thanks,
Converting my previous question into an idea….It would be very handy when implementing custom logging solutions to be able to get some sort of “stack trace” for where an error occurs in a workspace.It would appear that FME has access to this level of detail since the standard log files in FME Form are able to link to the transformer that produced the error but there doesn’t seem to be any way to access this information from the Logger, Terminator or a PythonCaller.For custom logging solutions it would be very handy to have the name of the transformer that caused an error along with any additional information that might be available.
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.
Asking for an improvement to FME Flow Apps, to better support ArcGIS Enterprise or ArcGIS Online content. Currently web mapping tile services are supported, while these are useful for basic public mapping scenarios, it can be limiting for enterprise users, like ESRI customers who rely on managed GIS content, authoritative operational layers, and internal esri basemap standards. Workflow for Geometry Picker….In FME Form under user parameters there is an input called “Spatial Geometry” type.Define & Select spatial Geometry user parameterWhen this parameter type is published to FME Flow and a ‘Workspace App’ is created, under the ‘Parameter Defaults’ there is an option for Map Configuration, as outlined in this helpful article Using the Geometry Parameter – FME Support Center.proposed UI improvement to Map Configuration in Flow apps - add ArcGIS map services Why add ESRI map support to Flow Apps?Many organisations already manage authoritative spatial context through Esri platforms. When a Flow App requires a user to draw or select an area of interest, the user often needs to see operational reference layers such as boundaries, tenements, assets, work areas, inspection zones, environmental constraints, or approved operational footprints.Without access to these layers in the Geometry Picker, users may need to manually cross-reference another GIS application, which can reduce confidence, increase error risk, and make the Flow App feel disconnected from established enterprise GIS workflows. Desired spatial geometry parameter functionality:Support existing Esri webservice/connections already configured and authenticated in Flow to come into the Flow spatial geometry parameter Allow Flow App authors to configure Esri REST 1. map and 2. feature services as selectable or reference layers in the Geometry Picker. Respect secured services where authentication is already configured in FME Flow, including (arcgis) web connections or stored/encrypted web service credentialsThe old htmlreportgenerator supports the consumption of “feature layer URLs”, even multiple layers if they are comma separated. HTML report generator support Esri leaflet - feature service URLs shared openly I posted on this in the past, and the community wanted the transformer to see more support added as well. HTMLreportgenerator ESRI leaflet - feature layer URL more info needed | CommunityOne issue I anticipate might be challenging 😥, is that the latest ARCGISFEATURESERVICE safe.esri.agol package only supports content that is my content or shared to groups. The above functionality all assumes the esri REST map/feature services are shared to groups. But through the use of web connections to arcgis content, supporting group shared or originisational shared content like basemap services could be explored?the latest ArcGIS feature service reader > its parameters to item sourceThe Background Maps available in FME Form, would be very complimentary if added to FME Flow and Workspace Apps!Much of the functionality could be used in a similar manner 😎in FME form we have ‘background map’ support… how about this in Flow apps? You might find other ideas similar to this onehttps://community.safe.com/ideas/geometry-picker-basemap-using-arcgis-webmap-29298 https://community.safe.com/ideas/set-a-default-map-for-geometry-picker-in-fme-flow-app-29958 https://community.safe.com/ideas/flow-apps-customize-geometry-parameter-search-37946
Nowdays alot of people uses cloud based remote computers for their work. It would be really benefitial to be able to access licenses for FME via a internet based licensserver. This makes it possible to utilize FME on remote computers that do not have access to the on-premiss license server.
Hi, I am wondering if there could be a way to have the option for an FME Flow deployment to act as a License Manager for FME Form Floating Licenses. Our team currently has Form on our desktops, an LM machine on one server, and our Flow deployment on another server. For whatever reason, the connection between the LM server and our desktops always has issues (don’t need to discuss that here), but it made me wonder if Flow could be used as an optional LM. We already had to work with the firewall team to open port 8080 between the Flow server and our desktops, so maybe there could be a way for that port opening/connection to also supply a floating license (if the license was available). Would literally just be the FlexNet License Manager embedded in the Flow app. Would obviously be an optional setting/config in Flow, since I’m sure many people don’t have Flow and still need an LM for Form licenses.
The 'NoFeaturesTester' custom transformer currently out on FME Hub is powerful. However, we're getting pushback from IT from using it in our production workspaces in FME Server. We've benchmarked their work-arounds, and it slows down the workspace significantly (2 seconds with NFT vs. 2.5 minutes with their suggested alternatives). My idea: Harden this transformer and turn into a standard transformer.
A Priority Attribute like in the AreaGapAndOverlapCleaner would be good for the anchor features. Use case is, there are many areas which have to be snapped to different line features with different priority.e.g. road has a higher priority than wall
I am revising/ simplifying the idea it would be nice if to start with the path reader would allow exclusion of write protected (received an error and failed), hidden, system, invalid folders/files. secondly I currently use a tester to exclude many folders that I am not interested in scanning. But this requires a read to get the features through the tester. It would be optimal to tell the path reader to use a list or sheet of folder names to exclude from the read. I know this sounds perf expensive but when scanning several hundred thousand folders the payoff is NOT to read them all before exclusion. leaving this confusing original section below:I have a question in community forum for a flow issue that cropped up. I previously had a ticket with my own IT with an issue that falls into this same category and now a third iteration.in each instance the reader fails and does not continue. whether in form or flow.instance:we receive a zip file that has been incorrectly named. When it is unzipped the folder name ends with a period. (eg. my folder-0name.it doesn’t\matter if there is a\period in the folder it only matters if the folder name ends with period.) this causes the reader to fail and cancel running in both flow and form. I have not identified why the second instance occurs but it is odd that if i am using a reader and it fails with ‘Media is write protected’. see this question here. I understand the 3rd instance is an error on our network. but still can’t the reader detect that it can’t really (with only symlink references) read this and just circumvent the folder? (the error is - PATH Reader: Error reading path '\\Tx-mio-mis01\fw-shared2\SURVEY\CHus\HM_PKG_9_LOWLINES\0_GIS\FOOTAGE_TABLE.xlsx' with error message: 'directory_entry::status: The symbolic link cannot be followed because its type is disabled. Response from my IT dept… From: Helpdesk <helpdesk@topo.sur>Date: Wed, 19 Aug 2026 16:13:56 (UTC -05:00) These are not corrupted. They are a new form of archiving that we have begun implementing. Are they giving you troubles? create specific exclusions. for instance maybe with regex. (e.g. _ARCHIVE) do not read
Hello FME Community 👋We at Safe Software are busy working on some exciting FME Platform enhancements, many focused on product security. We would like your thoughts on one of the ideas that is currently up for consideration.We’ve received previous requests to add OpenID Connect authentication support to FME Flow, and we think that OpenID Connect (OIDC) authentication could be supported broadly across both FME Form and FME Flow.So, before we dive right into development efforts on this idea, we’d like to know what you think about it! Would you benefit from the FME Platform supporting OpenID Connect (OIDC) authentication? If so, can you provide a brief description of how FME supporting OpenID Connect authentication would enhance your experience with the FME Platform? We are also looking for anyone who might be interested in testing out our implementation of OpenID Connect authentication, once available. If you would like to be included as an early tester, please indicate that interest in your response!Here’s a bit of background on OpenID Connect (OIDC) authentication. If you’ve ever tried to create an account with a new app you’ve downloaded, you might be presented with options to use another account (like Google or Facebook) to login to the new app. In this way, you can use an account you already have, instead of creating a new account. This is OIDC authentication at work, and can be considered an extension to the OAuth 2.0 protocol already supported across the FME Platform. More information on OpenID Connect (OIDC) authentication can be found by visiting the OpenID Foundation’s How OpenID Connect Works page. We look forward to hearing from you on this exciting idea!
Being able to reorder the attributes on a transformer is awesome. However, it's also tedious. Repeated right-clicks and selecting "Move Up" or "Move Down" in a long attribute list is painful.It would be great if you could drag/drop attributes to change the order. So instead of clicking and dragging anywhere on the transformer to move it on the canvas, clicking and dragging an attribute should allow it to be moved up or down the list. Then transformers would only be moved on the canvas if you clicked the top of the transformer (where the name is displayed) and dragged it around.
See https://knowledge.safe.com/questions/68957/get-the-last-index-of-an-array.htmlI now know how to access the last element in a list in a single statement thanks to @david_r's answer to this question. So I no longer have to count the list elements then subtract 1 from it before getting the value of the last element in the list. However, in the process of finding out how to do this, I discovered that the ListIndexer allows you to specify a negative number to start from the end of the list.I haven't yet had a scenario where I needed to get (for example) the 3rd element from the end of the list but these situations are bound to arise at some point! So I'd like to suggest that negative numbers be allowed e.g. _list{-3} to start from the end of the list rather than the start.
Request: Please add parameter options for for the Esri Geodatabase Open API reader that allows us to ignore the FeatureDataset path to featureclasses I have an esri GDB with featuredatasets (see featuredataset image)With FME using Esri Geodatabase (file geodb) reader and an ESRI license... it nicely drops the featuredatasets for feature types.... and keeps the featureclass nameDistributionCarrier_HV_OHUse the Esri geodatabase (Open API) reader however and you get ... featuretypes with the featuredatasets in the path. No parameter option to ignore themxxxxxx_Distribution_Carrier/DistributionCarrier_HV_OHI workaround for the OpenAPI is to use stringreplacer to format them such that I can get to the featureclass names, Thanks to AI assist in 2023.1, I can now write regex !
When granting access to connections via a security role in FME Flow, it would be nice to split out the Web Connections from the Database Connections via the interface. Or at least filter by connection type first, then the name. Currently, in the ‘Edit Role’ interface, all the connections are combined.We have over 450 connections in our organization it is cumbersome to assign access to the correct connection via a role.
Hi Safe Software team,We are looking to improve our automated data pipelines by integrating alternative object storage like Cloudflare R2 and Hugging Face with FME but the current Amazon S3 Compatible Storage connection is too strictly tied to AWS defaults.Could you expose a few standard SDK overrides in the S3Connector and Web Connection configurations? Specifically, we need: Free-text Region selection (e.g., to allow auto for Cloudflare R2). Addressing Style toggle (Path-style vs. Virtual-Hosted). Support for namespaced Endpoint URLs (to prevent FME from truncating trailing paths like /my-org for Hugging Face). Advanced Checksum controls (ability to disable strict AWS payload checksums). Adding these standard parameters would seamlessly unlock zero-egress and AI workflows directly within FME Form and Flow. Thanks :)
As of FME 2026.2, the new IFC_API Reader converts IFC geometry of type IfcFixedReferenceSweptAreaSolid into BRepSolids within FME (see IFC-to-FME Geometry Mapping). When these geometries are subsequently written using the IFC_API Writer, they are therefore written as IfcFacetedBrep.I would like to suggest native support for reading, preserving and writing IfcFixedReferenceSweptAreaSolid.The main issue with converting this type of geometry into a BRep is that a relatively compact parametric representation can become a very large explicit boundary representation. A swept-area solid can essentially be described using a cross-section, a directrix and an orientation rule, whereas a BRep needs to explicitly store the resulting vertices, loops and faces.As a practical example, FME currently does not appear to provide a native geometry type for sweeping an arbitrary profile along a path. For a railway use case, I therefore created the rail geometry manually in a PythonCaller by placing the individual rail-profile points along the input line and connecting them to form the final solid. While this works geometrically, the resulting object has to be represented inside FME as a BRepSolid and is therefore written to IFC as IfcFacetedBrep. This can result in considerably larger IFC files compared with representing the same geometry as an IfcFixedReferenceSweptAreaSolid.In one test containing only around 200 metres of rail geometry, the FME-generated IFC using IfcFacetedBrep was approximately 23 MB. After reconstructing the same rail geometry as IfcFixedReferenceSweptAreaSolid, the resulting IFC was only around 150 KB. While the converted file was created as a proof of concept through post-processing, the difference clearly illustrates the potential impact of the geometry representation on file size.Ideally, FME could provide a native swept-profile geometry type that retains the relationship between the profile and the path, instead of immediately converting the result into an explicit BRep. A comparable concept already exists for IfcSweptDiskSolid, which can be represented in FME using the Pipe geometry type.Such a geometry type could then allow the IFC_API Reader and Writer to preserve or create IfcFixedReferenceSweptAreaSolid geometry directly.
The search function is currently local to the active "tab" in the Workbench GUI.It would be very helpful if the searches from the "Main" tab included the contents of all the embedded transformers.This would be particularly helpful when opening workspaces with a large number of custom transformers.
When doing a FME Flow Fault Tolerant installation you need to configure multiple environment, but they pretty much have all the same configuration steps, something that would be useful would be to export the configuration at the end. It would be similar to a parameter file that you could use for a Silent Install.And when you jump on the other machine that you are installing FME Flow, you could provide the configuration file at the start in the installer, you just have to do the change for the machine name.
Hi,When we need to rerun a workspace using the same parameter values from a previous execution, it can be quite time-consuming to go back to the log file and copy/paste each value one by one.It would be very useful if we could select the parameter section from the log, or even better, drag and drop the log file directly onto the parameter section to automatically populate all values.This would make debugging and rerunning workspaces much faster, especially when there are many parameters, and would also help prevent manual input errors. Ref:
When writing PDF it would be good if I could choose to write PDF/A version of the files. PDF/A is an ISO standard specialized for the digital preservation of electronic documents and in several cases it's a requirement when delivering PDF-files to a customer.
I fully understand that Safe wants to make the sending of Success or Failure emails in FME Flow Automations more granular. But the big issue for a lot of us users is that we are at a severe disadvantage due to limitations our IT faces with getting the whole SMTP info set up correctly in FME Flow Automations. For this reason alone, I think it would be useful for there to be a basic emailer that can provide us users with an option for actually being able to use FME Flow Automations and send the one thing we need … An email with success or failure info. As for our company (And I’m sure this is the case at a lot of companies) we can’t use FME Flow Automations and that’s a real waste considering we have a lot of uses for them. Sadly, the Emailer has become the major dealbreaker for us. It’s out of our control as users and wish there was a viable easy option to just have an emailer that can send without having to be tied to a company’s email server.
In an Automation email action, we would like to use deployment parameters to set the following parameters:SMTP Server SMTP Server Port SMTP Account SMTP Password Connection security (less important)Motivation: we have clients with an important number of automations that use the “Email (send)” external action. When the smtp server settings change, e.g. between DEV and PROD environments, it’s a significant amount of manual and error-prone work to change these settings consistently in all the automations. It would be a big help if these settings could be set using deployment parameters:
It would be nice to be able to use ArcGIS web connection to authenticate processes when using the ArcPy library
It would be nice to have the ability to utilize the AI Assist tool in order to read all annotations within a workspace and create summaries or the ability to “search through” annotations to look for something specific.
I would like to see SAML and Office365 authentication added to the HTTPCaller so that it can access information from more different online sources.
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.
