Earn bonus reputation points and community badges by answering these questions
Hello fellow FME enthousiasts, We have been running into an issue when using the new Esri ArcGIS Feature Service [Writer] (from the new Esri ArcGIS Connector v3.13.2 package) to write to a Hosted Feature Layer on ArcGIS Online. The Hosted feature layer is created by Survey 123.Previously we used the old Esri ArcGIS Online (AGOL) Feature Service [Writer], since this won't be supported anymore in 2026 we started experimenting with the new one. When we try to update the hosted Feature layer with FME using the old one, all goes well, data gets written as expected and the geometry is visible.But when using the new one from the package we get a few warnings and no error's. The process tells us it's succesfull, we see the new records appearing in AGOL and the attributes seems to be as expected. The geometry is not visible either. When we try to zoom to a record nothing happens. When i open the layer in ArcGIS Pro nothing happens either when i try to zoom to layer/or zoom to selection. It's like there is no geometry.We've tried multiple settings without any result. When we try importing the same geometries into a newly created hosted feature layer in ArcGIS Online (through the New item button on the Content page) and using the new Esri ArcGIS Feature Service [Writer] everything goes fine. So it only seems to happen when it is a Hosted feature layer made through Survey123. Has anyone seen this behaviour before? Are we overlooking a setting in the new Writer maybe? Any help would be appreciated. I've added the log of the run to the new Writer below.Thx, and have a nice weekend!
Looking at the new Define Read Criteria By: Custom Query option in the FeatureReader in 2025.1I feel like there should be a warning against using Define Read Criteria with Esri Geodatabase format as it uses sql and bypasses specific SDE functionality.
We are implementing a CI/CD pipeline for FME Flow using an Azure YAML pipeline. When exporting an FME project from DEV with deployment parameters enabled under Advanced Options, those parameters overwrite the values in ACC and PRD during deployment. If the same project is imported manually, this issue does not occur.Is this a known bug in the FME Flow API? Or is there a recommended way to prevent deployment parameters from being overwritten during automated deployments?Additional details:If all advanced options are manually unchecked, deployments work as expected. The token used for the pipeline requires full permissions (fmesuperuser); otherwise, roles cannot be deployed. Restricting permissions or deployment parameter rights results in nothing being deployed.FME Flow version we have is 2024.1.2Any insights or best practices would be appreciated!










Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK