Authoring

Hello,I created an FME script in which I have 10 Readers and 10 Writers. I would like to run this script in a specific order. I don’t want FME to execute everything in parallel, but instead wait for Writer A to finish before reading Reader B… How is it possible to run things sequentially?Thank you for your help

Hi there,I have installed FME Flow 2026.1 in AWS has a High Availability WebUI/Core with distributed engines.The setup uses HTTPS on an internal url (corporate network)When I try to connect FME Form to Flow, I get the following error message Unable to retrieve public key from FlowUnable to establish secure communications with FlowDeployment parameter access failed (Connection Error) - Unable to connect to FME Flow. Has anybody seen this before? ThanksWhen I use the url in the browser on the same machine (tested on 2 different machines), i can log in using my admin user account 

Hello;I'm stuck uninstalling FME Form 2026.1 (build 26103) and I no longer have the installation package. Is there a version for download?I have version 2026.1.1 (build 26121) but I get an error when uninstalling the old version.Thank you.

Hi,I have several rasters that are quite dark, I’d like to brighten them. I can do this automatically in another software, but this involves me setting up a script (I use mogrify).I’d like to do this in FME, but I have never been able to work it out. I have tried several things over the years. The best I’ve been able to do dynamically is make the image better, but then the colours go all strange. I want to keep them close to real like. Here is an example of a dark image.I don’t think the images have a consistent correction that should be applied, which is why I want it to treat each image individually.Any help would be great thanks  

Hello, As announced in the following article https://support.safe.com/hc/en-us/articles/44279253166605-Nested-User-Parameter-Deprecation, Safe have deprecated nested user parameter starting with versions patching the recent security issue.First of all, the deprecation really took us by surprise, simply because it was written nowhere in the security advisory article the potential regression of applying the patch. We only noticed the new deprecation by checking the quaterly FME Knowledge. In my opinion, Safe should have better communication on new major deprecations like this one (as a matter of fact, our official FME Partner haven’t heard of this deprecation before us asking them).Moreover, I understand that due to the criticality of the issue, Safe had to patch it in a hurry, but FME Flow behaviour is less than ideal:Nested parameters being functionnal on FME Form but not Flow creates a major undocumented discrepancy between the two; Added to the fact that the error message is simply “

Hello,I try to do something very simple but I think I must be dumb. So I’m working with a ArcGIS Featureservices data which are agriculture data. In the RPG_2023, the attributes associated to “CODE_GROUP” will be only numbers like 11,16,18 so very simple.In the user parameter I try to add the “CHOICE” parameter because I want the script to ask me which kind of attribute I want to work with.I try to use the import wizard using the valuesBut then in this box is going endless ==>I don’t know if I do something wrong or it’s normal for the reading dataset to be so long.I don’t have a lot of different attributes (maybe 26 max different kind of “CODE_GROUP”). If someone could help me because I don’t understand what do I do wrong. Or if you have documentation about the subject I will be very happy to learn more about it.Thanks a lot and sorry for my english !! 

Hello,I found more people who raised the same question, but it was 4 years ago, and I don’t know if it has been resolved and/or how.I am in the following situation: I need to read subtype domains from an ESRI enterprise geodatabase, and I would like to see the domain descriptions, not just the codes. I’ve tried using the new ‘feature service’ reader (enterprise configuration) and enabled domain resolution and exposing subtype_name, but I didn’t get the expected result.While reading the documentation, I saw that the .sde reader offers more options in the constraints, including “Resolve Subtypes.” Is it actually possible to obtain subtype descriptions this way?Am I missing something when using the feature service?Thanks :)

I am using FME Form 2026.1. Using ChangeDetector. I have one point feature class (Reader name ends in _revised) where I moved a point to a different location but did not change any of the attributes. I output to the Writer and the change in the point location is not shown. I have Check Geometry checked in the ChangeDetector. I did not insert any new records, the only update was I moved a point. Any ideas as to why the point moved to the new location is not being written to the Writer? I have some screenshots from my workspace:ChangeDetector parameters: The Writer parameters: 

