Open ideas have been reviewed by our Product Management and are open for commenting and voting.
When reading data with the FeatureReader I often merge attributes as this is a more efficient alternative for using the FeatureMerger afterwards.In the FeatureReader you can choose for Prefix Initiator to prevent overwriting conflicting attributes. This is not added (yet) to the SQLExecutor. Would be nice addition.Current workaround is to use a BulkAttributeRenamer before the SQLExecutor.
We have a lot of people that only run FME files through a batch script, they do not need to edit/develop any new ones. It would be nice to have a "lite" type license for these folks that only need to run the data and not develop or create anything.
I can't tell you how many times I forget the exact syntax for "FME_SQL_DELIMITER ;" when I'm working with SQLCreator, SQLExecutor, the "SQL To Run Before/After Write" parameters, or anywhere else I enter SQL statements. I have to look it up every time.I propose a new "SQL Special Expressions" or similar group entry in the left-hand side of the SQL Text editor (see image)and the very first item on that new group entry would be "FME_SQL_DELIMITER". This would be similar to the Special Characters group entry in most attribute text editors (see image):There might be other handy SQL-related expressions that could go in this group entry.
A little birdie tells me a MicrosoftTeamsConnector is coming to Hub. Teams supports incoming webhooks that can deliver plain text, markdown text, or rich messaging using Adaptive Cards. My idea is to support constructing adaptive cards to support rich messaging into Teams.
With the current xslt-processor you can read simple xslt (1.0) and xml-files.The 'new' (exists already some years) xslt 2.0 fileformat can't be read.We would like an update for the xslt-processor which can read 2.0 fileformats and can output a *.fo-file.With this *.fo we can create a *.pdf-file with the fo-processor (apachi).
When constructing a calculated attribute in the Text Editor, it would be very useful to be able to debug the formula being entered by having a "preview" of the result of the formula.This feature is available in QGIS Field Calculator as per the attached image.
FME has an AutodeskA360Connector transformer. For BIM models Autodesk created BIM 360 Docs, similar to A360. For more information: https://www.autodesk.com/products/bim-360-docs/overview For a customer I request a AutodeskBIM360Connector transformer that allows conneting to BIM 360 Docs for uploading and downloading files.
As an FME User, I want the PostgreSQL writer to be able to write default values if I send an empty string/missing/blank value(s) to the writer. Currently, if you want to the database to write the default value, you have to use an SQLCreator or SQLExectutor (as per the workarounds provided on the linked threads below).This issue is currently being tracked as: FMEENGINE-8945Related Forum Threadshttps://knowledge.safe.com/questions/1703/serial-data-types-and-insert-into-postgresql.html https://knowledge.safe.com/questions/90068/postgis-writer-excluded-fields-with-defaults-still.html https://knowledge.safe.com/questions/85824/postgresql-writers-how-to-insert-only-in-specified.html
In Navigator ---> Transformers it would be great to have a list by transformer type, so that transformers could be shown. This is most relevant when the transformer names are changed and you want to find specific transformer types.
Hi folks,it would be useful to add support for AWS IRSA in AWS EKS environments - that we can annotate the serviceaccounts (for example: FME Engine) to get temporary aws credentials to access aws s3/sqs - in our environment we need to rotate aws iam user credentials every 90 days - with AWS IRSA solution we get new temporary aws credentials per default every 24 hours - this helps us a lot for managing sercurity related stuff in daily business...annotate kubernetes serviceaccount:apiVersion: v1kind: ServiceAccountmetadata: annotations: eks.amazonaws.com/role-arn: arn:aws:iam::123456789012:role/fme-engineafter startup the container get two new environment variables like: - name: AWS_ROLE_ARN value: arn:aws:iam::123456789012:role/fme-engine - name: AWS_WEB_IDENTITY_TOKEN_FILE value: /var/run/secrets/eks.amazonaws.com/serviceaccount/tokenin the aws sdk is a new credentails provider available sts:AssumeRoleWithWebIdentity, for exchanging the Kubernetes-Issued OIDC token for AWS role credentialshttps://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.htmlhttps://aws.amazon.com/blogs/opensource/introducing-fine-grained-iam-roles-service-accounts/we also opened an issue for helm-charts https://github.com/safesoftware/helm-charts/issues/64
Eager to do many jobs in FME Cloud, but Cloud has no support for Sketchup nor Real DWG, can this be fixed?
It's currently possible to manually trigger an Automation to run if the defined trigger event is a Schedule and if the workflow is currently running. (You need to select the Schedule item in the workflow and then click the Trigger button at the bottom of the parameters window.)It would be great if the option to trigger an Automation could be extended to all types of Automation trigger events so that they could be triggered from within the Automation interface, and so that the process could be made more consistent.For example, you can't currently trigger a topic subscription from within the Automations interface. For that you need to save the Automation and go to the Notifications page and fire the Topic from there. I haven't checked the directory watch and similar trigger events but suspect them to be the same, i.e. needing to perform an external action to trigger the event.Additionally, I've noticed that triggered automations do not get listed in the triggered jobs history until the automation job has completed. It would be good to see them listed as soon as the Automation is triggered (perhaps with an "Incomplete" Status and no finish datetime). Today I was testing firing a topic to trigger an automation and did not know it was working as the job wasn't showing up in the job history, so I inadvertently triggered multiple jobs...These ideas tie back to this question:https://knowledge.safe.com/questions/114447/testing-automations-in-fme-server.html?&childToView=114467#answer-114467Merged Ideas:On Demand Automation Option by robotix on March 31, 2020On Demand Automation Option-I don't want to stop, it go into the schedule, adjust it and restart it-I don't want to go to the job log and resubmit-No, I don't mean workspaces. I know you can do that.-Just right click Run Now..???-Actions: Run Now ???Thanks. Have a nice Day.
Topographic plans from surveyors that use the survey module of Civil3D typically contain lots of feature lines (and survey figure lines). It would be more efficient to read feature lines directly in FME. Together with its properties (from property sets). Reader support for Survey Figure Lines would also be nice.In 2021.0 release, a feature line that was used to build a corridor in the Civil3D DWG is read as an alignment, but no properties are found, neither with AttributeExposer. For an ordinary feature line (not linked to a corridor) nothing is read by FME.
Currently, the ArcGISOnlineConnector cannot download ESRI multipatches that are published as a Scene Service. The only way to download multipatches through the Connector, is by downloading them as Scene Packages (SLPKs). However, since SLPKs cannot be read with FME, this does not allow for further processing inside the workspace.
I would be nice to be able to create a user parameter by right clicking in the Parameter Name column, and select "Create User Parameter" from the dropdown dialog.Sometimes you build your workspace backwards, and want to create a User Parameter to assign a value to an existing attribute.
When using a SQLExecutor in a workflow, I want to overwrite an existing attribute on a feature. However, this also applies to the fme_feature_type which is now set to "SQLExecutor". Because of this, I have to store the original fme_feature_type in a temporary attribute and then reassign fme_feature_type after the SQLExecutor. It would be fantastic if there were an option to "Overwrite fme_feature_type" that was defaulted to false.
When using a ListElementCounter it would be nice to have an option to count elements with attribute values that are unique only.
Add Web Connection for OAuth2 authorization to gather Google Fit data. Link for scopes: https://developers.google.com/identity/protocols/oauth2/scopes#fitness
It would be very useful if the Schedules in the FME Cloud Management Console would have an option to compensate for Daylight Savings. As it is now, you have to manually edit your schedules twice a year, and if you have many instances it could be a lot of work. I am looking for a function like on my router (screenshot), where I manually can edit settings for Daylight Savings. We either really need this option or if you could abolish Daylight Savings... Your call, Safe :-)
Hi all,At my company we process a lot of measurement data with FME. The visual preview tool in the Desktop is really the best tool ever in development. But I am missing some features.Is it also possible to add dynamic charts in the visual preview? We can use the chart generator, but that one is too static. We always divert back to Python (plot.ly) or to Tableau Desktop for the troubleshooting. It would ease up the development if that would be possible.
Loving the new Parameter manager in 2021, but it seems we've lost some functionality in the definition of the Number parameter type.In 2021 we can set a range limit and choose whether to accept integers or floats. Prior to this we had the range limit and selected the number of decimal places allowed. I found this far more useful to limit the number of decimal places being entered to keep things simple for the user.For example if my workspace just expects a number like 5.1, I don't want the user to be able to enter 5.12345684935153. It is pointless and means FME has more work to do to render the parameter value to be as expected.While the drop-down choice between integer and float is quick and easy, is would be handy if when float is selected, a further parameter is activated to set the number of decimal places.
No description is available.
***Note from Migration:*** Original Title was: Histogram view for better classification and analysis (AttributeFilter, AttributeRangeFilter, Inspecor) Including an histogram view (number of features with attributes value, regression curve, mean, natural breaks...) to those transformers or the inspector would help to define ranges for numeric data and check data quality for categorized data. Most people need to load the data with qgis or arcgis to do it and it is a waste of time. This should really useful associated with feature caching mode.related ideas :https://community.safe.com/s/idea/0874Q000000TlJHQA0/detailhttps://community.safe.com/s/idea/0874Q000000Tl6SQAS/detail
***Note from Migration:*** Original Title was: Allow Geometry Type Multipatch to Esri ArcGIS Online (AGOL) Feature Service Writer Would it be possible to enable Esri ArcGIS Online (AGOL) Feature Service Writer with the option to write Multipatch features to ArcGIS Online?Currently these are the geometry types allowed: arcgisonline_pointarcgisonline_multipointarcgisonline_polylinearcgisonline_polygonarcgisonline_no_geom
What would really help with authoring high-performance workspaces, is to change a reader or writer into respectively a FeatureReader or FeatureWriter. This allows more versatility to switch from "dumb" (=traditional) reading and writing to "smart" reading and writing (more easily do actions after writing, or read in batches). This idea would lower the barrier for authors to transition to more advanced ways to read and write data.
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.
