Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
In network settings, why not just have a tick box to read secuirty and proxy settings from a browser software
To be able to take the Coordinate System from one dataset and reproject another dataset accordingly it would be useful if you could use a variable to set the destination Coordinate System in the Reprojector transformer.This idea originates from this question: reproject-to-the-cs-of-other-data-layer-in-a-workspace
***Note from Migration:*** Original Title was: Inspecting data in AttributeFileWriter transformer and opening containing folder Would it be possible to add the "open Containing Folder" and "inspect" withthe AttributeFileWriter transformer when we right-click on the transformer.not sure if that is possible.
***Note from Migration:*** Original Title was: Allow ALL FMEServerJobSubmitter parameters to be fed by attributes and allowable exposing of those paramaters I would like to read a spreadsheet and dynamically feed things like Workspace Name, repository, Tags, Output Dataset ("As Specified in Workspace and Parameters" as an option/whats already been published to server), etc. into a FMEServerJobSubmitter. I don't want to set up a single jobsubmitter for every workbench I need run. This helps with looping failed jobs until successful among other things. Hidden parameters of the FME Server Job parameters that we need less hard-coded control of: #! <XFORM_PARM PARM_NAME="USERNAME" PARM_VALUE="me"/> #! <XFORM_PARM PARM_NAME="SERVER_PORT" PARM_VALUE="0"/> #! <XFORM_PARM PARM_NAME="PARAMETER_TYPES" PARM_VALUE="STRING,STRING,STRING,STRING,STRING"/> #! <XFORM_PARM PARM_NAME="SUBSECTION" PARM_VALUE="SERVER_JOB_SUBMITTER"/> #! <XFORM_PARM PARM_NAME="PRIORITY" PARM_VALUE="100"/> #! <XFORM_PARM PARM_NAME="BLOCKING" PARM_VALUE="No"/> #! <XFORM_PARM PARM_NAME="REPOSITORY" PARM_VALUE="Waste Management"/> #! <XFORM_PARM PARM_NAME="DATASET_OVERRIDE" PARM_VALUE="As Specified in Workspace and Parameters"/> #! <XFORM_PARM PARM_NAME="XFORMER_NAME" PARM_VALUE="Hand_block_number"/> #! <XFORM_PARM PARM_NAME="WORKSPACE_NAME" PARM_VALUE="Hand_block_number.fmw"/> #! <XFORM_PARM PARM_NAME="SERVER_NAME" PARM_VALUE="coevdfme1:8081"/> #! www.arcgis.com,SourceDataset_GEODATABASE_FILE, cepcad01 micrdata GIS Data Hand.gdb,DestDataset_ARCGISONLINEFEATURES, www.arcgis.com,DestDataset_ARCGISONLINEFEATURES_6, www.arcgis.com,DestDataset_ARCGISONLINEFEATURES_5, www.arcgis.com"/> #! <XFORM_PARM PARM_NAME="TM_TAG" PARM_VALUE=""/> #! <XFORM_PARM PARM_NAME="PASSWORD" PARM_VALUE="fme_decrypt(thanks for looking ;) )"/> Please please please let me be able to expose these attributes after submitting a job and then consume them in another Submitting bench :)
Hi,I've just spend hours to track down an error in a custom Workbench transformer calling a Python transformer.Both transformers were fine, but I finally tracked the error down to being the name I'd given the Workbench transformer which contained a dash (as in "...T-SQL..."). FME used that name indiscriminately to auto-generate the code to call the Python transformer, yielding a not very clear error message, caused by dashes not being allowed in variable names in Python.FME do already replace blanks with underscores when naming its own transformers, so why not extend this to do the same with dashes (and all other illegal Python variable name characters) ?
I recently wanted to use the maximum value of an attribute on one table as the start value of the counter on another table. To do this i have to calculate the value then use an attribute creator on each table and a feature merger to then calculate the new counter valueI would have been much neater and simpler if i could have passed the value to a parameter that the counter could use as the start value.
As stated in the documentation of the ListBuilder, Features output from this transformer have no geometry.Hundreds of times already I have used the FeatureMerger to re-insert the geometry. During the #fmedays, @ArneBruksch informed me you can also use 'GeometryExctracter' and then 'GeometryReplacer'.Anyway, it would be nice to have the possibility to keep the geometry automatically while building a list. Any other fans?
In FME 2015, sending an invalid encoded geometry to the geometryreplacer causes the whole workbench to fail. It would be better to have a rejected port that handles these and lets the other geometries be produced.
***Note from Migration:*** Original Title was: True horizontal scaling based on load. FME Server Cluster to enable deployment of 10's, 100's or 1000's of engines for short duration.
Keep track of what paths data has been read from/saved to and make these easy to go back to. Every time a file open or save dialog would be in play, an easy pulldown of previously used paths would be available.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.