Okay, I need to check if anyone else experienced this or if I'm just dreaming Survey123 dreams…
A couple of weeks ago, I published a Survey from Survey123 Connect, using an existing Portal-hosted Feature Service via submission_url — and I swear the resulting Form item landed in the same Portal folder as the feature service.
It was beautiful. Clean. Organized. Rational. I didn’t expect it — in fact, I thought the only way to make that happen was via Python — but there it was.
But now… not only do new surveys go back into "Survey - [Name]" folders, but even the ones I remember being properly placed seem to have magically migrated back to their default survey folders. I didn’t move anything. No one else did either. What is happening?!
Did I catch a glitch in the Matrix? Did something change in the latest Survey123 Connect or Portal patch? Is Portal “cleaning up” behind the scenes?
We manage a lot of projects. Every project has at least 2 Survey123 forms, and many have 10–12. That means we now have 67+ “Survey - [Name]” folders cluttering up our Portal content structure.
It's extremely difficult to manage project content this way. We’d much rather have the Survey Form live alongside its associated feature service in the same project folder — especially when we’re reusing an existing service via submission_url.
Has anyone else seen a Survey123 Form land in the same folder as the source Feature Service (without scripting it)?
Could Portal or Survey123 Connect have moved those Form items back on their own?
Any workarounds or scripts people are using to enforce folder placement?
Is there any way to influence this behavior from Connect? Or is Python the only reliable way to manage folder organization?
I'd love to see future versions of Survey123 Connect give us a folder picker or the ability to match the feature service's folder — especially when publishing against existing services. Until then, I guess I’ll keep dreaming… 😅
