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 Experience Builder widget in edit mode deleting hidden values

Rar_Katia

I'm building an Experience Builder with a number of surveys. One of the windows is the edit mode of a survey to allow my user to switch feature status from open to closed. The problem is that in my original survey, much of it calculates values behind the scene to not overwhelm the user with information, and these hidden values don't carry over after the edit is made in edit mode. I can reveal the values, but that makes them editable, and the same issue happens when the values are read only enabled.

Has anyone run into this issue? Is there a workaround? My concern is that I don't want my user to accidentally change the values by disabling read only, but there seems to be no other option.

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

Accepted answers

ChristopherCounsell

If it's a select_one question, drop down should be available

Try building a form in map viewer.

All comments

Rar_Katia

I will give all this a try. Thanks for the advice (both of you!)

Rar_Katia

Do you know of any how tos out there for linking the second form to the same service? I've never seen this done before.

Rar_Katia

Two values, first is marking the feature as closed and second is a date field.

The "Open" or "Closed" is used in a secondary survey via a pulldata so I'm trying to use a dropdown to limit the user's possible inputs. I don't think that can be done using the Edit widget, or can it?

dougbrowning

Just use the Submission URL on the settings page. It is not as hard as it sounds really. Just do some searches and you will get it. There is even a support article here https://support.esri.com/en-us/knowledge-base/how-to-create-survey123-for-arcgis-surveys-that-connect-000014793

Basically 123 just dumps data into feature services. You can connect to that service through as many forms as you want.

Test this on your testing service first of course.

Hope that helps

ChristopherCounsell

If they're just changing one value, you could add an Edit widget and use a
form to update just that one attribute. Not survey123.

dougbrowning

mmmm never seen that happen. I would take a look at either a second 123 form that has just this question in it that links to the same service. Or if it is simply that one status field let them do it in the attribute table or use a Web form linked to the same service then use the regular edit widget. Would be much simpler and safer so that no values are affected at all. If you want to be super safe you could even create a view that has just that field so the other fields are totally read only or hidden.

Rar_Katia

I definitely would prefer a different survey, but how would I set that up to update the original dataset? I have never made anything with webhooks/power automate but would be willing to give it a try if it's worked for others in the past. Is there a process you would recommend?

The reason I have it set up as a single survey is because I need to mark when those submitted features switch to closed. Hence trying to edit the survey data using the original survey.

Rar_Katia

It's the survey123 widget.

dougbrowning

Are you using the Field Maps/Web form Edit widget or the Survey123 widget? The regular edit widget is meant for the web forms and the Arcade expressions that go with it and will not run, or even understand 123 calcs. If you use the Survey123 widget then they should work. Two totally different systems.

ChristopherCounsell

If users are doing a different workflow (edit > closed), a different survey or app is easiest. Remove the questions, calculations, or set a body-visible parameter clause to hide them.

If it has to be the same survey, you can use calculation mode parameters to avoid re-calculating. whenEmpty. Or in the calculations, things like Once. But then users get stuck in the first survey, so the earlier option - different tool for different workflow - is best.

Připojte se k diskusi

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.