I'm new to using Experience Builder but I've been creating and publishing maps services for many years using ArcGIS Server and even as far back as ArcIMS. I can't seem to understand why a hosted feature layer is not considered a "supported data type" for the map layer widget in Experience Builder. Why are feature layers treated any different than a full map service with one or many layers (i.e. a Web Map)? A hosted feature layer can be viewed in the Portal for ArcGIS Map Viewer and Classic Viewer. Why can it not be used in a front end generated in Experience Builder?
Your question touches on the nuances of how different types of GIS data are managed and utilized across various ArcGIS platform components, including ArcGIS Server, ArcGIS Online, and ArcGIS Experience Builder. The distinction between a hosted feature layer and a map service (or a Web Map), and their support in Experience Builder, primarily revolves around how these resources are designed to be used within the ArcGIS ecosystem. Let's break down the key points:
If you continue to face challenges, consider reaching out to Esri Support for more detailed assistance, as there might be specific issues or configurations unique to your environment that are affecting the integration of hosted feature layers into Experience Builder.
@FredericPoliart_EsriAU Thanks for the feedback. In my case I think it might be a little of all that you mentioned. I'm working on a disconnected network so our systems do not get updated as quickly as most. The system that has the most recent version of ArcGIS Enterprise is at v11.1. I'm mostly interested in leveraging an external Feature Layer service within Experience Builder. When I add a connection to the service via URL connection in the "Add Data" component of Experience Builder it sees the service and exposes the layers within it. The map widget doesn't recognize these layers as a supported data type. So, what widgets within Experience Builder will allow me to add these feature layers as an overlay within the Map view, and toggle the layer visibility (similar to those that are added via web map)? It seems counterintuitive to have to mask the feature service within a Web Map service.
I am attempting to add a Portal 11.1 Feature Layer to Experience Builder and use the Near Me widget. There must be bugs. This is so frustrating. The Near Me widget even saw the layers briefly before reverting back to saying "This map does not contain any feature layers. Select a map with at least one feature layer".
Esri's example I'm following uses a hosted AGOL layer. I'm going to test with a hosted AGOL layer. I bet it works. There are frequent problems trying to use Portal with AGOL.