FME Form

Hi, I want to calculate a new attribute using the attributecreator with Text Editor:  But I my results are always the source values:What is my mistake?Thank you for your support! 

Hi all, When sending a test request with a HTTPCaller, the Test Response Preview shows the response. When you close this window and reopen it later after closing and re-opening the workspace (even on another date) this response is still there (cached?). Depending on the URL used, this can lead to an unreasonably large workspace file. Is this an intended feature, or an oversight that can slow down workspace performance if a user isn’t aware of this?If there is a benefit to being able to revisit this test response at a later date, maybe it’s a good idea to be able to enable/disable this feature entirely. Or at least be able to ‘clear’ this Test Response Preview. Kind regards, Rob de Groot An example URL that leads to a +20MB size increase of your workspace if a test response preview is opened:https://services1.arcgis.com/ug8NBKcLHVNmdmdt/arcgis/rest/services/Peilvakken/FeatureServer/0/query?where=1%3D1&outFields=*&outSR=4326&f=jsonIf you do this for multiple HTTPCallers it ca

Hi everyone!Today I’d like to share a new approach to building reports in FME, along with an entire family of custom transformers I’ve created to support it. Why I built BRGI’m a long-time fan of the HTMLReportGenerator. It lets me craft reports quickly, and I love the versatility of HTML compared with, say, PDF. I even demo it in every Intro to FME course as a great example of “let FME handle the code.”But as much as I love it, I’ve always hit three pain points:1. Plain styling – it could really use a dash of CSS/Bootstrap.2. Hard-coded content types – adding a new chart or HTML element isn’t trivial.3. Cumbersome feature ordering – managing Sorters and AttributeCreators just to control layout can get messy.Earlier this year I had to build a highly procedural report with lots of HTMLLayouters, AttributeCreators, and Sorters, and the workspace quickly turned into spaghetti. That’s when I thought: I already improved SystemCaller with BetterSystemCaller… why not do the same for report ge

I have a workspace that works without issues in FME 2024.2.1. We are planning to upgrade to FME 2025, but I am facing issues. When riunning the workspace in FME 2025, it seems to work fine, but after a while I get lots of a recurring message like this one:2025-06-02 11:38:25| 119.2|  0.2|ERROR |FFS reader: Failed to open file 'D:\FMETemp\wbrun_1748852462857_30000\fmetmp_0\FMETable_1748853274266_18156\FTShim_1019.fts' for reading.  Please ensure that the file exists and you have sufficient privileges to read itThese messages DO NOT appear when running the workspace in FME Form/Flow 2024.2.1I have tried FME Form/Flow 2025.0.2 and FME Form 2025.1 (beta) and all of these fails.I have set my FME_TMP environment variable to D:\FMETempDoes anyone have an idea?

I have created a very simple workspace with a creator which creates a line and writes it to a GeoPackage using a FeatureWriter.The line is 2D, no measures, but the geometry type in the resulting GeoPackage is reported by ogrinfo as “3D Measured Multi Curve”.I would expect the result to be a 2D LineString instead - or maybe just LineString. As seen in the image I have exported the geometry to WKT and it indeed reports it as “LINESTRING (400000 6040000,900000 6400000)”.Is this the expected behaviour and is the FeatureWriter geometry type detection headed towards the broadest category for data instead of a more narrow approach?The test has been done using FME Form 2026.2 (26333) on Windows.

Hi all,I'm trying to bring object detection capabilities into an FME workflow using YOLO models built with Ultralytics, and I'd love some guidance from anyone who's tackled this before.What I'm trying to do:Run inference with a trained Ultralytics YOLO model (e.g., detection, segmentation, or OBB) inside an FME workspace   Data (e.g., from PythonCaller ) into the model and get bounding boxes / masks / class labels back as FME features Ideally write the results back out as vector features (polygons/points) with attributes for class, confidence score, etc.Specific questions:Has anyone integrated Ultralytics' Python package (pip install ultralytics) directly via FME's PythonCaller transformer? Any gotchas with FME's bundled Python environment vs. installing ultralytics and its dependencies (torch, etc.)? Is it better to run YOLO inference as an external subprocess/script call from FME, or embed the from ultralytics import YOLO calls directly inside a PythonCaller?Sample datasets/models fo

I have successfully created a Asana app for connecting to FME (giving me a Client ID and secret) and then established the connection as a web connection in FME Form, but when I try to use the AsanaTaskQuerier transformer and input the required parameters (Web Connection, Asana Project ID, and Query Type) the Asana Project ID gives me an error, “Arithmetic expression invalid”. I followed the help documentation for the custom transformer and it seems straight forward enough, but no matter which Project ID link I copy and paste into the field, it gives the same error and won't let me click OK to run the transformer. I have successfully tested the connection and know that works, the issue seems to be in the Asana Project ID, possibly because it seems to have to be an Arithmetic field? The FME Help documentation for this says to input the Asana Project ID as follows, which I have done so in the same format. Does anyone have a solution to what the issue is or if you have come across this iss

