Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
When you delete a transformer, the connection to and from it are automatically joined. If you want to "disconnect" a transformer, you have to do that yourself (or delete and recreate).Wouldn't it be a simple feat to add a "Disconnect" option to the transformer context menu, releasing the transformer from its connections, which are automatically joined ? That would make moving transformers around in the workflow more easy and intuitive.
The "Recent workspaces" is a great shortcut, but when you want to open another non-recent, you're stuck with a standard Windows dialog.In the "FME Options" / "Default Paths" you can enter a list of "shared" folders. I think it would be a great idea to enhance the workspace file open dialog with shortcuts to these folders, including the standard "FME Workspaces" in Documents.It may be implemented as a Favorites list, but with the "official" shared folders added automatically.
Transformer Gallery is getting pretty huge now so efficient search is important. When I enter text in the search box in Transformer Gallery in FME Desktop a list of transformers is shown where text matches the name or description. Sometimes I might just want to search on the name and not the description. For example if I am trying to remember which transformer creates a geometry from number x, y attributes. I type "point" in the search, but I get 247 items returned which makes it hard to sift through. When searching I'd like to be able to target the search for Name, Description, Store or a combination of those. Just need some simple control like a drop down list or check boxes beside the search text box.
***Note from Migration:*** Original Title was: Attribute Validator - Populate _fme_validation_message (string) with a concatenated string of failure messages that appear in the list When a record fails more than one attribute test I think it would be a good idea if _fme_validation_message (string) contained a concatenated string of all the list element messages that have failed, not just the first one. Eg. At present you get this I think it would be more useful if _fme_validation_message (string) contained “Attribute 'DevelopmentAddress' fails check for Has a Value', Attribute 'ApplicantSurname' fails check for Has a Value” The reason I ask is that I wish to create an error report that details all the issues that have occurred to each record in one line of the report. I also want a string that I can easily search and count to identify records that failed, certain elements.The list elements are very useful and I certainly want to see these kept, but if the above is implemented it would save a lot of work which now has to go into producing a one line message from the resulting list.
FME can be specified on the reader reads all subfolders with **.eg. C:Data***.shp, C:Data***.csvBut sumetimes, I don't need to read all the files in subfolders.If I have the following folder structure. If i set CSV reader dataset to C:Data***.csv.Case 1I want to read csv files in the [a1],[a1],[b1],[b1], But I don't want to read files in the [other] folder. I hope to add a [Max Hierarchies to Read] parameters, control the maximum number of the subfolders hierarchies. In this case, this parameter can be set to 3 .Case 2I just want to read csv files in the specified hierarchy folder. eg.[a1*.csv],[a2*.csv].I hope to add a [Specific Hierarchy to Read] parameters, control the number of specific subfolders hierarchy. In this case, this parameter can be set to 2 .
In FME 2015, when altering the drawing style displayed there is a checkbox which you can untick to restore to the original values. This feature appears to be missing in 2016, once displays have been overwritten there is no way to restore.
Re this question: https://knowledge.safe.com/questions/33126/validateread-export-thousand-of-txt-to-csv-txt-are.htmlI'm thinking it would be pretty useful if lines in a CSV (or text file) could be skipped depending on a particular test; for example it begins with a line with a comment character like So, to that end I suggest adding the Tester transformer behaviour into the CSV parameters dialog, like this mockup:
It's not possible to select the "Format String" from Attributes.
I use FME Desktop on a Mac and so some preferences are a bit different than with windows. One feature I love is the newly added ability to split your screen and have two apps fill up the whole screen (clicking and holding on the "full screen" or green button of a window and then choosing a second app to put next to it). When you do this there are obviously a fair number of icons in the "ribbon" of FME that are hidden due to the constrained screen real estate. Two of the most important buttons are hidden when the window is this size - add Reader and add Writer.I was wondering if perhaps this ribbon/top menu could be editable/customizable? Perhaps you could give us the ability to rearrange the order of these buttons? At a minimum perhaps the add reader/writer could be moved to the left somewhere so that when you are using FME in a smaller window you could still see them?Thanks for the consideration....certainly not hugely impactful or pressing but more of a "nice to have" feature.
We often have to trace our way through large workbenches that have a lot of useful annotations. It would be great to be able to search these user/summary annotations. This would be really useful for workbenches with FMEServerJobSubmitters/WorkspaceRunners as the workbench names are in annotations and would then be easier to locate.As a workaround we have been renaming transformers to end with job names as an easy way to find them but it seems like more people use annotations to store this information.
Instead of adding proprietary, non-standard and platform-dependent format https://knowledge.safe.com/content/idea/18863/ms-word-writer.html I suggest to implement OpenDocument Read/Write support. The wiki page is https://en.wikipedia.org/wiki/OpenDocument This is the best choice. It is a) standardized b) openly licensed c) supported even by MS Office d) cross-platform Thanks,
It would be nice to be able to export permissions table/matrix from FME Server.
I recently had a project, where I developed a runner workspace using multiple WorkspaceRunners. The client then decided to implement the process using FME Server. I had to delete all WorkspaceRunners, add FMEServerJobSubmitters, and reset the parameters for each Job Submitter (Note: Each child workspace had parameters that had to be set to a user parameter within the runner workspace, so the default values set within the children workspaces were not applicable)If there was an option to convert a WorkspaceRunner (or group of WorkspaceRunners) to FMEServerJobSubmitters, with identical parameter values, that would be extremely helpful!Thank you!
To be able to copy the path name of the workspace from the start tab . Something similar to the second image below.
Currently I have to use 2 statements to handle it, one plain SELECT COUNT(*) AS NUMBER FROM TABLE WHERE CONDITION, and the second statement performs actual update/deletion. It would be useful if SQLExecutor is able to expose number of rows affected bu UPDATE, DELETE commands.
I mean the first row versus the field values.
At the risk of sounding like a fuddy duddy, after a few days of using FME 2016 I'm really missing the help panel! The new window is too slow to load, too distracting when it changes continually when you click on different transformers, and takes up too much window real estate when you leave it open. Please bring back the olde panel!
When using the xmlupdater, there's not a good way to see which of your updates actually worked. You always get xml out, but it's not immediately obvious how it has been changed. It would be nice if there were a way to have an output of each update that was performed on the xml, or a way of seeing which features that you send in successfully altered the xml or not. Or just an output per feature that has attributes that show the results of the parameters for that feature.
It would be handy to be able to test workspaces on FME Server environments with disabled output. The Writer Redirect Parameter can not be published.
Would it be possible to implement a second type of custom transformer (CT) where the creator can state that all attributes created inside the custom transformer are local and therefore will not be added to the feature entering the CT. In the output port(s), those attributes that are the result of the analysis will be visible. In the parent workspace, the user that uses this CT can than be allowed to catch the values returned by the custom transformer ('the function') and store it in attributes with names that can be chosen by the user (or by typing or by value of an attribute). Implementing a custom transformer in this way, will allow us to completely differentiate between the feature that initiates the CT and the analysis done within the CT AND it will allow us to catch results in different attributenames without overwriting a possible existing attribute.Is it clear what I'm looking for?What do you think of this idea?
Instead of the short line and the teeny number on the right of the text box, maybe the text box itself will be occupied by the progress bar.
It would be great if the FME workbench could reveal the under lying code for Mapnik and let you adjust certain parameters through code as well as parameters. Or better still allow for a code box that can render images through mapnik code. THere are also a number of other programming laungages that have very useful open sourced libraries that would be brilliant to utulize in FE.
I wondered why there is no CSV flattener, like JSON or XML flatteners. I had to process CSV in HTTPCaller's response ('_response_body').So I made my own with Python caller (which is not utf compatible).import csv, StringIO import fme import fmeobjects # Template Function interface: def processFeature(feature): pass # Template Class Interface: class FeatureProcessor(object): def __init__(self): pass def input(self,feature): stringinput = feature.getAttribute('_response_body').encode("ascii","ignore") reader = csv.DictReader(StringIO.StringIO(stringinput)) for line in reader: for field in reader.fieldnames: feature.setAttribute(field, line[field]) self.pyoutput(feature) def close(self): pass
It would be nice to have a Launch new instance option in File menu, which would leave current workspace intact.
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.
