S123 unable to edit all fields in submitted forms

[OrrinFeril]

I'll get this started with: I'm relatively new to using Survey123, so this could be a simple fix.

Most of my surveys have been created using the web developer tool then linking them to Make to automate handling of reports etc. This seems to work just fine.

However, I noticed something odd a few days ago. Recently, I've created a new survey using ESRI's Survey123 Connect application. I noticed that once a survey is submitted, the end user cannot fully edit the survey on the website in the form view. In previous surveys developed on the web developer, users can fully edit the surveys on the website. Is this a setting somewhere?

We've noticed that we can see the full data payload in the data table at the bottom and in the form view on the right, but when we go to edit the survey, we cannot see all of the form fields. 

Further what's interesting is that when the Survey payload makes it to Make, not all of the fields are available for query. I don't know if these two things are related but it only applies to this new survey that was developed in S123 Connect. 

Secondary, we can't seem to find a way to delete pictures from this survey.

Any help would be appreciated as this is creating a bottleneck in our workflow.

[OrrinFeril · Accepted solution]

Well, good news/bad news.  I updated the field names to remove the _.  This creates a new field and keeps the old data in your data table. I didn't like having the old fields in the data table as I could predict it would confuse staff when editing the data table in the future. So I went through the process of copying the data from the old fields into the new fields using Calculate Field in ArcGIS Pro. This worked great. I then proceeded to go into delete the old fields in the data tab of AGOL for the hosted layer. This worked fine.

Bad news: When I went in to look at old data or edit old data in the survey, I was met with several errors because the survey was still referencing old data fields that were now deleted. 

So I went through the process of exporting the data to Excel and file geodatabase (per post). Then went through this process to extract the photos (per post). This worked great as I didn't want to lose old data.

I then used the XLSX template to create a new S123 survey in Connect. This gave me a fresh data table and my staff is now in the process of resubmitting old surveys to the new survey. Once this is complete and we verify old data is transferred, we'll delete the old survey and corresponding hosted features in AGOL.

Good news: The new survey that incorporates the fixes @DougBrowning suggested operates the way we want. We can see all data fields if we edit the survey in the form view. Secondly, this also fixed the issue with Make and the full payload is flowing through to our scenarios.

I know this was a long explanation of what we went through but I wanted to update the post with our resolution. Another user wouldn't have to do everything with the export if they weren't concerned about losing old data.

[DougBrowning]

Glad it worked out.  Not sure you will be able to submit old surveys to the new service though as the field names are all different then right?  May have to use Append tool in Pro mapping the old service to the new service field by field.  Download a GDB copy right away to be safe.  But it almost sounds like you overwrote the original service which I would not do.  I tend to build a all new spot then move the data over in Pro.

I have PTSD from getting burned on special chars for decades now.  It used to be common to always avoid them in the old days but now more are allowed (I even had spaces in a folder name get me last year), yet still weird things will come up and get you.  I know underscores are popular but being a char SQL uses a lot, I don't love them.  I do all of mine in CamaelCase.