Skip to main content
Question

Feature Writer transformer issue writing to ESRI ArcGIS Feature

  • June 23, 2026
  • 2 replies
  • 20 views

chadprop
Contributor
Forum|alt.badge.img+3

Hello All,

There may be a bug (or least a less user-friendly transformer) in Form 2026.1.2
Choosing specifically the Esri ArcGIS Feature Service as the Format, the Dataset parameter is by default disabled:
 

I’m unable to determine what the “related parameter” is that is *disabled.

I can setup my feature types by importing the schema of my intended target data, but saving all the changes in the transformer puts it in an error state.

If you visit the navigator window you can see where the “Dataset” parameter is in error.




The only way I’ve found so far to get around this issue is to go into the Manage User Parameters setting and create a new user parameter for Dataset which needs to be the feature id of the online feature, inclusive of the parentheses around the id number.

 


 



This is definitely adding more configuration steps to the Feature Writer than before as the Dataset used to be configurable directly inside the transformer and you didn’t have to remember to copy the feature id from Esri.

Anyone else experiencing this?
Thanks
Chad

2 replies

j.botterill
Influencer
Forum|alt.badge.img+58
  • Influencer
  • June 23, 2026

I assume your webservice/webconnection is configured and authenticate properly

check the fme package version under Utilties > FME options > Packages

I had to get to 3.25.1 for less bugs

I can only recommend duplicating the steps in a new workbench, in the 2026.1.2 form


chadprop
Contributor
Forum|alt.badge.img+3
  • Author
  • Contributor
  • June 23, 2026

Hi,

This is with the 3.25.1 safe.esri-agol Connector package, on Form 2026.1.2.  I had read in the release documentation that the Esri ArcGIS Feature was now requiring the feature id from ESRI as a parameter but needing to visit the navigator window outside of the transformer doesn’t seem as intuitive as working with prior releases of the package.  Also to note, this issue doesn’t present while working with a generic “Writer” against the same feature service.