Esri ArcGIS Portal Feature Service v Esri ArcGIS Feature Service

Yep. In the new ArcGIS Feature Service reader, make sure to select the Item Source first - either Group or User Content.

Once you do that, FME will list all services available under that source.

That’s not the issue, i want to reference a featureservice without reference to a group, which was possible in the existing reader.

I think this is a missing feature nowadays. When your source is AGOL, you need to select a group. This used to work perfectly. When using different software than FME it still does works.

I also miss the option to use a token. I used to get data from other people’s mapservices by simply putting it in the FeatureService reader, combined with the temp token found in the developer window. This way I could easily download the data from a mapservice, even when there was no featureservice present. Now I need to keep an older version of FME to do this, or use Python.

​@ebygomm, sorry for diverting your issue into a newer one. I’m quite familiar with ​@nielsgerrits comment above.

@nielsgerrits you can still use the generate token. Not really recommended for production deployment but for quick authoring, as you know. I don’t really like the user experience though.

Her’s the configuration.

Here’s the end result

Having Add Web Connection is for convenience, but I’m too skeptical since the Add Web Connection in the Feature Service formats can be confusing than keeping it in the Web Connections under FME Options, specially for beginners. WHen there were three separate formats it was fine, but when they were combined into one format, all of a sudden the list of web connections got longer - showing both the legacy and the new web connections of all feature services, in addition to the option adding more with this Add Web Connection feature from the format dialog.

When you are migrating from the legacy feature service formats to the  ESRI Feature Service format you can be overwhelmed if you manage numerous ArcGIS portals.

*When you are migrating from the legacy feature service formats to the  ESRI Feature Service format you can be overwhelmed if you manage numerous ArcGIS portals.*

Sensible naming conventions are difficult when you need two different web connections to the same location across all environments whilst things are migrated.

Can someone from Safe confirm this?

We have portal services that are shared at an organisation level and are not in any group. It doesn’t seem possible to read these with the new Esri ArcGIS Feature Service reader? 

Not from Safe, but interested to find out. It seems like an option for an Organization in the Item Source parameter should be available. (There’s only User Content and Group)

Yes, I can see that feature layers hosted in the Enterprise and shared to the Organization do not appear on the list of feature services, unless you own the feature service.

Tested with Data Interop for ArcGIS Pro 3.5/Enterprise 12.0 and Esri ArcGIS Connector safe.esri-agol [3.20.1]. I’ll check some more in a little bit.

In the older reader, it was always the case that if you used the dialog to select a feature service the group name would be included,

e.g.

GroupName/ServiceName(89495c8ad7b346ecaf4358d757469fe0)

but this could be removed and using just

ServiceName(89495c8ad7b346ecaf4358d757469fe0) is possible

Additionally, it’s now the group id not the group name that is actually stored under the group parameter so it’s also an additional parameter that needs to be changed between environments. (Although does remove the risk of people changing group names and breaking FME workspaces!)

Using the legacy Portal feature service reader, I see my user name and Groups in the popup dialog to pick a feature service:
 

I read back from the top and confirmed through testing how you were doing it.

I got confused myself with Groups and Org but I picked a FS that is shared only in the ORG and not OWNED by the User used to get the token.

You can actually still do what you have even with the new format reader. Here’s the three ways I tested.

Is there an ask here to add read FS shared only in the Organization? Considering that the ArcGISOnlineConnector and the ESRI Rest API allows the flexibility, it actually makes sense to have an option to show these feature services during the selection.

There are several use cases I can see mostly e.g. aggregation of Group shared feature services into an Org only accessible feature service.

1. Multiple county data managed by workroups in aggregated in a State layer shared to Org.
2. Parcel data shared in a large utility for other departments
3. Electric transmission and distribution data shared in a Shared portal with sister companies or just the Org 
4. Project data maintained in work groups, then for project transparency, shared to the Org.   

Thanks for posting the Idea @ebygomm!

Useful to know, thanks ​@salvaleonrp 

Can confirm that it works for the service i’m interested in. (That’s with package 3.19.1 and Enterprise 11.5)

My preference will be to not actually upgrade to the newer writer at this time, it’s only in cases where we want to use some of the new functionality of the package, e.g. attachment connector to avoid having multiple web connections

Added an idea