Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Currently the VariableSetter/Retriever can be used to set/retrieve just one global variable. It would be more convenient if multiple variables could be set/retrieved at once.
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
Allow the XMLUpdater to accept some sort of table (ex. text file, or .csv) as input for the ‘Updates’ parameter. Currently, the ‘Updates’ section must be entered manually. There is no way to import rows in bulk.I am currently working on a workbench to update file geodatabase metadata. The default format has well over 100 metadata fields! Usually, for a task like this I’d make an input table Parameters and feed that in to the tool - in this case it would be for the parameters in the Updates section: Update Type, XML Path, Value Type, and Value.I did a search through this forum for ‘XMLUpdater’, and found many results related to updating metadata of one kind or another. It seems to be that this improvement would be helpful for anyone looking to update metadata or complex (but well structured) XML.I suppose another option would be to allow ‘Create User Parameter’ from the ‘Updates’ parameter. Then the user could select a file to input, or even copy paste into a text editor formatted commands for this parameter.For now my current solution will be manually keying in my most critical top ten or so updates - but it would be simpler and less work to pull in all from a list in bulk.Thanks for considering this improvement!
A function to enable|disable the Startup|Shutdown Python Script at once would be desirable.It is always very expensive if you have to comment out all lines just jor testing
DescriptionWhen managing a long list of Workspace and Automation Apps in FME Flow (under Flow Apps > Links), reordering them using the current up/down arrows is painful.If you have 15–20 apps and want to move a new item from the bottom to the top, you have to click the "Up" arrow 15 to 20 times.Suggested Enhancements: Column Sorting: Allow us to click column headers (Label, Link, Type) to instantly sort alphabetically or by type. That way, we can organize the entire gallery in one go instead of moving items one by one. Drag-and-Drop Handle: Replace or supplement the up/down arrows in the "REORDER" column with a drag handle (like ⋮⋮) so we can easily grab an app and drop it exactly where we want it. Adding these would make customizing Flow App galleries so much faster and save admins a lot of repetitive clicking.
I'm frequently asked if it's possible to setup FME Desktop with some default configuration e.g. Proxies, Shared folders, database connection file locations, window layout, transformer versions turned on, number of recent workspaces set to 10 etc... and then save that off as a config file that can be deployed to other installations of FME Desktop in an organisation. Currently the closest option to this is a silent install, or packaging FME, but that's much more of an admin overhead.It feels like with 2019's ability to save presets in Transformers we're going in the right direction, so here's a suggestion along the same theme that will help organisations with more than a couple of installations of FME Desktop.
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, The JSONExtractor requires manually setting the Target Attribute and JSON Query. It would be really nice if there was an Import option similar to AttributeManager. I often have the attribute names stored earlier in the workbench as I passed them to an API call to get the data. After fragmenting the response, the JSON to get each attribute is json[0], json[1] etc up to the last attribute. So it’s quite easy to create the attribute/JSON combinations that I want in the JSONExtractor. Import from Feature Cache would greatly speed up adding the JSONExtractor settings. It would also be fairly straightforward (although not quite as convenient) to save the settings in an import file and use Import from Dataset.
The GeometryReplacer should have a parameter to optionally set the coordinate system (preferably allowing attributes) instead of requiring a CoordinateSystemSetter
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.
Is there a way to add the option to filter by selection? I know there are other ways to filter but i think when you sort and select values of interest, being able to filter out the selected or unselected values would save a bunch of time.
When creating a table using a FeatureWriter—particularly for databases—it would be beneficial to be able to add comments associated with column names right at the time of creation.This allows the database to be documented using FME scripts from the moment it is created. It is much easier to document a database during its creation than after the fact. Since many tables are created via FME scripts, documenting them at that stage would be a significant advantage.
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.
It has been a while since we have DWG Autocad Civil3D Reader that can pick up Property Sets created in Autodesk native software as FME attributes. However, it has been quite a few cases where DWG deliverables or even templates need to be custom built to meet project requirements.Having access to both FME and Autodesk ecosystems it is kinda possible to bridge the gap (real hassle) to achieve the above-mentioned task, however it would be awesome if this would be possible only in FME.Suggestion:Convert attributes established in FME to DWG Property Set schema which could be easily manipulated in workspace. Property Sets include common data types, which could also be included in attribute/schema definition, where list manipulation with basic database operations would be heaven.
FME can read AutoCAD Civil 3D, it would also be great if FME could write to AutoCAD Civil 3D as well.
Flow Apps are one of the most useful things in Flow. Most organisations have a process they could expose this way, but is often blocked by how the app looks.At the moment you can change a banner, a logo and a footer with some rudimentary colour changes. That is fine internally, but It is not enough when the app is going in front of customers or the public.What would help:Reusable theme definitions covering colours, fonts, logo, favicon and tab title, set once and applied to many apps Control over form layout, including collapsible sections, tabs or steps, and space for instructions or notices between parameters A documented embed mode so an app can be dropped into an existing site or intranet Custom success and failure pages, with the option to redirect on completion
For automations Azure Event Grid Topic (notify) is an external trigger option.It would be good to allow parameters to be set with deployment parameters to allow a more agnostic approach between environments.Event grid end point Event grid topic key
When using the Workspace compare tool it would be useful to be able to export the diffs. This could be used for recording change between versions for audit purposes.Extending the idea this history could be stored and viewed in Form or Flow as metadata.The format could be CSV or JSON as a suggestion?
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.
Currently, using a FME floating licence requires each individual organisation to set up a dedicated licence server : https://docs.safe.com/fme/html/FME-Form-Documentation/FME-Form-Admin-Guide/FMEInstallation/About_Floating_Licenses.htmThe setup of such a licence server is, per se, not very complicated, but frequently involves discussions / challenges wrt setup of a dedicated VM / re-use of an existing VM, security on the opening of ports, etc.., which also often require the involvement of a tech profile (e.g. system administrator).Wouldn’t it be easier to have a global licence server hosted on the cloud, and managed directly by Safe, which could be accessed without any specific tech challenges by all individual FME instances ?If some organisations still prefer to have an internal licence server, it could also be interesting to allow both options : a licence server managed by the organisation itself or the global Safe licence server.
My idea is to update the ArcSDE reader so that you can read from a versioned database. Currently the only way you can do this is by using an SQL executer, it would be nice if there was something built into the ArcSDE reader so that the version of a database you were reading from was dynamic.
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
Provide a connector to interface with Cube’s .NET format. A .NET file contains a travel network and when using Cube’s export tool, it creates a NODE shapefile and a LINK shapefiles. If FME has a way to conceptualize a full graph with link attributes and node attributes all in one file, so much the better.
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.
