You're in ArcGIS Pro. You're working with a hosted feature service with a lot of complex features, for example Tax Parcels. You make some intricate selections based on attributes and spatial filters, including some manual lasso selections.
- You create a layer from your selection.
- Symbolize, update labels, set rendering scales.
All is well in the world.
But how do I share that with a colleague?
Oh, I'll just save the map and publish.
ArcGIS Pro: I'm sorry, Hal. I cannot do that (current web layer changes will be lost - selections not supported).
Maybe I should just publish a new service.
Logic: But then I have to manage the same data twice - I just want one Tax Parcel service.
Well, there is no easy way to make this a view because the tools to make views are limited to attribute and multiple, different spatial filters including areas of manual selection. It's so much easier to do this in ArcGIS Pro. Oh well, time to do some hand crunching.
But, what if you didn't have to? What if all that work on selecting your features could be preserved by creating a hosted layer view using the selection parameters? The selection criteria definition could be passed to the hosting portal to create a hosted view of the parent layer and the new hosted layer view item would be shareable, and no extra copy of data would be required.
I dream of such a day, as I stare at the near 10,000 tax parcels I have selected using multiple methods, and now I need to recreate in a hosted layer view... by hand... again.
