Cannot copy mapservice with settings from one webmap to another

[AntoonvanHam]

We have the following situation:

In GeoWeb old (Geocortex Manager) it was possible to copy a map service with configurations on map layers (popups, fields) from one website to another.

That was really practical because there are map services with many map layers and extensive configuration.

Question: The layout and configuration of a map service for a VertiGIS Studio website takes place in a WebMap in AG Portal.

Is it possible in AG Portal to copy a map service from a WebMap one-to-one?

In other words, a copy with full configuration like popups, fields, etc.

The question is not about copying a WebMap as a whole!

Note: We haven’t found a way to do this in AG Portal in a WebMap yet.

It seems like in AG Portal 11.5 the configuration must be completely rebuilt.

We see this as a step back compared to the map in the old Geocortex Manager, where a map service with configuration could be imported with one click.

With kind regards,
Antoon and John
city of Eindhoven, Netherlands

[AntoonvanHam]

Today i've been looking further into this issue. I've found that for feature layers it is possible to save and re-use them in other webmaps (with configuration). The thing is that within the city of Eindhoven we mostly make use of mapservices, rather then feature services. These mapservices can have many layers with extensive configuration and therefore it takes much effort to 'copy' this into another webmap. The few feature layers we have are hardly ever copied to other webmaps.

[WaterschapNoorderzijlvest]

You can accomplish this on the Portal server itself:

1. Note the id's of the webmaps.
2. Navigate to the Portal content folder (...somepath...\arcgisportal\content\items).
3. Open the itemid file within both folders (it's a json, but lacks a file extension).
4. With Notepad++ and the JsonToolsof JSTool plugin -> pretty print.

Now it is a simple matter of copy/pasting the correct sections.

Use this now and then for the same reason; ran into a limitation when adding a wms to Portal:

OGC WMS group layers are not supported. 

Which I didn't know of until I had already created a wms (in a different application) with some 150 layers in group and subgroup layers. With a few sample layers in the webmap and pretty print the structure was quite obvious. So edit, save and refresh the browser and the change is effective.

Note that there are layerid tags with (pseudo)random alphanumeric strings. Don't know whether they have to be unique, but just to be sure I do a +1 in the number part of the layerid when duplicating sections.