One way that I look at it this: Feature layer is a layer (as folks mentioned early in this chain) that (a) pulls features (includes geometries and attributes) from a service and (b) draws them on the client The source of a feature layer could be a) a sub layer off a map service e.g. https://sampleserver6.arcgisonline.com/arcgis/rest/services/Hurricanes/MapServer/0 b) a sub layer off a feature service e.g. https://sampleserver6.arcgisonline.com/arcgis/rest/services/Military/FeatureServer/2 when the source is a sub layer off feature service (not a map service), you will see Editing capability enabled in addition to all rendering/drawing capabilities. Screenshots showing difference of map viewer UI based on layer source When source is a feature service When source is a map service
... View more
Philip - I appreciate your feedback and maybe it's just the way I'm thinking about it. However, to answer you specifically, I found this in this thread (https://community.esri.com/thread/191678-arcgis-data-store-and-rdbms#comment-672633 ) Release of the Deprecated Features Plan for ArcGIS 10.5.1 | Support Services Blog ArcGIS 10.5.1 is the last release to support anything other than the Data Store product as a data store for a Hosting Server. So, from where I sit (the CIO seat - so I'm no expert), this kind of language suggests that there will be functionality available thru the Data Store technology that won't be available in legacy configurations. As I think about it, this part of my original question is moot. Until there's a supported way for me to see what's inside the Data Store, I can't use it anyway (from a HIPAA compliance perspective) since it's a bit of a black box. And this won't happen until enough HIPAA-covered entities come to the same realization. So thanks for your help. We're going to give some of your non-supported suggestions a try and make a determination if they'll ever be officially supported.
... View more