This past fall, I successfully created a survey in Survey123 Connect that points to a pre-published feature service containing two SQL Server point feature classes and two SQL Server tables. The two tables and one of the point feature classes relate to the main point feature class through a relationship class. I am now trying to build another survey that uses a different feature service but will eventually reference some of the same point feature classes and tables referenced in the feature service of the survey that I built last fall.
To get started with building this second form, I was hoping it would be as simple as copying the first form that I had built in Survey123 Connect by clicking on the 3 dots next to the form in Connect, clicking "save as", and creating a new form with a different name. I then changed the title of the form, the submission_url parameter to the new feature service I've built, and have been attempting to publish with no luck. When trying to publish, Connect always hangs at this screen-
A folder called "Survey-TESTING" is successfully created in Portal under my username, but nothing is then added to that folder.
What's strange to me is that, as of now, my new feature service is identical to the first feature service I made, the only difference is that it has a different name. And, in the new form that I'm trying to create, I haven't changed anything besides the submission_url parameter and the title of the form. I figured for the sake of testing purposes, this would be the best way to go by making very small, incremental changes to the form and to the new feature service, but I'm not even able to get past this first, seemingly elementary step.
I have also tried building a very simple form from scratch that references the new feature service, and I get the same result. I have tried uninstalling/reinstalling Survey123 Connect, trying the latest version and previous versions of the software, all to no avail.
Has anyone had success doing what I'm trying to do? Perhaps connecting more than one feature service to the same feature classes and tables isn't best practice/not possible?