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.
The AutodeskDocsConnector currently requires a file URN. This is contained within the URL used by ACC, but in encoded form. It would be helpful if you could also just paste the ACC URL directly into the connector and have FME do the parsing internally.
I love the HTTPCaller, SQLExecutor, and FeatureReader, but I have to admit I was confused how to make them work. It turned out I had to use a Creator transformer, which is not obvious. I'd prefer if they just worked without adding a Creator transformer.
User is trying to write out an explicit table https://support.microsoft.com/en-au/office/overview-of-excel-tables-7ab0bb7d-3a9e-4b56-a3c9-6c94334e492c rather than a block of data styled as a table. Currently the data writes out without issue but the table stays as a single row, not expanding to fit the data in the table.Similar to this community thread, and this idea.Currently, FME's Excel writing library does not have support for tables and we cannot modify them. Excel has marked out the table’s extents in the sheet and we are simply appending to the existing range. With enough interest we could add a new library to tackle this issue.
If one Point of the tunnel-connection is selected - you can see the connection line as a dashed line.But if you want to change the view to the other side of the tunnel, you have to navigate by your own.That's not fine for big workspaces. So a possibility to jump to the oher tunnelpoint in the view would be a nice feature :-)
For example, if you need to replace suffix {a, b, c} with {x, y, z}, you will have to use three StringReplacers with different regular expressions. In this example, the StringPairReplacer cannot be used since the source string contains a, b, c within the non-suffix part.sourcedestination1abcaabcx2abcbabcy3abccabczI think the StringReplacer has a room to improve to allow users to define one or more replacement rules. Probably the parameters setting for the above example looks like this.If the user defined two or more replacement rules, the transformer performs every replacement in the order from top to bottom.
In Autocad layer colors can be defined either by index or RGB.FME doesn't have a way of validating RGB layer colors. It looks like FME is doing a best guess using the color index here, but unlike with objects we don't have something like autocad_layer_true_color where we can find the exact RGB values.
In many organizations, FME Flow is managed centrally and engine resources are shared across different teams or departments. However, FME Flow currently does not offer any permission control on engine queues.At the moment, when a user/author has access to view queues, they can see all queues defined on the FME Flow instance. This can be problematic in environments where engine usage needs to be compartmentalized. Example use caseThe IT department is allowed to use 2 specific engines/queues.The GIS team is allowed to use 3 different engines/queues.However, because queues are not permission-restricted, any user can select any queue when creating schedules, automations, or running workspaces if they have access to the advanced part. Suggested ImprovementAdd the ability to control which engine queues a user or role can see and use.This would allow administrators to:Restrict access to specific queues based on user roles or groups. Prevent users from unintentionally using engines they are not supposed to access. Improve resource isolation and governance in multi-team or multi-department FME Flow environments.
During workspace testing I often use a lot of different parameter values. When I have a certain version ready for deployment or a next iteration, I would like to (re)set all the parameter values at once. This could be to the parameter default values or clear all values.My suggestion is to add to the Navigator pane:User Parameters (root)Published Parameters (sub)Private Parameters (sub)FME Server Parameters (sub)right mouse click options:Set all parameter values to DefaultClear all parameter values
As discussed in this q&a, output from the FeatureWriter is not included in the Total Features Written stat at the end of a workspace log and thus also not included in the job results page on FME Server. This can be confusing and potentially misleading so I'd like to suggest adding these numbers to the total.
I’m trying to download files from a SharePoint environment using the SharepointOnlineConnector transformer in FME. After a certain period, we hit the timeout criteria, and SharePoint becomes unavailable/unreachable.According to Microsoft’s documentation, there is a Retry-After header option that can be used to introduce a delay after each API call:https://learn.microsoft.com/en-us/sharepoint/dev/embedded/development/limits-calling#patterns-and-best-practicesHowever, I cannot find this option among the parameters of the SharepointOnlineConnector transformer:https://docs.safe.com/fme/html/FME-Form-Documentation/FME-Transformers/Transformers/sharepointonlineconnector-pkg.htmQuestion:Is it possible to extend the transformer with a header clause where we can set the Retry-After parameter? Or is there an alternative way to implement this behavior in FME?
Currently, FME Flow Apps and Gallery Apps are either always enabled or always disabled. There are times when it would be useful for this to be managed in the app settings for example: If we need to restrict access to specific timeframes, such as during business hours. Having to manually enable and disable apps is frustrating. For apps with a defined start and end date for their availability, it would be much easier if we could automate them being switched on/off. It would be epic if we had a scheduling feature for FME Flow Apps that allows us to define periods of availability, similar to that for Schedules for Workspaces, where we can set when and how often an app is availableBeing able to configure an app to be automatically enabled or disabled based on a recurring schedule (e.g. weekdays from 8am to 6pm) Setting a specific start/end date and time after which the app becomes available/unavailable.
I’m interested in using FME Flow for Connection Storage in FME Workbench.We have a single FME Flow instance that does not have redundancy. I’m concerned that if Flow is unavailable, that FME Workbench will effectively also be rendered unusable if I use Flow for connection storage, based on what I’ve read in the documentation.Further, FME Form provides me a sort of redundancy at the moment - if Flow is unavailable or if the engines are consumed, I can run my processes locally, as a last resort. In my understanding, moving my connections to Flow would remove this redundancy and leave me more vulnerable to network/infrastructure/system issues.If the above is true, would it be possible to maintain a local cache of connections, similar to the default Personal Database Connection Storage, where it prompts for and perhaps even requires connection and syncing to Flow, but has some sort of fail-back mechanism in the event of failure?I could keep an export of connections locally, or a Shared Database copy, but this will go stale and defeats the purpose of the FME Flow option, I imagine.Thanks for any thoughts or corrections on the above.
Currently, we can only set the default layer color in the DWG Writer using a color index. Various CAD standards also work with layer colors based on RGB values. I would like to see this expanded so that it can be set using both color index and RGB values.This will avoid having to create templates with thousand of layers manually (extensive cad standard).
Often, I’m dealing with large amounts of spatial features, but only need the non-geometry attributes. Reading in a national dataset of small polygons must add a lot of time to the process. Reading it all in and then removing geometry is a small saving, but not much. Could we have a ‘no geoms’ option in Feature Reader/Reader?
I've been working with data virtualization for a few projects now. I like the possibilities, but I think it still needs some improvements to make it easier to use the functionality:There seems to be only one way of linking a data virtualization workspace to an endpoint. And it seems to be a 1:1 relation. I think it should be much more flexible which workspaces can be linked to an endpoint. You're really bound to one way of working. It would be great if you can just create a normal workspace in Form, add an endpoint from there, and link it to the virtualization API endpoint afterwards. When testing with feature caching enabled, it asks for the input json every time again. It is not obligatory to add this input (since it uses the cache), but I do not understand why you keep getting the screen. I would expect that it works the same as a parameter. As soon as it is set (and you don’t change it) it is kept in memory without showing the pop-up every time again. If I'm correct it is not possible to change the namespace of an API after creating it. This is no issue if you just started, but for maintenance in the future this is really something which should be possible.
I often filter duplicates immediately before counting via a StatisticsCalculator. This led me to think that a ‘count unique values’ setting in the StatisticsCalculator could save a preceding DuplicateFilter each time, so that’s the idea.
Similar to the Regex Editor, I’d like an interactive window for creating and fine-tuning JSON queries.Bonus points for a live view of the query output using cached attributes.
Currently, FME Flow supports database connections via JDBC, but authentication typically relies on static credentials such as username and password. In modern cloud environments like Azure, using Managed Identity is a best practice for secure, secretless authentication.This idea proposes adding support for Azure Managed Identity including System Assigned and User Assigned identities for JDBC connections to databases such as Azure SQL Database, Azure Synapse, and other services that support token-based authentication.Why is this important?Eliminate hardcoded credentials: Reduces security risks and simplifies credential management. Cloud-native security: Aligns with Azure best practices and enterprise compliance requirements. Automatic token refresh: Improves reliability and reduces operational overhead. Flexibility: Support for both System Assigned and User Assigned identities allows organizations to choose the right approach for their architecture.How it could work:FME Flow detects it is running in Azure and uses the assigned Managed Identity. When establishing a JDBC connection, FME Flow retrieves an OAuth 2.0 access token from the Azure Instance Metadata Service (IMDS). The token is injected into the JDBC connection string or passed as a driver property (depending on the database/JDBC driver). Configuration options in FME Flow to select: Authentication mode: Managed Identity Identity type: System Assigned or specify a User Assigned identity (via client ID) Use Case Example: An organization runs FME Flow on an Azure VM with a User Assigned Managed Identity that has access to multiple Azure SQL Databases. Instead of storing credentials in FME Flow, the system automatically retrieves tokens for secure, passwordless connections. Security NecessityStoring static credentials in FME Flow or any application introduces significant risks:Credentials can be leaked through logs, backups, or misconfigurations. Manual rotation of passwords is error-prone and often neglected. Compliance frameworks (ISO, SOC, GDPR) increasingly require secretless authentication methods.By leveraging Azure Managed Identity, FME Flow can achieve zero-secret architecture, reducing attack surfaces and aligning with modern security standards.
The Esri ArcGIS Connector hub package includes the ArcGISBranchVersionManager transformer which currently supports List, Post and Reconcile actions.This idea is to support querying version differences using the version management Differences API endpoint, including resultType and async parameter options.The use case is to find edits that are to be propagated to an external (to ArcGIS) system in an efficient delta transaction. Usually it will be the default version state at two moments that will be queried, as it is the default version that will be propagated to the external system.In the legacy traditional version reading scenario, an SDE reader could extract differences with a Baseline Historical Date and Time constraint, this idea is an equivalency issue for branch versioned data.
Sometimes you only realize after a while that you need some followup action after a writer. This results in deleting the writer and inserting all the necessary information into a new FeatureWriter.I think it would be helpful if you could convert a normal Reader or Writer to a FeatureReader/ FeatureWriter.
For my current use case - a workspace app - I do not want users to see either option highlighted in the attached image and only wish to allow them to drag/drop or upload from their own machine. I attempted to try multiple file paths and uncheck the ‘Allow URL Path’ option within Form’s user parameter manager, which had no effect on the URL/path option showing, and see no option to disable browsing resources which has been asked about in the past:For simple file uploads by users not needing to provide a URL or browse Flow resources, I think disabling both should be possible.
Would it be possible to get the feature merger to be able to merge 3 or more tables/data streams rather than two, in cases where the tables are joining on a single consistent attribute? Up to now I've just added in sequential feature mergers in situations like the one I have now, where I have 3 tables to merge together. Thinking possibly on the ridiculous side, but if somehow one ended up with 20 tables with a single consistent key to link them wouldn't it be great to just use one transformer.
I occasionally get timeouts or 503 errors from ArcGIS Online (AGOL) Feature service, if I instead would implement this using HttpCaller (and using the rest api) I have much more possibility to tune for increased resilience using featres such as editing timeouts, specify number of retries and even parallel processing.It would be great if we could specify these in the FeatureReader/Reader as well!
As of FME Desktop 2022.1.1.0 build 22623 I cannot see a way to change editing options or specify the ArcGIS Server folder (not the Portal folder) that a feature service is published to (on federated ArcGIS Enterprise 10.8.1). These would be good options to specify when publishing; I am aware that editing options can be changed in the Portal item's settings page but it would be good to set these up front if possible.
Hi,It would be great to have the possibility to enable those GDB functions in FME Form for a GDB writer.Attachments (automatic creation of the relation and the _ATTACH table) Global IDs Editor trackingThis tutorial is well made but way too long !https://support.safe.com/hc/en-us/articles/25407508005645-Writing-ArcGIS-Geodatabase-AttachmentsThank you!
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.