I am using the same workflow that I used in my older version of FME workbench. When I update the FME workbench to 2026.2 I was started getting error in Line Builder. I have number of points that create a polygon. All the points are already sorted. Can anyone let me know is this the bug or something wrong. You can see in the screen shot like waylineid is common and wayjsonindex. if there are 96 features then there will be 96 way_json_index.Thank you in advance!​@j.botterill ​@david_r ​@rylanatsafe  

FME Desktop 2022.1 crashes when trying to read Esri File Geodatabase - Reader works fine with any other format including Arc SDEs but crashes when setting format to File Geodatabase and trying to browse local drive

Hi there,I am importing connections from an older deployment of FME Flow into Form, in order to publish to a new FME Flow. When I do so their names are locked to whatever they were named before.  These names do not confirm to our new naming convention.  It would be helpful to be able to rename Web and DB connections in Form. I understand this would possibly break workspaces referencing this, but this is a risk I am willing to take.

Hi,Is there any way to optimize the FME Inspector?In my case, I'm opening a DWG containing approximately 600,000 features, and it takes nearly 7 minutes to open.It appears that the Inspector indexes all attribute columns when the dataset is loaded. In some cases, I don't think this is necessary, especially when working with very large datasets.It would be great to have an option to disable attribute indexing for large datasets, or even better, allow users to select which attributes should be indexed when needed. I believe this could significantly improve loading performance for large files.Is there already an option to control this behavior, or would this be a good feature request?Thanks!

I am reading many jxl files. Each jxl has a "CoordinateSystemRecord". 1 for each file. howver this is not a standardized CS as recognized by fme.It has an attribute for ZoneName which is a text value like "New Mexico East 3001" and a SystemName attribute like "US State Plane 1983". How can I use these to set the coordinate system value as the file is read?i currently have the coordinatesystemextractor transformer in my wb. but the value is empty. 

We have a hosted feature layer that we update via FME on a schedule. It worked fine until we made a view layer of the hosted feature layer. Now we get an HTTP Error Code: 400 saying 'Cannot remove Layer 0 from <layer name>. Layer 0 is referenced by view service <layer name view>.'  In the writer we’re using Feature Operation: Insert and Feature Handling: Use Existing. We’ve also tried changing this to Truncate Existing which still didn’t work. What is the correct workflow for updating a hosted feature service if the feature service has view layers? 

Hi everyone,After upgrading our FME Flow instance from 2025.2 to 2026.2, a workspace parameter with dynamic values stopped working in a Workspace App.When opening the app, FME Flow shows the following error when testing the dynamic parameters:Loading from WorkspaceKartenautomatisierungen/Kartenautomatisierung_ZUBA_PreScript_2.fmwError loading schemaUnable to generate dynamic parameters from source file.Error was:E:\appdata\fme\systemshare\resources\system\null\null\FeatureWriter\ZUBA.jsonPlease ensure the file exists and is readable. A few observations:The same setup worked without issues in FME Flow 2025.2. The workspace itself executes successfully. It loads the JSON after the workspace is done.  The error only occurs while loading the dynamic workspace parameter. The path contains system\null\null\FeatureWriter\ZUBA.json, and the corresponding folders do not exist. I never configured FME to write schema files to that location.Has anyone seen a similar issue after upgrading to 2026.2

Hi,I have a dynamic feuture writer which writes tables from my PostGreSQL/PostGIS database to a geopackage. Some of the source tables are with no geometry and some are with. This is why I have two readers, one for Posgresql and one for PostGIS. I write all the tables dynamicly to the geopackage with a FeatureWriter and have set the geometry type to read from schema definition. In the resulting geopackage I see the table which should not have a geometry with a geom attribute with all null values. The table gpkg_contents has a data_type features instead of attributes. When I try the same with a manual definition it works fine.QGIS does not seem to have any problems with the geopackage that has the wrong definition, but ArcGIS Pro has. How can i get the dynamic writer to write correct to the geopackage? Or is this a bug or a works as designed? I run FME 2023, but also tried it with FME 2025.Thank you all

Hi team,I’ve noticed a bug within FME 2024.2.1 (Build 24801)… When I’m building out a workspace and reference a Password Deployment Parameter in a reader. If I edit that or any other Reader or Writer under the Navigator (i.e. Right Click, Update Reader, make changes and click OK), it will drop the Password Deployment Parameter, anywhere they are referenced.Text based Deployment parameters remain, but it just drops the Password based Deployment Parameters. Has anyone else seen this issue? Once they’re all set and we publish, it seems to retain them, but it’s only after we update the Reader and Feature Types.

