Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Service Cloning renames Feature Service URL unnecessarily #1835

Open
shane-pienaar-gbs opened this issue May 23, 2024 · 0 comments
Open
Assignees
Labels

Comments

@shane-pienaar-gbs
Copy link

shane-pienaar-gbs commented May 23, 2024

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants