-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Description
Describe the bug
Cloning a Feature Service with a GUID in the name (e.g. as generated when Survey123 creates a Hosted Feature Service) from one Portal instance to another results in the renaming of the service name at the target, even if the end service name does not exist at the target.
For example:
https://source/../Hosted/**survey123_adfdf243f6be4944bbc46ab1b2d75d7f_results**/FeatureServer
becomes
https://target/../Hosted/**survey123_e09d2_results**/FeatureServer (or similar)
To Reproduce
Use .clone_items(clone_items, copy_data=True, search_existing_items=True) to clone a Survey123 source Hosted Feature Layer to a new Target portal
error:
N/A
Screenshots
N/A
Expected behavior
If the service name does not yet exist at the target, it should remain the same as the source.
Platform (please complete the following information):
- OS: Windows
- Browser : NA
- Python API Version: 2.3.0
Additional context
If I monkey patch ../clone.py, line 2945 as follows, no renaming occurs:
if not self.target.content.is_service_name_available(name, "featureService"):
name = self._get_unique_name(self.target, name)