Kelly Gerrow
On-prem Feature layers are too slow in my testing. The double layer name listing is still an issue for me.
Adding sublayers ie layerpath/0 always adds it as a featureLayer. This appears to be a limitation of either the webmap or REST API. Most of my layers are too heavy to work as feature layers. I've tried webGL, scale dependency etc. And feature service tiling on-premise still seems not to be in Server 10.7.1. I can't store data on the Esri cloud as feature layers, as it has no grouping. Only way for me to use layers which load fast and have grouping is map image layers.
I would settle if there is an elegant programmatic way in WAB Dev Ed to remove the top-level service name. From the Layer List, but hopefully also Query, Print and Legend or anywhere else. But the main area to remove them for me would be LayerList. Thoughts?? I am thinking the only thing I could do now is make the name blank at the service level in the webmap although I don't think it will allow spaces, though I could use a character.