Open ideas have been reviewed by our Product Management and are open for commenting and voting.
***Note from Migration:*** Original Title was: Ability to Set Attribute Order in AttributeExposer: Alphabetical vs. Default Order via Import It would be nice if the AttributeExposer could honor the sort order of attributes if they are imported via a CSV or other type of source. Currently the AttributeExposer defaults to put them in alphabetical order vs. honoring the order they we were listed in the CSV. Alternatively, if the CSV contains a separate attribute for 'sort order' could the AttributeExposer transformer use that to maintain the sort order? Maybe give the users a choice: Maintain Existing Order or Alphabetical? Manually moving attributes in AttributeManager or in the Writer seems like something a transformer should be able to do.
I recently received several .numbers files with data that I want to relate to points on a map using FME. I had to ask the sender to export them from her Mac as Excel or CSV. Fortunately, she was willing and able. This is the first time that I have received .numbers files, so I don't know if this is a larger problem for the community. For the current project, I anticipate receiving more data in this format.This from the web: "You can only open NUMBERS files with Apple Numbers in macOS and iOS. You can also upload NUMBERS files to the iCloud version of Numbers in your web browser (requires an Apple ID). This is helpful for Windows users who don't have access to the Mac or iOS versions of Numbers. In the iCloud application you can view, edit, save, and download NUMBERS files."
We need an Active Directory connection with group managed service account (gMSA).We can only use gMSA (for the "search account") to connect to the AD. Right now, FME Server supports only regular accounts. So, i cannot use our AD.That's the interesting point for me. Please support the gMSA in FME Server :-)
Include an option to control what is added to the Windows Context Menu (right click on file/Workspace). With multiple versions the list can get quite large - and I never use Quick Translator. OK I could edit the registry but would prefer something less extreme.
When using FME Desktop, the "Run" button is always enabled, allowing a user to potentially run a workspace at any time, and therefore overwrite data at any time. While the "Redirect to FME Data Inspector" option is available for Writers in a workspace, that does not disable all transformers, including Executors and FeatureWriters.This idea is proposing a "Disable Run" option for the entire workspace, allowing a user to toggle on/off the ability to run a workspace. An additional functionality is to allow an author to "Lock" the "Disable Run", therefore if the workspace is opened by a colleague (or other unauthorized user) the workspace will not run unless the enabled.
Integration frameworks like Make, Power Automate & Tray support the creation of webhooks when connecting to Online hosted feature services, FME should too, including managing them (events, frequency, payload URL etc). This should come to Portal too when it gets webhooks.
It would be nice to have a panel with an overview of the existing FME Server apps in the main FME Server window. It's definitely one of the most used functionalities.
Hi,Are you planning to support IBM Notes? I actually don't understand much what this is, I've just got this question from a customer.Thanks a lot!
The current writer for JPG exports a WLD file. It would be useful to have it be an option to export JPW files.
Its would be great to be able to create world file for Jpeg2000 (.j2w) and for the ECW (.eww)
Many times, I have a workflow that reads multiple tables from one database, performs a few simple tasks to each one individually, and writes to another database. If there are 10 tables, it completes one before moving on to the next. This can add up to long processing times in the end. However, if I split that job up into 10 separate workbenches and run them concurrently on FME Server, the total processing is drastically reduced since they are run in parallel. Unfortunately, that method creates a data management nightmare. My suggestion is to allow parallel reads and writes within one workbench (when those reads/writes don't depend on the other reads/writes in the same workbench).Obviously this wouldn't apply if there are table joins or any transformers that hold features.Example: The screenshot below is a job that takes nearly 24 hours to run due to large amounts of data. However, no single table takes more than a few hours. But since FME runs in "serial" mode, all those hours are added together in the end.
This thread outlines it pretty well:https://community.safe.com/s/question/0D54Q00009QoujHSAR/best-way-to-remove-fractional-seconds-in-date-timeCurrently if you want to drop the fractional component of seconds you need to do extra steps. This is fine, however, it feels like it would be neater it the DateTimeConverter/DateTimeFormat function could handle this. Just a nice to have really.
Hi everyone.I was wondering if there ever was the idea of an "Tester" within all Transformers (such a the "group-by" is in almost every Transformer now).I couldnt find the idea yet and didnt see that this feature will be added in 2022.Is there any reason not to implementt?Not sure about increase of performance, but for overview and reduction of Transformers. Might be only makeup but i have around 60 Testers in one of my workspaces and i thought it might be a not too difficult to implement.I guess the necessity hasnt been too big yet, but i feel there will be more and more workspaces on fmeserver/fmecloud where the users can choose parameters which have different impact within the workspace.Would be glad to see this or to read if/why not to see.Cheers
What happens on FME Server 2017 and later versions (Linux) - when FME_TEMP is out of free space during translation, FME Engines are just crashing with "ResourceManager: Optimizing Memory Usage. Please wait..." message. The message is quite confusing and we had to dug many days about the cause. I propose to change message so the user know exactly what happened: "FME TEMP is out of space, please reserve more free space in temporary directory" or something similar.BTW - Shouldn't the memory to FME_TEMP be dumped in a clever way to use only what's available and not crash?
A visual compare and diff between two workspaces. Which transformers, readers and writers are added changed or deleted. Compare two workspaces and tell the differences in color.Merged Ideas:Visually compare two workspaces (Duplicate of this idea) by stalknecht on August 22, 2017A visual compare and diff between two workspaces. Which transformers, readers and writers are added changed or deleted. Compare two workspaces and tell the differences in color.Identify Differences Between Two Versions of Same Workspace by mark_f on November 6, 2015Currently difficult to compare two versions of the same Workspace. You can use a standard diff tool on the FMW files but there are often too many minor changes in the file to identify the real differences.FME workspace compare tool by ynaphade on January 25, 2016After seeing the demo of workbench reader, I was thinking we may need some tool to compare 2 versions of FME workbench to see what changes developer has done. we can do text compare but if developer just moved the transformer there is more noise and facts.
Fonts like Fira Code (open source) make source code more readable by representing common character combinations with unified symbols. For example, == looks like a double-wide equals, -> looks like an arrow, >= looks like a standard mathematical greater-than-or-equal symbol. I already have support for fonts like this in my JetBrains editors, but it would be nice to also have it in the PythonCreator, PythonCaller, RCaller, and TclCaller transformers, as well as the scripted user parameter editor.
When transfering FullName to the Username in a Windows Active directory, FME server uses the "User logon name (pre-Windows 2000)" which has a 20 characters limitation. This has the effect of truncating the FullName which can cause problems when making API calls to the Username. It would be helpful to be able to configure FME server so that it uses "User Logon Name" instead of "User Logon Name pre-Windows 2000" to help with that character limitation problem.
***Note from Migration:*** Original Title was: Autocad DWD/DXF Parameters allow Read ALL Paper Spaces beside of manually choosen ones When I read several DWG's, I don't know the names of all the Paper Spaces that may be there.I want to filter the viewports, or reading the Model Space Entities through viewports with Name starting with....When I read in all DWG's only with all Paper Spaces and without Model Space, then I can read in the right Paper Spaces with a second feature Reader.
The Group By option on transformers with several input ports is usually used with attributes which occur on both/all input ports.Can there be an option in the attribute selection window to only show attribute names that both input ports have in common?For instance, on the clipper, both the Clipper and the Clippee should contain the attribute I want to group on. So it would be great if I could display attributes that are existing on both input ports.
Please consider adding bulk mode support to the PythonCaller.
Okay, I know it's irrelevant to most people here,But this is a small idea, which can enhance the user experience for a many people!In Hebrew, as in other languages, we read and write from right to left.When I publish a server app for our clients, the title of the parameter is to the left of the box that needs to be filled.It makes perfect sense if the parameter was also written in English, but for our customers, we prefer the local language,So it creates confusion in the eyes.If there was such an option to set where we want the title of our parameters, it would be great!Thank you!
When running the SurfaceDraper transformer on 3D polygons as the surface, a surface polygon may throw an "invalid third dimension" error/warning. The message, however, does not specify which feature caused the error. It should. For me, anyway, I work with very large datasets, and identifying the offending feature is nigh unto impossible. In fact, I have this problem at this moment, and no amount of geometry checking in either ArcGIS or FME has been able to identify the offending feature. Simply identifying the offending feature in the error message in the logfile would make all the difference.
As a Python developer, I would like to be able to import an FME Python API package/module from a Python module on a machine with FME Desktop/Server installed and call any transformer that is present in the gallery.This would be similar to Esri ArcGIS Desktop arcpy package exposing all the geoprocessing tools from ArcToolbox.This would let streamline integration of FME and Python ecosystem!
Hi.I just experienced FME crashing in a fairly limited translation. The problem was the feature caching.I used a HttpCaller to fetch a GeoTIFF into an attribute, tested it twice (for HTTP result code, and for it being an exception) before writing it to a file. I.e. the output from the HttpCaller is cached by 4 different transformers.The problem is, that the GeoTIFF in question was 1.5 Gb in size, and I had 6 feature instances with this attribute. I.e. that FME needed to cache approximately 36 Gb in memory. This made it crash off course. Running without feature caching solved the problem.Howeever, the 4 times cached value for each feature is really unneccessary, since it is the exact same attribute value for each feature.My suggestion is:- to only cache such very large feature attributes once, and just link to it in each transformer cache ?- alternatively, and maybe simpler, enable turning off feature caching on individual transformers ?Cheers
Such feature will help us to audit and code-review FME workspaces.
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.
