Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
It would be nice if the ChangeDetector match all attributes could exclude unexposed workspace level attributes like multi_reader_id, multi_reader_full_id, multi_reader_keyword, multi_reader_type.As it is, I need to either use match selected attributes and select them all (not possible in dynamic scenarios) or expose the multi_ attributes prior to the ChangeDetector so that match all except can be used.
This question has been asked so many times and is ridiculously confusing and hard for something that should have been added ages ago. I have a table that has table or layer names that I want to process in FME. I should be able to Dynamic SQLExecutor or FeatureReader to read the list and add them in to form without having to know the schema ahead of time. The issue is the schema they read comes from the input table and not the features it reads. The attributes are returned so you can write them with a dynamic writer, you just can see or use them in form. It needs the ability to dynamically return a value as defined in the source table (for example the @layerID or allow a wildcard to return all fields) and the fme_feature_type, fme_basename and fme_dataset not from the initiator but from the dynamically read table/layers. In this case I have the layer/table name and the ID I want to expose in the initiator table there just doesn’t seem to be a way get the attributes to dynamically read from the imitator table or to just dynamically read all attributes back.fme_attributes should come from the feature it is reading not the initiator, same with the schema it should be the schema of the feature it is reading not the initiatorIt can read the list of tables in but cannot read the attribute I want dynamically. For example, when it reads TRAILSIGNS the attribute I want returned is TRAILSIGNID
It would be useful to allow a way to group related transformers together without having to use a bookmark. Bookmarks can take up too much space, or also the grouping might not be logical to put in a bookmark. Would be nice to just be able to select a group of transformers and make them ‘stick’ to each other, so if you need to move them again you don’t have to manually select the whole area they cover (and accidentally select other things you don’t want), all this can make working with FME more productive
I would like to propose a new feature for the Excel Writer in FME Form: the ability to automatically enable Excel’s built-in “Sort and Filter” functionality on the output file.This enhancement would allow users to generate Excel files where the column headers are immediately interactive, making it easier for end users to sort and filter data without additional formatting steps in Excel.Proposed Implementation:Add a checkbox option in the Excel Writer parameters (e.g., “Enable Excel Sort and Filter”). When enabled, the writer would apply Excel’s AutoFilter to the header row of the output sheet.Benefits:Improves usability of Excel outputs for non-technical stakeholders. Saves time by eliminating the need to manually apply filters in Excel. Enhances the presentation and interactivity of exported data.This small but impactful feature would streamline reporting workflows and improve the end-user experience.
FME24 provides an overly simplified and bland user interface and experience. Even as a long time FME user I find it difficult to use and even train new users. Personally, I’m yet to find a single benefit of the change.E.g. Simple icon colours which categorise items in the navigator (Purple = Parameters) are gone.Similar to being able to select dark mode, I think it would be extremely helpful to enable users to select the theme and icon styles that improve their user experience.
I am looking for a way to write to a self-created GeoPackage that contains multiple foreign keys and check constraints. To ensure the data loads correctly without ordering conflicts, I need to temporarily disable foreign key validation by executing:PRAGMA foreign_keys = OFF;Once all feature classes are written, I need to re-enable the checks.Currently, the GeoPackage writer lacks the option to execute SQL scripts before or after the translation process. Using a separate SQLExecutor is not a viable workaround because it operates in a different session; therefore, the pragma command does not affect the writer's connection.Interestingly, I can achieve the desired behavior using a SpatiaLite writer with a SQL statement on the same file, but this method fails to handle geometry correctly. Due to these limitations, I am considering switching from GeoPackage to SpatiaLite as a temporary measure, though this is not my preferred solution.Could you please add SQL before and SQL after parameters to the GeoPackage writer to support these types of database operations?
It would be really helpful in the “Search in Workspace” Function would include an option to also search through all populated Feature Caches in the Workspace.Related to this it would also be great if there were more search parameters like “whole word”/”match case”/”regular expression”.
I’d like to request a feature for the AttributeManager transformer (or all tables really) that allows users to export the hover table output (attribute actions table) directly to the clipboard. This would make it much easier to document, share, and review attribute configuration settings outside of FME, especially for workspace audits and reporting. Ideally, this could be enabled via a right-click menu or a dedicated export button.This would be very useful for the amount of documentation I have to do for all my Workspaces.
Hi,It would be a nice feature to add support for SLD files. They're XML files, so it ought to be fairly straight forward.Some sort of cross-format support to input/output styles handled by the various style transformers, so I could e.g. read an SLD at designate it to output as MapInfo styles directly, or e.g. output an SLD file based on MapInfo styles, would also be very neat. This is nice-to-have though, and may be a little more complicated.Note that there may be version issues to consider.If this can be achieved by packaging some templaters etc., that's great too.Cheers.
Please vote for this format if you think it should be in FME: https://www.geonovum.nl/uploads/documents/220405-JSON-FG.pdf https://docs.ogc.org/DRAFTS/21-045.html
Apache Parquet and it’s GeoParquet spinoff are increasingly used for data distribution and analytics, now the RaQuet format is emerging as an option for raster data. Vote here if you would like RaQuet supported in FME, and cite your use cases too.https://www.linkedin.com/pulse/raquet-raster-data-apache-parquet-javier-de-la-torre-chice/https://www.raquet.io/
The available system events is rather limited. Everything should be a system event! Here are several that I noticed are missing:Deployment Parameter published/created/updated/deleted Web Connection published/created/updated/deleted Resource published/created/updated/deleted Automation published/created/updated/deleted Schedule published/created/updated/deleted Stream published/created/updated/deleted Flow App published/created/updated/deleted Project created/updated/deleted
Add to the scheduling screen the ability to view schedules in a calendar view. It would be nice to be able to format it daily/weekly/work week/monthly. It would also be nice to be able to click on an opening in the calendar to start scheduling a new job.Merged Ideas:FME Server Schedule - Ability to identify the schedule(s) that gets executed on by atiul on August 8, 2018***Note from Migration:***Original Title was: FME Server Schedule - Ability to identify the schedule(s) that gets executed on a give time range (future date/time range)It would be great, if FME Server provides an interface that can list out the schedules that get executed during a give time range (future date/time range). This would be helpful to disable the affected schedule(s) during outages (server maintenance activities).
In FME Flow, Automations can be triggered by various FME Flow System Events, such as the creation or modification of repository items. This provides a powerful and flexible way to build event-driven workflows and governance mechanisms.However, currently these system events are primarily focused on repository-based entities. There is no equivalent event available for entities that exist outside of repositories.For example, the creation (or modification/deletion) of an FME Flow App does not trigger a corresponding FME Flow System Event. As a result, it is not possible to directly react to such changes using Automations.This limitation makes it difficult to: Implement governance or auditing processes for FME Flow Apps Automatically enforce naming conventions or security policies Trigger notifications when new public apps are created Maintain synchronization with external systems Track lifecycle events of non-repository entities
When bookmarks are closed, transformers inside the bookmark are not cached. While this is a great feature, I barely use it as closing and opening bookmark usually change the layout, and I really like to see the transformers and how many features go where. It would be nice to have a featurecaching enable / disable switch on bookmarks.
Just been trying to get a picture of the used connections in workspaces - This would be helpful. I can see it in the workspace file but the reader doesn’t include them.
Writers - Redirect to Inspectors - should also work on FeatureWriters
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!
It would be great to have a direct integration in FME Form to do git commits, etc. in the GUI itself. It could be in the form of a developer command line/powershell or even as a built-in git integration much like what we have with FME Flow. As it stands today, I do this indirectly through Visual Studio. I essentially save my .fmw files in a Visual Studio project, and do all the version control through there. I would love it if I could bypass that altogether.
The Tester and TestFilter transformers have five distinct Comparison Modes:Automatic Numeric Case Sensitive Case Insensitive Date/TimeAs well as the option to Specify Per Test.The FeatureJoiner and FeatureMerger transformers have three Comparison Modes:Automatic String (presumably the same as Case Sensitive, above, but I have not validated that and don’t see it specified in the documentation) NumericAnd the way that these transformers are designed, they are inherently “Per Test” or per “Join On” condition, as it were.The general Idea here is to make the Comparison Modes more consistent across transformers - there are likely other transformers that could be included in this, beyond the four mentioned above.Case Sensitive, Case Insensitive, and Date/Time could be useful in the Feature-type transformers, in addition to the Test-type transformers. There are other ways to achieve these, of course, but there may be value in having them readily available. The order in which Comparison Modes are listed could be consistent - this is a minor point.If the various types of Comparison Modes are already tailored to best match each class of transformer, then the idea may not have merit, but posing it in case others could see any value in the proposed change or a similar change.
Level up to the parquet format (updates and snapshot)
The current version of the AutodeskDocsConnector can download a specified source file. However this will not include any annotations or stamps added to PDF documents in ACC, which must be done through a dedicated export method. These annotations and stamps may contain critical information about the state of the PDF and its position in the lifecycle.It would be great if this package could implement the following two endpoints to allow PDF exports that include stamps and annotations:https://aps.autodesk.com/en/docs/acc/v1/reference/http/v1-files-export-pdf-files-POST/ https://aps.autodesk.com/en/docs/acc/v1/reference/http/v1-files-export-status-and-result-GET/
I would like to identify custom annotations attached to objects using WorkspaceReader. This is possible with summary annotation because the transformer name is included in the annotation attribute. Custom annotations take up less space than summary annotations and allow the author to document the workspace. Having the ability to export this information helps with cataloging and reporting.Can we have the transformer name or transformer ID included in the annotation feature type either in the annotation attribute like in summary annotation) or as a separate attribute?See the posthttps://community.safe.com/authoring-6/workspacereader-find-annotation-linked-to-transformers-37719?postid=164422#post164422
StringPairReplacer has been deprecated at FME 2025.2.However, there are use cases where StringPairReplacer would be farther convenient than StringReplacer.For instance, sometimes we have to replace multi-byte alpha-numeric characters with single-byte ones. In StringPairReplacer, it's easy to set replacement pairs, as in:Ａ A Ｂ B Ｃ C Ｄ D Ｅ E Ｆ F Ｇ G Ｈ H Ｉ I Ｊ J Ｋ K Ｌ L Ｍ M Ｎ N Ｏ O Ｐ P Ｑ Q Ｒ R Ｓ S Ｔ T Ｕ U Ｖ V Ｗ W Ｘ X Ｙ Y Ｚ Z ａ a ｂ b ｃ c ｄ d ｅ e ｆ f ｇ g ｈ h ｉ i ｊ j ｋ k ｌ l ｍ m ｎ n ｏ o ｐ p ｑ q ｒ r ｓ s ｔ t ｕ u ｖ v ｗ w ｘ x ｙ y ｚ z ０ 0 １ 1 ２ 2 ３ 3 ４ 4 ５ 5 ６ 6 ７ 7 ８ 8 ９ 9How can you perform the same replacement with StringReplacer? Not impossible but you will have to define 62 replace strings rows. Too tedious!I strongly hope StringPairReplacer will be back! [Addition] Alternatively, it would be great if StringReplacer would have "Replace String Pair" mode, in order to perform the pair replacement with this setting.Text to Replace: ０ １ ２ ３ ４ ５ ６ ７ ８ ９ こんにちは！ さようなら。Replacement Text: 0 1 2 3 4 5 6 7 8 9 Hello! "Good Bye."
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.
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.
