Shape the future of FME with your ideas
New and Open ideas are awaiting review or have been reviewed by our Product Management team, and are open for commenting and voting.
When using an SQLCreator or an SQLExecutor, and something goes wrong (for example the query takes longer than the timeout-limit, or something like that), you can use the Rejected port on the transformer to catch that - which is imperative when using in a webapp, because you’ll need to give the end-user feedback. On the Rejected-port you’ll get the _reader_error attribute, but the way that one is populated is not very helpful. The contents of that attribute are always An error has occurred. Check the logfile above for detailsIt would be very helpful and much more meaningful if the contents of the Provider error, which is always in the previous log file line, was added. Because then I could catch that and show that to the user:(-2147217871) Query timeout expiredwhich is much more helpful than “check the logfile above” (there is no above - there is nothing, because this has been handled through HTMLReportGenerators to return to the end user’s browser).On FME Form it’s not a big problem, because you’ll have the logfile right there - but when you then upload your workspace and create a webapp, I’d like to be able to provide more meaningful feedback to my users (and myself).
The opposite of the attributeExposer. Sometimes I need to temporarily expose an fme_attribute in order to preserve it's value (ex. LineJoiner) or replace it's value (ListIndexer), but would rather not have it trailing through the rest of the workspace, especially when this takes place within a custom transformer.
When you add columns to, let’s say FME Jobs Completed page, the following occurs:Scrolling Bar Menu is displayed at the bottom of the page which is rather inconvenient. Edge display the page content better than Chrome as in re-adjusting the columns when adding / removing columnsFound it at the bottom of the page whilst looking for it
Assuming it’s possible, FME Form should look in the same folder as the workspace for FME related components - e.g., CustomFormats, CustomTransfomers. In FME Flow if you have a CustomTransformer which lives in the same repository as a workspace it will work. It would nice to be able to keep CustomTransfomers in the same location. As it is right now in FME Form if you want to keep all files related to a porject together you need to copy the version from the location where FME can find it (e.g., FME folder) to your project folder.The process is problematic because you quickly run into issues with copying and keeping track of the version which you’re actually working with in workbench vs what is in your project folder.
It would be nice if we can choose an ArcGIS webmap to use as the basemap of the GeometryPicker. This would be very nice to use with the Web App.
The GDAL libraries are highly efficient both in terms of performance and in terms of the integration of very specific raster functions.It would be very useful if FME were to integrate these libraries natively, so that they do not have to be installed and run separately via Systemcaller. This is often difficult on FME Flow instances.A potential GDAL-Caller transformer could enable them to be executed
[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
Add the "EWKT" Geometry Encoding definition to GeometryReplacer and GeometryExtractor.EWKT is a simple extension to WKT that allows to include the coordinate system with the geometry, for instance: "SRID=4326;POINT(-44.3 60.1)" instead of "POINT(-44.3 60.1)"https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometryEWKT is supported by Postgis and can be found in many open datasets.
Currently the translation log window starts with a messageCommand-line to run this workspace: "C:Program FilesFME2016.1.1fme.exe" someWorkspace.fmw --Param1 "Value1" --Param2 "Value2"but this information is not reflected in the log file itself, and unless you have a ParameterFetcher+Logger, you cannot easily recreate the settings of a workspace with just the log file.I would like an option in the Translation Log Settings to write the (published) parameter settings to the log file. Perhaps as part of the FME Configuration Inform messages?
Hello,We are currently expanding the use of Apache Kafka across our organization, and more and more departments are requesting access to published topics.Unfortunately, I cannot use the Apache Kafka Connector in FME to publish data because our Schema Registry is protected by authentication. When the connector tries to access the Schema Registry, it fails with an "Unauthorized" error.As a workaround, I developed a custom Python script that publishes the data directly to Kafka. While this solution works, it is far from ideal. One of the main advantages of FME is that non-developers can build and maintain integrations without writing code. Not everyone in our department is comfortable with Python, so relying on custom scripts creates an additional maintenance burden.It would be great if the Apache Kafka Connector supported authenticated Schema Registries, allowing users to publish messages directly through the native connector without requiring custom Python implementations.Best regards,Felix 😊
It's not always possible to print to a PDF, so it would be nice if you could export the entire workspace canvas as a graphic file for documentation purposes.
In the current situation + Finland & Sweden joining NATO there is more demand to support Nato Vector Graphics (NVG) -format. Just read a RFP where it’s a must and waiting for more similar RFP’s to come. It’s not just the military people who ask for it, it’s also e.g. border control and who ever is providing services for them.
When using a FME Server App which fails for some reason there is no built in way to return an error message to the user. It is always an unknown problem.It would be great if there was a way to return a few more details to the user. This is particularly important when an invalid dataset is uploaded. Without a workaround there is currently no way to let the user know their data needs to be fixed.
re-proposing the past idea:
The following improvements to Role Based Security would be useful:1.Increased Granularity for Job Viewing and Job Management PermissionsI need the ability to allow users to see specific other user’s jobs and logs rather than all jobs and logs. We use different service accounts for different enterprise projects and currently I am having to share all jobs/logs with users so they can monitor their processes. Since not all groups need to see each other’s jobs this is not the best solution. (Thank you Safe for new search options in 2019 as they slightly help with this issue.)Likewise, in the current Role system being able to view all jobs requires job management permissions which let users cancel jobs in the queue or terminate running jobs. This puts me in a difficult position regarding how we implement SOX compliance. It is preferred users be locked out from managing running production processes. If the ability to view all logs but not manage jobs was made available that would be a move in a positive direction. If the option to say kill queued jobs but not running jobs was an option that may also be useful.2. Additional Options on Database ConnectionsHaving a Read option alongside the Full Control option for database connections would be excellent. I am seeing issues when I grant users access to connections without giving them full control over a connection. Since we have many processes using the same named database connection it is not ideal to grant users management access since one incorrect change by any user with access could disrupt jobs for all users using the connection. Something similar to how the Notification items are broken out would be amazing.3. Automatic Content Sharing with Administrator AccountsIt would be helpful if FME Server automatically shared user created content with members of the Super User role. If this could be an option for the FME Admin role that would also be appreciated. I have a plethora of users creating content and when they ask for help it is cumbersome to have to share their content with myself and my fellow Admins before I can help troubleshoot.
When downloading data using Data Download service (e.g. from an FME Workspace App), a Zip file is created containing the output files. The zip file is automatically named something that looks like “FME_4B425D3A_1772473610895_13172.zip”. It would be nice if an option was implemented to allow customizing that name to something that is more user friendly. For example allow authors to specify what exact name the Zip file should have, or allow the use of parameters to create a string to use as file name. Even if the final filename has to have some extra characters at the end like 4B425D3A_1772473610895_13172, giving authors some customization capability would be beneficial.
From this question: Toolbar connections are stored separately to Web Connections. When you change to using FME Flow as your Web Connection storage you can’t separately manage your toolbar connections.I wonder if an approach could be that the toolbar connections are their own separate ‘connection type’ that shows regardless of you connection storage settings? Additionally this could then give you the option to copy to/from the toolbar and connection storage
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.
A parameter is like an argument that is static. A variable, however, represents a state and can be dynamically created and assigned in a workspace. I wish FME workspace UI exposes variables the same way it exposes parameters or attributes. Converting variables to attributes via VariableRetriever does not help, as attributes are about content while variables are about states and flow control.I am in agreement with @bambography in his or her post. https://knowledge.safe.com/questions/34563/can-global-variables-be-accessed-as-values-in-tran.html
It is currently not possible to style inline text other than choosing a type of content first.As in, chose Content Type as “Paragraph / List Heading” first then format the whole text in, for instance, pale blue / underlined.In my case I’d like to highlight a hyperlink, formatted in pale blue / underline, as part of my sentence or list or any other Content type. Example below using a DocumentPDFStyler with Markdown enabled:Go to ‘My Account’ online at --@Value(mvdc_site_hyperlink)-- and registerIt would be good to be able to style @Value(mvdc_site_hyperlink) separately but part of the same text.Not sure if feasible but hoping for an implementation of this Idea.
I would like there to be a level of access to job logs which allows a user to See any jobs run by any user that are within a repository they have access to Download any job logs for jobs that are in a repository that they have access toSimilar to what is described hereGrant read only access to a user based on a role | Community
Hi,it would be nice to have the same option as in ArcMap when visualizing data either in visual preview or data inspector where you can choose to only show the tabular information of selected features. Simple functionality, always useful.
I would like to propose an enhancement to FME Flow regarding administrative security.Although administrators are already authenticated when logged into the system, certain critical actions pose a significantly higher risk and impact. These include, for example: Creating or restoring backups Connecting or modifying Authentication Services Adding or deleting users Changing security-related configurations Other high-impact administrative operations To increase security and reduce the risk of unintended or malicious changes (e.g., in case of session hijacking, unattended sessions, or compromised credentials), I propose that FME Flow require administrators to re-enter their password before executing such critical actions.This additional verification step would: Strengthen security for sensitive operations Reduce the risk of accidental misconfiguration Align with best practices for secure administrative interfaces Provide an extra layer of protection without significantly impacting usability The re-authentication prompt should only appear for clearly defined high-risk actions to maintain a smooth user experience for routine administrative tasks.
FME can read AutoCAD Civil 3D, it would also be great if FME could write to AutoCAD Civil 3D as well.
Currently, FME can write geometry to Revit, but surfaces are typically created as Generic Models.I would like the Revit Writer to support creating native Revit elements from FME features, for example:FME wall → Revit Wall FME column → Revit Column FME beam → Revit Structural Framing FME roof → Revit RoofThe resulting objects should behave like normal Revit elements, including their correct category, type, parameters, scheduling, filtering, and Revit editing capabilities.This would make FME much more useful for converting GIS, CAD, IFC, point-cloud and other source data into correct BIM models, rather than geometry represented as Generic Models.
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.
