Add repeat to published survey?

[RHammers]

Hello! I would like to add a repeat to an already published survey, but I can't seem to do so without it deleting the existing feature service. That's bad enough, but even worse is that it would also then break my dashboard.

Is there a way to add a repeat without having the feature service deleted?

[ChristopherCounsell]

Unfortunately no, you can't add new layers or rename tables to the Hosted Feature Service.

https://doc.arcgis.com/en/survey123/desktop/create-surveys/updatesurvey.htm

You could back up your data, recreate the layer, and then append the data back. Some care in rebuilding maps and apps that use the layer.

[RHammers]

@ChristopherCounsell Could I duplicate an existing table and rename it?

[ChristopherCounsell]

Add a table as in the repeat?

You cannot add a repeat or change the name of one, without overwriting the existing service.

[DougBrowning]

Yea its a no.

Some things

You can use AGOL Assistant to swap out the Dashboard data sources I think.  They also were talking about a way to flip the sources but not sure its out yet?

Before you do anything export a GDB of the service!

You can let it wipe the service and then append the old data with Pro from the export above.  

You can make an all new form then copy over with Pro from the old service directly.  This is usually a good plan since you can time a decommission of the old form.  

You can point the old form to the new service but no real point in that.

This is a major schema change so not much way around it.

[RHammers]

@DougBrowning Thanks for the info! There's actually no real data in this particular feature service, I'm still developing the survey/dashboard/feature reports. I just don't want to have to reconfigure the dashboard and reports again. This would be the third time.

This has happened in the past where I'm putting together a survey, realize I need an additional field, and run into issues adding that field since I've already published the survey. I would hold off on publishing, but I also need to make sure that the survey is displaying as expected from the end-user perspective, and for that it needs to be published because I have found that things often don't display in the field app/web app as they appear in Connect.