URL parameters stopped working, partially

[AnninaRupe1]

All:

I have a survey (created using Survey123 Connect) I launch from a URL in a pop up. I have configured the URL to include parameters to automatically populate survey responses. This has been working for a while (1+ years?) but just noticed that a couple of the questions I have included parameters for aren't being populated. They are in a group in the survey, are integer field types, and the source and destination field names are the same. The parameters are in the middle of the URL; parameters before and after work fine (including other questions in groups). The data even display in the URL but they don't show in the survey fields. I've tried the following:

• Clearing browser cache
• Re-publishing survey (from Survey123 Connect)
• Changing all fields in the source hosted feature layer in the web map to not use thousands separators (not just the fields I'm having trouble with)
• Submitting the survey even though the fields aren't completed to see if they might populate the table (they don't)

I've attached screenshots of part of the URL and the portion of the survey where it should be written. Note: I have the "Enable Draft Mode" setting turned on due to random submission failures. This needs to stay on. I have tried resetting the page and it still doesn't populate.

Any ideas or if this might be a bug with a workaround?

Annina

[abureaux]

My first instinct was special characters in the URL. That can break these URLs. To resolve the issue, you need to encode the URL. But, the fields on screen all look very basic.

Two quick things to try:

1. Rearrange the URL and see if that changes where it breaks (if it does, that likely indicates something in the URL is the culprit),
2. You can always try taking the complete URL, dropping it into a URL encoder, and trying that to see if that magically fixes it.

If those doesn't work, this may be a new bug (in which case I'd suggest reporting it).

[AnninaRupe1]

Thanks for the suggestions!

Both don't work so I'm contacting support. I'll update the post when I receive a solution!