I have an address feature class in a SQL Server 2022 Enterprise Geodatabase. Some records have been updated in the attribute table and new records have been added. I want to write these updates and additions to another Enterprise Geodatabase and a File Geodatabase. Would the recommended approach be to use a ChangeDetector before each Writer and then use Upsert in each Writer?OR Can I use Upsert in each Writer without using ChangeDetector? Currently, the way I do this is to Truncate Existing in the Writer for the Enterprise Geodatabase and the Writer for the File Geodatabase. But, this can take a long time to run. It seems more efficient to use Upsert.

Hi.As most will know, Geopackages are notoriously sensitive to geometry topologies.I want to insert all polygons into a single layer/table, but the topology is tripping me up.I have a number of fairly simple polygons (fme_polygon and fme_donut) and a handfull og more complex polygons, e.g. large polygons with many holes. These latter polygons are stored in FME as fme_aggregate for some reason. The holes are all created by the Clipper transformer.I’ve successfully coerced my simple polygons into fme_aggregate’s, but when output to Geopackage, some of the geometries gets deleted and the feature is stored without its geometry. This typically happens to the unaltered geometries (i.e. the original fme_aggregate’s).I’ve checked that all the input geometries to Geopackage are valid and has @GeometryType() = fme_aggregate, so what’s tripping me up here ?Any insights are welcome.Cheers.Using 2025.1.1 for this.

Hi,Has anyone used the 12dxml reader before and know why it is so incredibly slow? Even for small files with caching turned off. If there was a way to speed it up that would be great.The actual reader isn’t so bad, it is ludicrously slow when you use the feature reader though. I can’t see whyThanks

Hello all - grateful for some suggestions here - I’m being driven slowly mad…We are developing a ‘data portal’ style workbench running in FME2025.1, using a dynamic writer to deal with multiple input and output datasets and multiple possible output formats - the dataset and output format are specified by user parameters.The source datasets are point or polygon datasets stored in an MSSQL Esri SDE and output formats  include all the usual GIS data formats.This is generally working well but one polygon dataset is failing to wite out. In this case the log reports the following:=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-Feature output statistics for `GENERIC' writer using keyword `GENERIC_1':=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-                           Features Written Summary=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=============================================================

What happened to the reader and writer drop down menus in FME 2025.2? Why would they remove them? Am I just missing how to add them back in? So frustrating.

I have some columns within my Excel template that have a lot of text, so I thought to put the wrap text feature on for basically the whole spreadsheet. Thing is, only some of the cells wrap text instead of all of the cells. In the screenshot you can see what I mean - I have tried everything to try and fix this. Hoping someone in this community can assist! I tried using the ExcelStyler transformer too to no avail. 

The zoom slider bar is missing in FME Flow 2026.1. Please bring it back. It makes zooming more convenient. It was in FME Desktop 2021. Are there plans to bring it back? Or is there identical functionality in FME Form 2026.1? If so, where?

I have a very simple workflow setup:read a table (typically either a .CSV or Excel file) which then connects to an Attribute Manager set up with multiple fields from a template that adds and renames them so they can be seamlessly imported into another database with exactly the same field names; and then this connects to  Excel Writer (the file format required for import)Since the files I’m reading into FME Workbench do not have all the fields or match exactly those in the template/Attribute Manager has (the point of the workflow), I get an “incomplete transformer” error message. The workflow executes flawlessly, however, and I’m getting the results I need.I’m wondering, however, if there is a way to eliminate the error - the red “incomplete transformer” icon in the navigator window is a bit disconcerting. 😉 PS: I have added the following annotation to the AttributeManager should there be no way to get rid of the error message/icon before I share the workflow.************ATTRIBUTE MANA

Just sharing information about a new feature I found."Enable Performance Profiling" would be introduced in FME 2025.2 Workbench. You will be able to log detailed performance profiling on workspace run easily whithout editing header.Have been waiting for 10+ years :-)Sharing: Detailed Profiling of Workspace Running Performance[Addition] The command is available since FME 2025.1. I have overlooked that... 

