nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Re-publishing Survey123 Connect

Almaz_Naizghi

Hello,

I made some minor changes to the survey I designed in Survey123 connect and would like to re-publish it to AGO, but I got the following warning. I have done this in the past without any issue, and I am not sure why I am getting the warning now. Could you please assist me in resolving this problem?

Thanks!

タグ付きの投稿をもっと見る

Accepted answers

All comments

JayasriB

I would suggest revert the conflict, extract the data to a file .gdb or csv, then delete the old survey or feature layer from your AGOL content. Return to survey124 connect and click publish.

May I know which edit caused your this error?

Almaz_Naizghi

Thank you for your suggestion. But this process will not work for my workflow.

I made some minor changes, such as tweaking the label for some of the survey questions and the form title.

Neal_t_k

@Almaz_Naizghi did you change any of the question types while leaving the field name the same, i.e. from text to a number or something like that that usually triggers an overwrite warning you are seeing. as the feature service is no longer compatible with the schema coming from the form. The only options are to change those questions back to the original type, or download the existing data, overwrite the database and append the data back after fixing any data type mismatches.

Almaz_Naizghi

I didn’t change the type (schema). The only changs I made were the label of the survey questions and the form title.

Neal_t_k

Not sure if this will work, but do you have a form_id set on the settings page in your xlsx. Try setting the form_id to the exact name of the main layer of your Feature Service. I am thinking if you didn't have a form_id set it may take the form title as your id, and if that changed then the matching up the tables may be no longer working. Worth a shot.

Almaz_Naizghi

I tried but didn't work.

Neal_t_k

That part of the screenshot you redacted, should give some clues on what is causing the issue. I am guessing something like Table <Table Name> not found? That would point to either the main table name being different than the feature service main table name or a repeat group no longer matching. You will need to fix that; form_id on the settings page, or repeat group name if it is a repeat table.

会話に参加する

サインインしたメンバーは投稿、更新のフォローなどができます。初めてですか？無料アカウントを登録してください。

クイックリンク

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.