Authoring

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

Hello I’m experiencing some issues using Dissolver. I want to take a polygon dataset which contains 160,455 independent polygons objects. Some of the polygons overlaps with other polygons. Some are not overlapped by others. I want to merge all of the polygons, whilst dissolving any overlaps, to create just one polygon object. Using Dissolver I am only able to merge polygons where they are overlapping, whilst input polygons that are not overlapped by other are remaining unmerged. This means that I’m getting 80,090 records in the output. But I don’t want that. I want just one polygon object as one record. This diagram illustrates (conceptually) what I have, what I’m getting with Dissolver, and what I require.How do I use Dissolver to do this? Or should I use a different transformer. Thanks,

I’m not sure if this is a bug in FME or if it’s expected behavior. We work in versioned, replica file geodatabases. The issue that has presented is that when our data was being checked back into the Enterprise database, the change records in our replica were being applied to features outside of the AOI of replica. In other words, somewhere in our FME processes it was not managing the OBJECTIDs in the INSERT/UPDATES/DELETES tables correctly. We believe we have tracked it down to the ‘Fast Deletes’ parameter of the FileGDB Writer. From my research it looks as though this truncates the tables, and re-inserts the features that weren’t deleted. I’m also reading that this may cause issues because it bypasses the A/D change tables. This tracks with the errors we are seeing.Is there any validity to that? If so, I’d like to suggest that the Fast Deletes parameter be defaulted to ‘No’ instead of ‘Yes’.

Hi, a client is using nb_NO (Norsk Bokmål) Locale on a Windows Server machine and the produced FFS filename is incorrect. They are using FME Form 2024.2.3.0.I have tested same om my machine Windows 11, FME Form 2025.1.1.0 - build 25615. I want to produce a filename “t2_æøå”.FFS (where æ, ø and å are Norwegian alphabet letters)using en_US Locale the produced file is t2_æøå.FFS using nb_NO Locale the produced filename is t2_æøå. FFSI repeated the test wiriting to Esri Shapefiles - and both Locale will give the result t2_æøå.shp. Seems like the FFS writer have an issue with Locale. Might be a known issue  but I was not able to find it. Thanks 

Hi.I’m looking into whether I can use InlineQuerier for a Workbench validation of data using a list of criterias.One of the things I need to do is use RegEx, and is thus trying to use the REGEXP construct mentioned in the documentation. However, this is the error I’m getting:InlineQuerier_2 (InlineQueryFactory): Error preparing database query: no such function: REGEXP Unable to execute statementThe full query is here:SELECT * FROM "Data" WHERENOT(("tvaersnitsform" IS NULL OR "tvaersnitsform" REGEXP '^(other: )[0-9a-zA-ZæøåÆØÅ]{2,}$' OR "tvaersnitsform" IN (SELECT "key" FROM "LOOKUP.Tvaersnitsformtype")))If I remove the REGEXP part of the criteria, it works just fine.Has anyone used InlineQuerier much, and have some insights into what might be wrong here ?Is it just a subset of SQLite’s SQL language being available in InlineQuerier ?If I click the dialog Help button, it leads me to a page, that clearly shows REGEXP.Cheers.

Hello Forum, I need to run a polygon-in-polygon attribute update process. I would normally use the AreaOnAreaOverlayer transformer for this where I know that features from the first polygon dataset are all fully within any individual feature from the second polygon dataset. But I now have a dataset where any feature from polygon dataset 1 could be… a) fully within a given polygon from polygon dataset 2, b) straddling between two or more polygons from the other polygon dataset. This is what I need… If a feature from polygon dataset 1 is fully within a feature from polygon dataset 2 then populate a new attribute with the value of the feature from polygon dataset 2 If a feature from polygon dataset 1 is partially within two features from polygon dataset 2 then populate a new attribute with the values of the two features from polygon dataset 2. These diagrams explain it further…. Is this possible in FME Form?  Thanks,

Hello, I have a dataset containing an attribute PROP_TYPE. This contains any one of the following values: HOUSE_MNGD; FLAT; DUPLEX_SHRD; MAISONETTE; FLAT_TYPE2. I want to change these values within the FME Form workspace… HOUSE_MNGD change to House managedFLAT change to FlatDUPLEX_SHRD change to Duplex sharedMAISONETTE change to MaisonetteFLAT_TYPE2 change to Flat type 2 I know I can change a stated value within a StringReplacer. This works well, but it’s only on one of the possible values (e.g: Text To Replace = HOUSE_MNGD; Replacement Text =  House managed). How can I use the StringReplacer to specify all possible values within the PROP_TYPE attribute and replace them with the values I then specify? And do that in one StringReplacer? I’ve tried AttributeValueMapper and added in all my possible changes (line by line), but I couldn’t get that to actually change the values in the output. So, I’m hoping I can do it in one command within one StringReplacer. Thanks,

This seems pretty basic so it’s probably a configuration that I’m missing, but I’m using FME Form v2025.1.1.0 and I have a half dozen Loggers set up to capture features that are repaired or failed in GeometryValidators that precede them.  When I run the workbench I have ‘Enable Record Counting’ set so I can see the counts going to the Loggers, but none of the messages I would expect are getting written to either the Translation Log window in FME Form nor to the log file on disk.  I’ve set the Navigator > Workspace Parameters > Log and Troubleshoot > Max Features to Log to -1 to log everything, and I’ve confirmed that the ‘Severity Level’ in each Logger is ‘Information’.  I’ve tried all 3 settings for ‘Feature Logging’ of ‘Log Only’, ‘Log and Record’ and ‘Message Only’ in various combinations of the Loggers and I’ve confirmed that the ‘Max Messages to Log’ for each Logger is larger than the number of features being routed to them. The expression in each Logger is pretty simple,