Use the same Portal item id when publishing a web layer from Pro on different Portals

[PatriceLabbé]

Hi,

Since this previous idea has been implemented (Add "Save As SD" to overwrite an existing service - Overwrite Web Layer), we're looking for more consistency between our different ArcGIS Enterprise environments (dev - staging - prod).

We would like to be able to keep the same Portal item id no matter the destination Portal.

We think a pre-generated list of item ids should be added to the .sd file so the values would be sent to the portal for the different types of services (ex : Feature Services, Map Image Services, OCG Services, etc... everything with an item id). This way, we would have the same item id between environments.

Another way of doing this would be to improve the ArcGIS API for Python's Server.publish_sd function. The 2.4.0 version already allows us to set an item_id for the main type of service but not for related capabilities (ex : WMS, etc.). Maybe a dictionary of service_type:item_id could be the new parameter type?

Another option would be to add a way to modify a portal item id. But we would have to alter portal items once the have been published...

Thank you!

[JonahLay]

Thank you for sharing this idea and describing the need. This functionality will be available in ArcGIS Pro 3.5. 

[PatriceLabbé]

Hi @JonahLay,

Thank you for quick answer! Is it possible to have more details please?

[PatriceLabbé]

Hi @JonahLay ,

Any help on how all this has been implemented in ArcGIS Pro 3.5 and/or ArcGIS API for Python 2.4.1 would be very much appreciated.

I don't know where to find this after having downloaded and tried that new version.

Thanks!

[JonahLay]

Hi @PatriceLabbé,

The Upload Service Definition GP tool has a new Output Item IDs parameter that allows you to specify item IDs of the output web layers staged in the input service definition.

Hope it helps,

Jonah

[PatriceLabbé]

Hi @JonahLay, 

So I understand item IDs aren't saved within the .sd file...

I don't see the same functionality as the Upload Service Definition GP tool with the ArcGIS API for Python. We actually are using publish_sd on Azure DevOps agents (no ArcPy). Is importing the toolbox would be a solution (see Using geoprocessing tools | ArcGIS API for Python) for us? To do so, ArcGIS Enterprise 11.5 would have to expose it or we would need to execute the tool and then publish it as a geoprocessing service on each ArcGIS Enterprise environment (dev - staging - prod)... a bit of an overhead.