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; } } }

Survey123 Connect - publishing behavior - 401 vs ok to publish

jhodny@Newark.de.us_CityOfNewarkDE

Hi, I am using Survey123 Connect. In an existing XLS Form, I made one change, I added a default value to a select_one question. I saved the form. When I went to publish the survey, I was greeted with the 401 message. I canceled the process.

I then pressed Publish again, and was greeted with this message, A-OK to publish. I canceled the process.

I clicked Publish again and was greeted with the 401 message. I tried this a few more times and watched the messages toggle between 401 and it's OK to publish.

If I remove the default value, save the form, and go to Publish, I get the same toggling behavior. If I am in the 401 message pane, and accept the warning and publish, I will wipe out 600 collected data points.

The form version is 3.19, 27 February 2024. I signed out of 123 Connect, closed Connect, reopened and signed in, same behavior. I did not reboot my laptop.

Any ideas on why this is happening, and how to prevent it? Thanks in advance, Jay

Najděte více příspěvků označených jako

Accepted answers

jhodny@Newark.de.us_CityOfNewarkDE

I was able to resolve my publishing issue with Esri tech support, though there was no clear "aha" moment. We did create a new Connect survey using the XLS Form from the original Survey, as the template, and could publish with no error. The recommendation in creating a duplicate survey (in my case for testing purposes) was to create a copy of an existing survey using the XLS form as the template, and do not simply perform a Save As on the original survey. Another recommendation was to use short titles (length unknown but keep them short). A final recommendation was to upgrade to the latest 123 version, 3.22.

All comments

ZacharySutherby

Hello @JayHodny,

If you are using ArcGIS Enterprise configured with Integrated Windows Authentication you are likely running into BUG-000173543 or a variation of it. If you are using ArcGIS Enterprise, what version of Enterprise are you using?

jhodny@Newark.de.us_CityOfNewarkDE

Hi Zachary,

I will check into the bug. We are using ArcGIS for Enterprise 10.9.1. And we use IWA. Connect version 3.19, likely upgrading to 3.22. Not sure why this is occurring now, we have been using Connect and 10.9.1 for a few years now.

Regards,

Jay

jhodny@Newark.de.us_CityOfNewarkDE

Připojte se ke konverzaci

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

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