Copying and Pasting from old table into a new table

[ScottJones1]

I have a Survey123Connect, where all the questions are the same, however I wanted to add a 'repeat'. If I did this with the current survey, I would lose all data upon publish.

Option 1, is a new question with a select Multiple, this can work but I am scrolling up and down the list to select the necessary selections.

Preferred Option 2, is to create a repeat with an 'autopopulate' However this requires publishing a new Survey with no old data.

If I do option 2, is there a way to copy and paste the old data into the main sheet? then continue with future entries having the repeat table populating. I am guessing I could go back and find the Parent Guid for individual entries.

[jmaxwell_braun · Accepted solution]

I'm trying to figure out how to migrate data under your Option 2 right now. Need to replace data after adding a repeat to a Survey123 form.

The logical assumption would be to download your existing data as a file GDB, republish the survey, then run the Append tool in Pro to copy the old data from the file GDB into the new feature service. However, you have to make sure the original global IDs are preserved to make the related tables carry over properly. That's where the trouble comes in. The append tool doesn't support preserving global IDs unless a unique index exists for the global ID field. Unique indexes are not supported in file geodatabases.

There are workarounds involving mobile geodatabases and enterprise geodatabases here: Preserving a GlobalID while moving data between Fe... - Page 5 - Esri Community.

Let me know if you make any progress on this. It's insane that something so reasonable has to be so difficult!

[JL_NWS_GIS]

I, too, am having this issue and thought Option 2 would be a logical approach. I was also thinking that the "Update Data" in AGOL would work. I have yet to try it, but it seems like it might be similar to the ArcGIS Pro approach.

I agree with your statement wholeheartedly: "It's insane that something so reasonable has to be so difficult!"