FME Form

I have a workspace where FeatureMerger_2 and 1/3 connection is disabled, but when I trigger a Partial Run from the upstream reader BODENBEDECKUNG_A, I get the "Caches required to run translation are missing or stale" prompt, listing all the transformers that feed into that disabled FeatureMerger (See attached screenshot)Since the FeatureMerger itself won't execute, I'd expect its exclusive upstream feeders to be treated as dead and excluded from the run, but apparently they are still requiredIf I instead disable each incoming connection to the FeatureMerger, the feeders correctly drop out of the run and I don't get the prompt, even when Feature Merger is enabled.Can someone explain the logic here? Why does disabling a transformer and the relevant connections (the one coming from the reader where the Translation is started) not back-propagate to exclude its upstream feeders, while disabling the connections does?

When I try to connect the .sde file on FME, I got the this Error. 

 Hello,I would like to remove attributes (or columns?) from my data stream that have no value (missing or null)In below example that means “eindegrarantieperiode” and “integraalproject” need to be removed. Note: can we do this dynamically? I don't want to manually go through 50+ attributes to check if they contain a value or not.(FME 2025.0) 

In >2026 to connect to AGOL or Portal enterprise from FME, we utilise the “unified” Esri ArcGIS Enterprise OAuth (Template)(safe.esri-agol) web service   ARCGISFEATURESERVICESWorking with Esri ArcGIS Feature Services in FME – FME Support CenterThe article perhaps fails to mention how to handle the web service Loopback Interface Redirect or Proxy Redirect Strategy, as the Embedded Browser is deprecated in FME Form 2025.2The arcgis registered application needs to have http://localhost as redirect URIWhat about FME Flow redirect URI?My suggestion is in Connections & Parameters - FME Flow for any given safe.esri.agol newest Esri web service in Flow >26It needs a default Redirect URI of “ self “? 

After the June 2026 ArcGIS Online update last week, the Esri ArcGIS Connector stopped working when attempting to download .csv admin reports. Prior to last week’s update, the connector would download these .csv files without issue. As of last Friday (6/26), FME returns the following:fme_rejection_message: 400 Client Error: Bad Request fme_rejection_code: INVALID_FILEwhen attempting to download .csv file. These errors persisted over the weekend and today. It fails both in FME Form and FME Flow. Versions I am using:FME Form: 2025.1.2.0 (Build 25630) FME Flow: 2025.1.2.0 (Build 25630) Esri ArcGIS Connector: 3.25.1Note: This exact error is returned for multiple types of .csv files generated within AGOL. I have dug into Chrome Developer’s tools to compare and confirm URLs and Payload being sent to the API and everything looks the same on both ends (Chrome and FME).Something might have changed with AGOL API’ backend. Is anyone else seeing these same issue? If so, how did you resolve it? Or,

Hi all,I am trying to write a dynamic Excel formula (=SUBTOTAL(103, A2)) to an Excel sheet using FME Form, so that it evaluates automatically when a user opens the spreadsheet. However, FME keeps writing the formula as a literal text string (showing =SUBTOTAL(103, A2) in the cell) instead of calculating the actual formula.Here is what I have configured so far based on the documentation: AttributeManager: Created an attribute named ZICHTBAAR.formula Value set to: =SUBTOTAL(103; A2) (or with a comma depending on locale) I also exposed the base attribute ZICHTBAAR without the extension. Excel Writer Feature Type (User Attributes): The column ZICHTBAAR is present. I tried setting the Data Type to both string and auto. The issue: When running the workspace and opening the output file in Excel, the cells still show the raw formula text. It only evaluates to 1 or 0 if I manually double-click the cell and press Enter, or force a hard recalculation.What am I missing to

hi,I'm trying to load data from a WFS service into a database.The WFS service contains 25 feature types (tables) with a total of more than 153,000 features.Here is my FME workspace:CreatorHttpCaller (retrieves the list of layers)PythonCaller (extracts the 25 FeatureType layer names)HttpCaller (GetFeature request using typeNames=<layer>)PythonCaller (retrieves the numberMatched and numberReturned values for each layer)Tester (numberMatched == numberReturned)PythonCaller (retrieves the features, transforms the geometry, etc.)CounterAttributeManager (adds a unique ID using the counter)SchemaScanner (collects the 25 schemas with their attributes, along with the 153,000 features)FeatureWriterThe issue is that the FeatureWriter doesn't correctly associate each schema with its corresponding features.If I insert a Sorter transformer before the FeatureWriter, the workspace runs successfully, but all attributes end up being written to every table instead of only the attributes that belong

