Skip to main content
Open

ESRI ArcGIS Feature Service Writer: Expose Feature Service Web Service URL as an Output Attribute

Related products:Integrations
  • February 4, 2026
  • 5 replies
  • 116 views

salvaleonrp
Enthusiast
Forum|alt.badge.img+20

This enhancement will allow full automation of attachment backup workflows using ESRI ArcGIS feature services or geodatabase attachments being backed up to ArcGIS feature services.

Currently, even with the ESRI ArcGIS package, you need to manually configure the feature service feature URL on a FeatureReader so that the features’ featureID can be passed to the ArcGISAttachment connector.

Implementation would be sinmilar to the Publish Action item of the ArcGISOnlineConnector which exposes the _webservice_url

 

 

 

 

5 replies

PierreAtSafe
Safer
Forum|alt.badge.img+11
NewOpen

salvaleonrp
Enthusiast
Forum|alt.badge.img+20
  • Author
  • Enthusiast
  • May 20, 2026

Looks like it need to be implemented as a reader format attribute first so it gets exposed to the writer … is that correct ​@PierreAtSafe?

Woohoo!!

3.25.1

  • Reader: Add arcgisfeatureservice_url format attribute to store the feature server URL. (FMEENGINE-87137)

andreaatsafe
Safer
Forum|alt.badge.img+15

@salvaleonrp - correct! 


salvaleonrp
Enthusiast
Forum|alt.badge.img+20
  • Author
  • Enthusiast
  • May 27, 2026

@andreaatsafe I find this implementation odd that the service url will have to be exposed from the source to appear into the FeatureWriter… what if my source is from an Enterprise SDE reader or a different feature service than the destination… I thought the ask would be the service url wll be from the destination itself, whether its a newly created one or an existing one.


andreaatsafe
Safer
Forum|alt.badge.img+15

@salvaleonrp - misinterpreted this idea with the backend related ticket. My apologies!

The implementation note that you highlighted earlier is for the the reader to output an attribute holding the feature server URL: arcgisfeatureservice_url

On the Writer side, exposing the feature service URL as an output attribute isn't something that's supported today. 

 

I would be interested to hear from folks who upvote this idea what their use cases are to help us get a better gauge of what gap is missing.