Skip to main content
Open

ArcGISFeatureServiceViewManager transformer in the Esri ArcGIS Connector package

Related products:Transformers
  • October 3, 2025
  • 5 replies
  • 116 views

bruceharold
Supporter
Forum|alt.badge.img+19

If the information product you want to manage is a hosted feature layer view then at present you need to manually adjust its properties outside your ETL workspace, or tackle the job using the ArcGIS REST API via HTTP.

Feature service views offer ways to leverage feature services other than simply as they were created.

Here is an example of using HTTP calls to automate one property - swapping the source service for the primary layer..

In addition to basic create views, add and remove layers, and delete views functionality for views you might want to adjust name, description, tags, visibility, extent, editing access, definition query, field visibility or layer order.

The definition-adjusting REST calls (addToDefinition, deleteFromDefinition, updateDefinition are tricky to implement.

Who would like this capability?

If you have other requirements comment in this idea.

5 replies

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

chriswilson
Enthusiast
Forum|alt.badge.img+21
  • Enthusiast
  • October 6, 2025

Setting sharing as well.  Great idea Bruce.


bruceharold
Supporter
Forum|alt.badge.img+19
  • Author
  • Supporter
  • October 6, 2025

Setting sharing as well.  Great idea Bruce.

Thanks, yes of course.  FYI, feature service views currently list as feature services in the ArcGISOnlineConnector and you can share them.  However I separately requested that feature service views be listed as an item of type “Feature Service View” so you can identify them for things like calling their sources endpoint.


phoeffler
Contributor
Forum|alt.badge.img+9
  • Contributor
  • January 7, 2026

This is a great idea - Views can be very powerful, but also very tricky to navigate. Being able to do so within FME more directly could be a nice option. We’ve run into issues when trying to deal with schema changes, swapping sources, corrupting view items, etc. The more support for these powerful items that esri seems to be moving towards more and more, the better.


jklatt
Participant
Forum|alt.badge.img+2
  • Participant
  • January 15, 2026

I would definitely like this functionality. Funny enough, I’m in the middle of implementing a “Blue/Green” or “A/B” strategy to updating feature services that swap the source.

Requirements that come to mind are: creating a view from scratch, swapping the source of a view even when the contents of the view changes (handling changes to the scope of layers in the view and the schema of each layer), and validating the accuracy of the view (does the data in the underlying source match what’s seen on the view?). Also, an option to remove the original source (but this can easily be done downstream).

In general, build the new view, point the view to the right source, and validate that the view has the proper properties and accurate datasets.

I haven’t gotten very far yet, so these are the requirements I can think of at the moment. I’ll weigh in as I get further along.