FME Form

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,I’m using FME 2026.1.1 Build 26121.I have observed strange behavior of SQLCreator today.User attributes which are created using “Create User Parameter” option are not getting saved (Step3.jpg). If we create then though “Manage User Parameters” and add user parameter with text option. User parameter is saved in user parameters in navigator but SQLCreator is saving the user name or password. Two screenshots are attached for reference with names step1 and Step2.This issue I have seen just today and everything is fine till yesterday. Even I entered the username and password as constant values directly, values which are entered are not saved. When I open the SQLCreator constant values are not saved. Waiting for response...Thank you! 

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

Hello 😊I recently updated FME Form to version 2026.2 and started experiencing an issue when connecting to an Enterprise Geodatabase using an SDE connection file configured for Operating System Authentication.FME returns the following error:"Failed to connect to Enterprise Geodatabase using connection file 'path_to_the_sde_file' due to missing credentials. A connection requires either Windows Authentication or both a user name and a password."The SDE connection itself appears to be valid. If I open the same .sde-file in ArcGIS Pro, it connects successfully and shows the correct authentication type in the connection properties.This workflow worked without any issues in previous FME versions and only started failing after upgrading to FME Form 2026.2.Has anyone encountered this problem before? Is this a known issue in 2026.2, or is there a workaround available?Any help would be greatly appreciated.

I read in a PoinCloud with Component x,y and z_2025_gem. The year changes as time passes by so I use a Parameter to define the component. For reading the point cloud, the component is read as z_$(JAAR)_gem. That works fine.When I want to use a User Parameter within the expression of the poincloudfilter I get an error on Flow but when I try it on Form with default values for the parameters, it works fine. If I try the workspace with default values on Flow it works fine as well.I checked the values for the Parameters on Flow by sending an email to myself with the values of the Parameters and the values are fine. So I guess that cannot be the problem. The parameters are used for reading the file and components as well and there are no problems there, only using them within the PointCloudFilter I have tried the following Expressions:1: @Component(z_$(JAAR)_gem) != -999992: @Component($(Z_JAAR_GEM)) != -99999by which JAAR = 2025Z_JAAR_GEM = z_2025_gem With the first expression, the Filter d

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 often find myself reusing subprocesses from my main workspace, either for debugging or for creating similar workflows with small changes in a new Workspace. I'm aware that FME has a ton of useful shortcuts, so I was wondering if there's one that lets you automatically select all the necessary(only!) transformers that belong to a previously used process. The idea would be to quickly copy and paste the used chain into a new workspace without having to manually select every necessary transformer or just copy paste all. Is there a shortcut or built-in feature for this, or is manually selecting the chain still the best approach? I feel like this is most likely highly specific to my own taste but I wanted to ask nevertheless since the main process got way too big :DThanks in advance! :)

I've got a few challenges concerning styling of an excelsheet. It's not just an ordinary sheet with columns and rows, but it's a reporting template. The report contains several attributes in different fields and several images. The issues/challenges I'm currently facing:I would like images to fit itself into a named range or predefined rows and columns. See screenshot below. I created a predefined named range ‘overzichtskaart’ which covers cells $C$4:$E$16. But as far as I can see there is no option to let FME/Excel know that the image should stay in those cells. I created a workaround now which tells the image that it should align in xlsx_row_id 4 and xlsx_col_id2 with a height and with of 255 pixels. But this goes wrong as soon as the alignment of the attributes changes (for example multirow text in column B). Does anyone have a smart work-around to fit the image exactly in the desired cells? Named ranges are useful to make sure that the attribute-data ends up in the right cell, but

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 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 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

Today I placed a default value for a date User Parameter as@DateTimeFormat(@DateTimeAdd(@DateTimeNow(),-14,'day'),'%Y%m%d')essentially the date widget in FME flow would go back 2 weeks, this used to work fine…. But alas, in 2026 it is now returning something wild Where is this highlight in Change logs? I read something about ‘better support for SQL date’… but nothing about Date\Time functionsAm I supposed to use this now ?a new datatime function?Here is the help documentation https://docs.safe.com/fme/2026.1/html/FME-Form-Documentation/FME-Form/!Transformer_Parameters/Date-Time-Functions.htmWhen we upgrade transformers, will the @DateTimeNow() functions get transformed into @CurrentDateTime ?Also the @DateTImeAdd is this going to be converted to @AddDateTime I can see the syntax @AddDateTime(<datetime>,<interval>)https://en.wikipedia.org/wiki/ISO_8601#Durations So this @DateTimeFormat(@DateTimeAdd(@DateTimeNow(),-14,'day'),'%Y%m%d')has become@DateTimeFormat(@AddDateTime(@Cu

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.

Hello, We have recently upgraded our FME Form to 2026.2.0.0 and I have been updating my workbenches that used the old Cityworks Inspection/Work Order Creators that have since been deprecated to the TrimbleUnityConnector. However, I am running into an issue of being unable to add assets to the inspection./work order which I did previously with an HTTP Caller. Is there a native way using the TrimbleUnityConnector to add assets?

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?  

We're using the TrimbleUnityConnector in FME Workbench 2026.2 and have noticed that when creating a new activity, the connector displays template options for items such as inspections. However, no Work Order Template options are available.As a workaround, we've been passing the Work Order Template ID as an attribute, which works, but we'd expected the templates to be selectable in the connector like the other activity types.Has anyone else experienced this behavior, or is there additional configuration required to expose the Work Order Template options?Here is inspections for comparison