There was an update to ArcGIS Online last week 06/2026 that is causing an issue with the number of records you can read using the AGOL reader. It is limited to 400k records. Since the hosted layer that I am reading has way more than 400k it has broken my workbench. Has anyone ran across this yet and is there a workaround I can use since this workflow is essential for updating an enterprise application.

I am looking at this Article for setting up Azure OAuth Connection for Data Bricks, the article is for Reader, but I assume the same set up will work for the Writer.   We have an Azure app already set up for the FME SharePoint Reader and Connector, can the same Azure app work for both SharePoint and Data Bricks ? are there any best practices about using the same Azure app for both or making separate Azure Apps for each ?   Any suggestions or cautions, things to watch out for, etc,  appreciated  https://support.safe.com/hc/en-us/articles/27147444106381-Setting-up-a-Databricks-Reader-Azure-OAuth-Connection   

I have an issue with a working workspace that has run for a couple years now. Recently, since 28/5 I have issues with writing integer values.What I’m trying to do:Insert point features into an existing ArcGIS Online hosted feature layer using the Esri ArcGIS Feature Service writer. Integer attributes (e.g. reportYear, equipmentNr) should be written with their actual values, e.g. 2026 / 2027.What happens:Every integer field is written as 1 in the target layer, regardless of the source value. In the Data Preview right before the writer the values are correct (reportYear = 2026 / 2027). After the insert, the integer fields all show 1. I reduced this to a minimal workspace (reader -> AttributeKeeper keeping only the integer attributes -> writer) and it still happens.Environment:- FME Form 2025.1.2.0 (Build 25630)- Esri ArcGIS Connector package 3.25.1- WindowsWhat I have verified / tried (none fixed it):1. Values are correct integers in Data Preview, immediately before the writer.2. C

I just found that in the geodatase_sde writer, you can create domains for the field you’re creating. This is very exciting news! And the domain is indeed created in the SDE database. However, when I view the featureclass in arcpro, the domain for that field is not there. I still have to associate that domain to that field. Has anyone tried this? Is there a parameter i’m not seeing? I’ve checked all the parameters around the field, the feature type, the writer and didn’t see anything that could be it. The documentation didnt have any info except on how to create the domain. bug or feature? 

I’m trying to connect to Salesforce in form with 2026.2, but every time I do, FME never finishs authenicating. My log in on Salesforce goes fine, but it still says waiting authenication in FME. Do I need to change a setting?

Hello,We are currently upgrading an FME-based application for one of our customers from FME 2020 to FME 2024, and we have encountered an issue that appears to be related to coordinate system handling.The application uses FME to convert a set of DGNV8 drawings into an MS SQL Server database. For some drawings, we observe a positional shift of approximately 10 centimeters (a few decimeters at most) after processing.In the DGNV8 Reader, the Coordinate System parameter in the Navigator window is set to "".When inspecting the source datasets with FME Data Inspector in FME 2020, all drawings are reported as having an Unknown Coordinate System, regardless of which file is opened.However, in FME 2024, we see different behavior:For some drawings, Data Inspector reports the coordinate system as EPSG:28992. For other drawings, it reports NationalRD-NL.The drawings belonging to the latter group appear to be shifted relative to the other drawings.My questions are:Is this behavior related to differe

Just recognized, after migration of a workspace from 2024.2 to 2025.0 a BulkAttributeRenamer shows strange results: The transformer is set to change attribute names to lowercase (mode rename) for a selected set of attributes. This works as expected. However the remaining attributes (not selected for any change) got almost completely removed. ‘Almost completely’ means from the >5000 records only 4 have the attribute after the transformer while all other records show the attributes as <missing>.@safe - although it’s easy to mitigate it might be worth to dig into it.note: in mode ‘keep original attributes’ results are as expected.Klaus 

Has anyone else noticed when creating a list using the AttributeExploder it truncates the last two characters of the list name, resulting in complications when using a ListExploder downstream because the list doesn’t exist.Using the default settings:Default List Settings in the AttributeExploder Transfomer The resulting list:List Name Is Truncated In Feature Information This broke a workspace that was previously working. It was a niggly one to catch as the only thing that had changed was the FME version.As a workaround, we created a user parameter which had the default value “_attr_li{}” and used that in the ListExploder which worked. FME Form version:FME(R) 2024.1.1.0 (20240729 - Build 24619 - WIN64)

