Ability to Group Layers for Publishing in Portal

DGessman_USF

Currently working with Enterprise 10.7.1. I am looking to find a workaround for being able to publish layers so that they are grouped within the Feature Service. I would also like them to still have a direct connection to our SQL. Since we have so few data editors, I am looking to do edits in PRO against our Enterprise GDB or Portal and still have that connection.

Todd_Metzler · ‎04-08-2021

Hello,

Suggest Share a web feature layer 1st.

Here's a suggestion. In your ArcGIS Pro project map, in the contents, highlight all the layers you want to group in one service, select Share, Web layer, Publish Web layer. Looks like this when you are done. Of course, my example is a hosted feature layer, but your referenced service should look the same.

ThomasEdghill · ‎05-17-2021

This functionality seems to be already offered in ArcGIS Enterprise but please let me know if I've misunderstood the request.

As @Todd_Metzler mentioned earlier, you should be able to use Pro to select multiple layers in the map, and share them grouped together in a single service to ArcGIS Enterprise. This includes feature services which reference data stored in an Enterprise Geodatabase. Pro can then be used for editing these layers. Feel free to reach out if you have any questions. Thank you!

Kevin_MacLeod

Once you federate, unless I'm missing something, the only way to publish is to a "hosted server". And then it does not allow Grouping. At least for me. I'm on 10.91 and Pro 3.3.1. Like many things in ArcMap and classic Viewer, what was simple is now complicated. Instead of just Grouping and publishing... it appears that now we have to Publish a bunch of loose layers and then in New Map Viewer manually regroup them. Will Grouping eventually be supported by Pro and Enteprise? Perhaps at Pro 3.4ish and Enteprise 11.4? I hope it is on the roadmap.

I am not using new map viewer. Not only is the UI more extra clicks and takes more screen space, but it still lacks ability to use referenced related data in many ways old viewer can. (Try it in forms) I hope focus on 'plumbing' can happen in 2025. Related data, basic Server functionality, catching Exp Builder up to WebApp Builder etc. I know it'll get there.