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 Dynamic Choice List with Pop-up Geopoint Passover Not Working

Adam_Bourque

Hello everybody, I have been working and evolving this Hydrant flushing survey to include both clicking on the hydrant to flush then being able to generate a list of residual hydrants hopefully just using arcade expression / advanced S123 functionality. I took this recommendation to use dynamic choice lists from the S123 guru's themselves @BrettStokes and @IsmaelChivite at the ESRI USer Conference. Using the buffer option, it is able to pick up the other Hydrants and filter out non-operating hydrants.

However, I can only get the dynamic list to generate the list if I manually enter in the geopoint, it will not read my passover geopoint value that is generated by default opening the Survey. Can I alter the arcade expression to allow this functionality to work fully? I see that when I click on the point it maybe geocodes / generates some additional info that is used in the dynamic buffer that does not work with my popup pass?

I tried to use "calculate" to reference the geopoint field but that did not work. If I need to share more info /elaborate please respond and I will happily do so. I shared a skimmed down version of my survey123 form and took screenshot of expression but I can share anything else more you need! Desperate to have this work fully, so close.

UPDATE: Spreadsheet updated

Thanks!

S123 spreadsheet share2.xlsx

geolocation.png

S123 Discovery Bottom Left2.png

S123 Discovery Bottom Left.png

ReneRubalcava_0-1723475603267.png

MelissaSalich_0-1723475566692.png

7G1A7708.jpeg

ZachBodenner_0-1723475487300.png

Find more posts tagged with

Accepted answers

All comments

LaurenceTait

Your xlsx sheet contains dozens of errors.

Adam_Bourque

Sorry about that, I was trying to make a very slimmed down version to highlight just the part of the survey that was experiencing issues and made lots of issues in that version. Here is an updated form, could you please re-review. I can also send you the full original survey form if this one has any issues but I did test the copy this time.

S123 spreadsheet share2.xlsx

Adam_Bourque

Also just to reiterate, everything in the survey seems to function properly when I manually click my own geopoint "under location information group of my survey" (screenshot attach shows). However, when I let the pass through from AGOL with arcade expression autoassign the location, it does not refresh the "Residual Hydrant" list on my survey, says 0 results instead of this 1 result.

Is there a way to "refresh" the geopoint question so the dynamic select question can pull from that question properly? Seems like the only way "intersects" with geopoint can work is if I choose the location within the form. If there is a way for S123 to trick this behavior with a repeat or something I am all ears, but even my repeat attempt with a calculation did not work 😞 @LaurenceTait @BrettStokes

S123 works kinda.png

LaurenceTait

There is a fairly simple way to force the location to update using a repeat. See this question: https://community.esri.com/t5/arcgis-survey123-questions/how-to-hide-map-in-geopoint-question/m-p/1190226

But before going down that path, can you make the changes in the attached xlsx form and let us know the result?

I suspect this has something to do with the order in which the calculations are being done. You're basically asking the form to restrict the list f hydrants based on the geopoint, but that may be happening before the geopoint is actually calculated, hence no valid results.

Hopefully, if you base the restriction on a series of calculations, rather than direct off the geopoint, it will evaluate in the right order.

Form 6.xlsx

Adam_Bourque

Hey Laurence, thanks so much for the response and trying to help. Inching closer to an ideal workflow; however, still resulting in a hiccup. I have to click the "x" on the additional geopoint now and then "refresh" until the list generates any results.

I will look into the other path next, while not as ideal as an automated form solution, it is still better than what I have right now. I will still be open to any other solutions / updates but will try to let you know tomorrow if I have success with the button at least!

(Also I tried including default with the filter for operable hydrants but the user would have to change or click yes or no themselves which I guess is the same principle as the repeat button).

s123 reply.png

Adam_Bourque

I feel like we keep inching forward @LaurenceTait , but the problem now is back to an old one I ran into.. I have to manually change the filter response by either clicking "yes" then "no" and then "yes" again for it to generate a list with the filter instead of having to close down the geopoint.

I don't need the filter option for non-functioning / functioning hydrants but if it even worked by having to click "yes" at this point I would be more happy then having to click it multiple times.. I can see too every time I change the filter option the cloud appears where the magnify glass (in the final generated residual hydrant list within 10 mile buffer).

Appreciate the help, really just want to be able to put this form to rest as I am so close to it's fully completion, any other ideas?

Adam_Bourque

B.U.M.P.

Adam_Bourque

I guess since there is no good resolution for this workflow I will have to create attribute filter "dynamic lists" based on Hydrant No to pickup other Hydrants from that sequence as the buffer output is just too glitchy in working properly. Or probably the better alternative is for me to create polygons with flushing zones and use that as part of the searchType

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

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