I’m testing the new OPENFILEGDB Reader in 2026.1 that supersedes the old Open GDB Reader, but it doesn’t resolve my subtypes and domains. Am I missing something?If not, please bring this functionality back, as it is/was one of the main reasons for using the Open Reader.Workaround for now: the old one is still present albeit marked as deprecated, so I guess it may disappear in the near futureOld Open GDB ReaderNew Open GDB Reader 

We’re currently in the process of looking to move to a newer version of FME Form (2025.2) but we’ve hit an issue where we can’t meet the required dependencies for adding a Smallworld reader regardless of having the correct files in the right locations. If we open an older workspace with the reader already added, it will still complain about missing dependencies but the workspace will execute correctly.If you select ‘Update Reader’ from the navigator you can add additional feature types etc and change parameters, but you can’t add a new reader due to the missing dependencies. I noted that there was a Fix in Build 25811, but when I tested in 2025.1 (before the fix), there are no issues adding a Smallworld reader. I understand that the Smallworld user group probably isn’t the largest but is anyone else having the same issue. Would really appreciate if someone is able to provide a sanity check. Thanks

I’m trying to follow the FME Form course from a MAC and one of the very first exercises is using a Esri Geodatabase (File Geodb Open API) writer. Unfortunately I’m getting this error on the platform. Is there any workaround for this?

Moving this to FME Form Q/A.  

Within the new ArcGIS Feature Service reader (part of the Esri ArcGIS Connector Package) if you choose a source type of Enterprise it’s not possible to connect to a feature service that is shared across an entire organisation and not in a group.This can be done if you use a Source Type of Standalone Server (but it’s not obvious).It would be nice to have and Item Source of Organisation which would allow connection without specifying a Group 

In Form v2026.1, what exactly does the new option “Read Best Fit View if Selected view is Missing” do? The “Help” says:“This parameter controls reader behavior if a selected view is missing.By default, if a view specified in the Specify View to Read parameter is missing, the reader selects the next available view.”Does it select the very first view that pops up when clicking the 3 ellipses (...) or is it referring to something else?Was that option a hidden feature in previous versions that got exposed as a parameter in 2026.1?

This seems like is should be so simple, but I can’t get it to work! I want to take a CSV file that has Feature Class Names, FieldPrefixs, and Feature types. For example:FeatureClass, Prefix, FeatureTypeRoads, Road, LineWildLandUrbanInterface, WUI, Polygon. This CSV file will be dynamic, meaning that the Feature Classes that will be summarized will change.I then have a SummaryPolygon Feature Class which defines the polygons on which to summarize. I want to iterate through the CSV file, summarize the data for each CSV record, and then add two fields with the prefixs (ie Road_Miles, Road_MilesPerAcre or WUI_Acres and WUI_PercentArea) to the SummaryPolygon. I thought the workspace runner would work well for this, but the Child workspace isn’t updating/showing the new fields that were created after each iteration. Meaning the schema isn’t dynamically updating with the two new fields on the next iteration. In my Reader, I have Workflow Options set to Single Merged Feature and Merge Feature T

I want to embed a DB connection in my workspace without the password being saved in the workspace.A password should not be saved in an FME workspace file. But I want the connection details to be saved in the workspace file.What I've tried:- If I leave the password blank, the workspace does not run because the connection requires a password. I could save the workspace with a blank password. But if I want to run the workspace, I need to edit the Reader/Writer or Transformer properties and enter a password. FME detects this as unsaved changes in my workspace and it could easily happen that the workspace gets saved with the password by accident. This is a stupid solution.- I could create a user paramter for the password field. When I run the workspace, I have to make sure that the "Save As Parameter Default Values" option in the parameters dialogue is disabled. To ensure that, I could add a custom message to the parameters dialogue telling the user to be careful and not to save the paramet