Publishing warnings when updating a survey in ArcGIS Survey123 Connect

[AlexFB]

I have been requested to make changes in an already published survey for staff to record and organize projects, tasks and other info. These changes were mostly adding/removing fields and setting new definitions for choices. The survey has a main feature service layer for general information, and a related table created by the "repeat" type for tasks and deadlines.

When publishing the survey to update, it prompts me a warning that the feature service is not compatible, the related table is not found and republishing the survey will cause the previously collected data to be permanently deleted (see picture below).  What did I do wrong? Is there a way to correct this? Any alternatives on how to deal with the situation? The goal for this is to update a published survey with no changes to the previous data.  Thank you.

[ToddW_stl]

did you happen to rename the repeat to "deadLine_tasks"?  it seems like the issue is that the name of something changed that doesn't match the existing feature service layer or table name.  can you share the xlxs form, or screenshots of the repeat name, layer/table name from the hosted service, and your submission_url from from the settings tab?

[AlexFB]

I didn't rename the repeat nor the layer name.  I kept it the same as it was.  
Layer name: Form_3
Table name: deadLine_tasks

   

The submission_url field is empty.  Looking for more information about this.

[Neal_t_k]

Can you take a screen shot of the schema of the feature layer in ArcGis Online, Unless you already overwrote it, it should be the original schema, you can then compare.

[AlexFB]

Attached are the screenshots of the schema (both layer and related table) in AGO.  I haven't overwritten it.  There are fields that have been added and others that have been removed, as per the request I was given.  Some edits in the display name as well, but not in the field name.

[Neal_t_k · Accepted solution]

Your table name in the AGOL is "DeadLine_tasks" and in your new schema is "deadLine_tasks". They have to match.

[AlexFB]

Thank you so much!  Even a small nail can derail a train.