In FME 2026.x, the way Double data types are identified seems to have changed. Decimal numbers are only recognized as double when using a period ('.') as the separator, whereas a comma (',') is not. This is quite unusual, unlike previous versions which worked perfectly fine with commas.I believe the identification method in previous versions was more efficient. For large workspaces, it could save us from using additional Transformers to convert commas to periods. Moreover, since input data formats in different regions still use commas as decimal separators, keeping the old identification logic would be much more flexible.  

How can I check the extension on input files for FME appsFor example a file with a DWG extension Thank you for answer

I'd like to read a DGN file, which contains a terrain model. In version 2025.1.2 it is being read as igds_polygon_collection. The fme_Geometry is “fme_undifined” and the fme_type is “fme_no_geom”.When using a Civil 3D file, it can read a surface model, which is the same principle as the terrain model in a DGN. The terrain model is created in OpenRoads.Or is another option available to read the terrain model directly from a DGN file without converting it to another fileformat or element type?  

In a process that deals with GPS messages that are received every 15 minutes, I have two User Parameters that set a Start- and an End date, in order to prevent having to process a couple of million rows from the database every time. These are configured as DateTime parameters, with the Datetime Format set to Date only.The GPS Fix time is copied to a new attribute while converting to a Date, using a DateTimeConvertor. Format selected is FME date (%Y%m%d). If I then use a Tester to check whether the GPS fix time falls between the start- and end date (with Comparison Mode set to Date/Time), they all fail, because the parameters value is 2026-01-01, while the attributes value is 20260101. So the Tester’s comparisonDate >= $(StartDate)(where Date is the by DateTimeConvertor created attribute) does not work anymore, since our upgrade to 2026.1.2. Before (when we used 2025.0.3) this was working without a problem. Upgrading the DateTimeConvertor and the Tester (this is an older workspace) d

I have a non-spatial Oracle table fifteen attribute columns, two of which columns store images.One column is called “image” and the other column is called “thumbnail”Both store images in jpeg format.All of the jpegs are less than 1MB in file sizeI want to write this table to PostGISI have constructed a table in PostGIS with the columns “image” and “thumbnail” both defined as bytea How do I write the workspace that Reads from Oracle and Writes to PostGIS? I made an attempt, but now FME fails to display the data from the PostGIS table, so there is something wrong. My version of FME Desktop isFME(R) 2022.1.3.0 (20220928 - Build 22630 - WIN64) 

Hi team,In my workbench, I'm snapping line endpoints to the device X,Y.To do this, I stored the point's X,Y in the line's attributes and used the VertexCreator transformer with "Replace point at vertex" set to −1 (the end point), passing in the device's X,Y.This moves the line's end point to the device's X,Y as expected, but it also changes the line's start point to what was previously the line's end point.To avoid this, I tried using VertexRemover to remove the end point, then VertexCreator with "Add point at vertex" set to −1, again passing in the device's X,Y. With this approach, the line's start and end points end up swapped.I need the start and end point order preserved as-is, since that order is used for terminal assignments in the Utility Network. Someone please suggest a solution for this? ​@redgeographics  ​@radek.cervenka  ​@hkingsbury 

Quick question.Are there alternatives to using AttributeManager to manually sort attributes by name?Sort of an AttributeSorterByName or AttributeSortedReexposer transformers ?Cheers.

I’m using FME Form 2026.2. I have date and time strings that I need to convert into a date field in ArcGIS Online. It seems like this should be easy, but I can’t get it to work. What format does ArcGIS require to create a date field.I create a new datetime attribute then write it to a AGOL Feature Service. The field is created in AGOL, but the value are null.@ParseDateTime(@Value(LocationDate) @Value(LocationTime), %m/%d/%Y %H:%M,repair) In ArcGIS Online all values are null. I attached an FME workspace and CSV file to reproduce the issue. I searched for documentation and forum posts. I think that I’m missing something simple.I must have a date field in AGOL because I’m creating a dashboard and need to filter dates.

Since a few days two of my FME hub transformers return the error below. I think it mentions that it is not possible to create a folder any more using the TempPathnameCreator. This might be resolved by updating the transformer to the latest version, but this also means that the transformers on FME hub cannot be used on old(er) versions any more. In another recent ticket in contact with Safe, I experienced something similar. Because of the security-changes for Flow several workspaces do not work any more. So I'm pretty sure many people will have similar issues. How can this be fixed without having to update all transformers to the latest version (and making it impossible to use them with older versions)?2026-07-15 13:08:16| 0.0| 0.0|ERROR |@Tcl2 -- failed to evaluate expression `set sampleTempFile [FME_TempFilename]; set ourTempDir {}; append ourTempDir $sampleTempFile {_d}; file mkdir $ourTempDir; set env(InlineGeoJSON_TempPathnameCreator_6e0c2906_d797_4636_928a_fa984000ecc45_dir) $o