I was using Service account Key File as a credential source for google cloud storage connector but it looks like its been removed as an option. anyone else seeing this? 

Hi there, Could I please have an update on if the I3S writer support point clouds after the release of 2023.1.1? If not then could I please have an update on the timeframe on this? Thanks, Shilpa

I'm seeing the following lines in the Translation Log:AutoCAD Reader: Entity type of 'AeccDbAlignmentStationLabeling' found, but not supported. Skipping entityAutoCAD Reader: Entity type of 'AeccDbAlignmentMinorStationLabeling' found, but not supported. Skipping entityI'm reading a .DWG in as an AutoCAD Civil 3D format file. Am I interpreting this correctly that station labels are not supported by FME?

I was able to do a cumulative count of duplicate values (where duplicate is “-1” only) using a Group By on a Counter transformer shown below. (Added note: I should have added this to remove ambiguity - SORRY. The output as shown below in the Preview is the desired output. I only care to know the number of consecutive sequential values when the value is “-1”. If the pattern changes and another series of duplicate “-1” appears, the count starts with “1” again. I don’t care if the pattern for duplicate values are greater than “0”, like “2420” on the Preview.)  Since I have more than a dozen of these attributes, I’d like to use an AttributeCreator instead but I can’t seem to use the CurrentAttribute() to accumulate duplicate values.In addition, everytime a sequence of “-1”s begin (as shown in row 143 above), count starts at 1 again.Any suggestions?

I am writing AutoCAD DWG with changing areas/extents. My template file defines the styling. When opening the file in CAD it zooms to a blank area (possibly from the extents of the template file) and I need to zoom to extents to find my current area. Is it possible to either remove any extent information from the template file, or force the output DWG file to zoom in on the current area extents?

I am using FME to write to microstation DGN. The FME workbench file is using the fanout option to write different areas to the microstation DGN file, based on the same seed file. At the moment I have to use a microstation macro to "fitview" of each produced file in order to have the microstation file centered at each specific area. I rather use only FME to avoid this additonal step.Is there a way / transformer in FME to save the microstation file centered in the written data?

Hi All,I'm experiencing a bug in the Excel writer in the new FME 2024.0. I've made a script that outputs multiple data categories I need to process in a particular order to ensure my calculations are fed as desired. The bug causes the attribute names to not be written in the first row in Excel; it just starts with the data in the second row. Whenever I open the exact same script in FME 2023.2, the writer does write the field row names, without me changing anything in the writer settings.For now, my solution is to not use FME 2024, but since my customer does use 2024, it's not desirable. Does anyone have any ideas?Here is a preview of Excel. I can't scroll up to the first row, the data is not hidden, and the navigator also won't allow me to go to row 1. 

I am clipping a raster by a polygon, but it sometimes seems to skip parts, I have the clipper set to Candidates on clipper boundary set to Output as Inside.  I know this poly crosses 4 cells, so this is what I was thinking would come out of the clipper Inside port  But instead I get this Any thoughts why it is skipping that one cell?  This is a single band raster and all these cells have data 

When adding a Geopackage Writer to the workspace and using the “Copy from Reader...” functionality to import a feature type definition (from a Geopackage reader), the geometry set on the Geopackage writer feature type is incorrect.Upon opening the newly added writer feature type, it doesn’t show any geometry. Opening it a second time then shows the Geometry as <All>, which is not a valid value for the Geopackage format. We’re currently investigating the issue and will be filing a bug report shortly to get this issue resolved. 

Currently I have 23 CoG’s in an Azure Blob container and I want to retrieve only the area of those CoG’s covered by a rectangle that I use as the initiator for a FeatureReader.Unfortunately, the FeatureReader is reading first all the CoG’s in before making the decision where the bounding box is within, and then it returns the entire CoG, where I was rather expecting it would return the part the bounding box is covering.The CoG’s originate from the Copernicus DEM coverage GLO-30, contain overviews, etc…It takes almost 3 minutes for the FeatureReader to process the request. The bounding box is within a single CoG.When looking at the parameters for the COG reader, then I can see there is actually the possibility to set a search envelope. I could feed the bounding box to the envelope, which sadly is missing in the FeatureReader. Is there a way to speed things up? I only want to have the parts of the COG’s covered by the bounding box used as initiator, basically performing a range request.