Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
***Note from Migration:*** Original Title was: Add a SQL Server Date format to @DateFormatter function and DateCalculator transformer Microsoft SQL Server (at least on 2012) only allows timestamps containing milliseconds (3 decimal places for fractional seconds) to be written to datetime and datetime2 columns. Dates generated by the @DateTimeNow() function automatically include nanoseconds (9 decimal places for fractional seconds). There is currently no way in the @DateTimeFormat function or DateCalculator transformer to only return milliseconds. Using either the "ISO" format shortcut, or using the %S flag always passes nanoseconds. One workaround I found was to wrap the @DateTimeNow() in a @Format() function like this: @DateTimeFormat(@Format(%.3f,@DateTimeNow()),ISO) to truncate the extra digits.I propose adding a "SQLServer" shortcut that returns the timestamp with only millisecond precision, and a flag of some sort that returns the seconds to millisecond precision.
Sometime a feature has an unacceptable set/combination of attributes, which means that the feature must be stopped from being output normally. If this is detected in AttributeManager, e.g. in a conditional value, there's no mechanism to block the feature. It has to be done using Testers before or after.If a "rejected" value could be set, and the action could be expanded to react on such a rejected value (or do it automatically) by either terminating the feature or outputting it via another port (e.g. <Rejected>), it would simplify the overall logic and minimize the clutter of transformers.Cheers
The FeatureReader provides an option to prefix _initiator_ attribute names when merging results. I would like an option to be able to prefix _result_ attribute names.
It can be cumbersome to write master/detail features using FME as you have to pay close attention to the order you write the features if there are foreign key constraints in the database. I propose giving the FeatureWriter a Group By option, where all the features in the same group (across all input ports) are written to the database inside a single transaction, when the output format allows it. It should also have the option "Input is ordered by group" to prevent the FeatureWriter from being blocking, whenever possible.This would solve the issue about writing master/detail features in a simple and intuitive way.
Ability to read and apply styler to a Bentley AecoSIM BXC file (format and styler). Currently can create 2D cells in dgn format from source (GIS) data however want capability to produce 3D format as well (compound cell). This way can establish one single data model from source data and output in 2D or 3D to use going forward. Also subsequent transformer to automate.
On a Mac, and only in FME 2019, if you right click and the mouse moves at all the first select of the dialog is picked. This is using a MagicMouse and I have gone through all forums (Mac and Safe) to see if there was some kind of fix. This was an issue before but appeared to have been fixed in 2018.1 but has now come back causing a lot of accidental cutting deleting inspecting. I have a VM on the same machine running in Windows and do not have the same issue.But congrats!!! The data inspector on cached data is BLAZING fast. ;)
Il would be nice to have a transformer that prevents any feature to pass before the rest of the workspace had run. It would behave as a disabled connection than becomes enabled once the rest of the workspace had run completely.
When FME server and license server are on the 1 x server machine, uninstalling FME server stops the license server. You have to manually start the license service again for desktop users
This post explains the issue in detail. Dates from FME Cloud are returned in UTC and you have to customize a workspace and associated functions to convert the time to the required zone. The handling of datetimes should be improved so the posted solutions (which I feel are a bit convoluted, especially the first one) are not required.
If merging datasets or use the StatisticsCalculator grouped by many attributes it would be great if there was an option on writers to remove empty attributes. Especcialy if the filename (or sheet name in Excel) is set by an attribute. In this cases ther can be many attributes in the written files that are empty.
I need to apply a merge cell to a series of cells in the excel writer. if the styler could do this that would be sufficient. It would be nice to be able to manually identify for instance O34:V34 and apply a value to that merged cell.ultimately if it could all the building of the cell range like O( _count+1):V(_count+1) so that it could always follow the data being written in the preceding rows.
Would be great to be about to output Dynamic blocks to AutoCAD, things like Visstate and Flip setting would be great, Distances for stretch, rotation and Alignment parameters might be a bit harder to achieve.
The AttributeValidator currently outputs the results in English. Since it is sometimes necessary to provide localized or custom messages, I suggest that the AttributeValidator include "message numbers" in addition to the full message, much like Oracle does with error messages (ORA-nnnn):Currently: Attribute 'abc' with value 'a' fails check for Type is 'INT'Suggested: Attribute 'abc' with value 'a' fails check for Type is 'INT' (FME-AV-1234)Where 1234 would be a unique integer that identifies the message.To translate, one could then search for FME-AV-nnnn rather than a specfic wording interspersed with attribute names etc.
Many times, I run into the following situation...I made an analisys, resulting in a raster-object... (DEM or whatever), and I want to nicely present this black-grey, one-band result.I can of course recalculate all cells to integers, use a RasterPalletteGenerator or calculate some RGB-values for each cell.. but that is cumbersome. To my experience in general raster transformers are less intuitive than vector ones...So I revert to QGIS giving me a nice drop-down menu with pallette options, color-ramps, breakpoints, classification and whatever to make my raster visually appealing and informative.Having something similar in FME would not only make my life easyer, but allow me to automate stuff on Server, and stream results as a nicely styled raster.Kind regards,Martin
***Note from Migration:*** Original Title was: Data Inspector: Changing Background map (or turning off) option to not reset view Using the 2020.2 data inspector is a joy. The recent improvements with the background maps are amazing!! Having the ability to background high res 2-4 cm imagery is a great QA tool for doing detailed heavy cad-gis with lots of schematic level detail. Not sure if this is already suggested elsewhere or a bug. When reviewing data zoomed in to building level, it would be great to be able to change the background map or turn background off without the data inspector resetting the view to full extent. I notice the Refresh view operation keeps the viewport the same so maybe this is a bug.Bonus items: have an option to keep or share the viewport between views (tabs) so that switching tabs would enable easy back and forth visual comparison.tie this "shared viewport" functionality into saving views and/or arranging views (tabs) as side-by-side panes would be a great tool for comparing datasets in different views with common and differences jumping out. NOTE: Im providing this feedback using DI in standalone mode (not within WB).I can provide some better use cases for saved/shared viewport with a bit more digging and experimenting within workbench; I suspect this may also lend itself to data management in general.Best, Reed
It would be helpful if FME could read my feature classes that contain an attribute with an attribute rule that uses an Arcade expression, and write it back out.
I would like to suggest that connection vertexes added by the "Insert Vertex on Connection" option move with with a bookmark. Currently, if a bookmark is moved, it will move the transformers, but the vertexes added by this function stay in their original location. It would be nice if they moved relative to the other connections and the transformers.
FME Server has a Access Permission per User and/or per Role, but FME Cloud not.It is possible to create/invite a different users with the the Roles either Admin or Member but both of them has access to all Instances listed in the Dashboard.This idea, of course is just an overview of the whole thing but here is implementation: Should be nice to be able to create this "Permissions" per User or per Role so we could (as an example) be able to create a token for that user and this one would be able to see/list only the Instances allowed/permitted for this user.
I frequently need to create multilevel XML. FME does a great job of creating one or two levels of XML. Unfortunately a lot of XML I need to create has at least 3 or 4 'sub' levels- or elements within elements, within elements with multiple attributes etc. The only work around I have is using multiple templaters and creating the inner elements first then using a 'key' attribute to join to the next upper element [in another templater]. This is sort of a daisy chain of nested XML until its finally assembled. However, it would be nice to do this all in one templater.Thank you.
***Note from Migration:*** Original Title was: Use a Slack Channel/Slack app to trigger FME Server translations/transformations The Idea would be drag and drop a file into a slack channel, somehow you pick a workspace/repository (slack apps?) this will trigger the workspace and then you can receive the results back in the same Slack Channel .
I remember that a past version of LineCombiner has "Process When Group Changes" (or "Input is Ordered") option.Hope the option will be revived in the next version.
It would be great if the AttributeFilter had a Case Insensitive mode similar to the Tester.I had a situation recently where I'm validating incoming data but occasionally they change the case of the data which isn't a problem generally but in order to make it work in FME Attribute Filter had to enter the different cases:I did get around this by using a TestFilter instead which has the case option functionality but is a lot more time consuming to setup:
With versioning enabled in an Amazon S3 bucket, I would like to use the S3Connector to retrieve the version ID of the latest upload and download the file of a specific version.
At the moment we run our FME server instance on Redhat version 7. We are currently in the process of upgrading all of our RHEL7 estate to RHEL8 but FME is causing us a few headaches. I could containerise it and leave it on RHEL7 but i wondered if there was any plans to support RHEL8 natively in the future?
Standard readers and writers allow for the individual feature types to be expanded to view the attributes but the FeatureWriter does not provide this option on the input ports.It can be very handy to be able to quickly visualise which attributes are correctly connected in the output schema.Please add the option to expand the FeatureWriter input ports to view attributes.The image below shows the same feature type as represented in the FeatureWriter and in the standard writer.
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.
