Open ideas have been reviewed by our Product Management and are open for commenting and voting.
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 😊
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?
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.
Support readers/writers for Bentley's Open Roads, as many transportation agencies are using 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
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.
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.
Reading a OGC API - Features (WFS 3.0) currently always returns data in WGS84 no matter what storage coordinate systems are available.It would be nice if you could choose to return data in the default storage coordinate system. Or failing that, the crs parameter should be available in the collection query parameter drop down
White Box Tools is an open source geoprocessing package made by the University of Guelph.Its key benefit is its extreme speed, being able to process tools between 5 and 50 times faster than ArcGIS Pro. It would extremely beneficial if FME included an WBT transformer which could allow users to pass FME data to WBT and allow the user to select which WBT to run (there are hundreds). This would greatly expand the raster capabilities of FME, and include some functionality which is currently lacking in FME (viewshed)Whitebox Geospatial
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.
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
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
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.