After upgrading my ArcGIS Pro to 3.3, I keep getting this error when survey tries to generate report:
ERROR: 'Survey' object has no attribute '_stk_url'
Any help is greatly appreciated.
Hi Zach,Has a bug been logged for this? I can't find one.It is June 2025 - I've added two patches to ArcGIS Pro 3.3 and the problem persists.Is there a specific patch I need to add?Thanks
We do not have a results feature service view. Is that something that I need to enable somewhere? We've never had a need for such functionality- we simply have a feature service and a map service published off of a SDE feature class, and obviously use the feature service for report submissions. And yes, the user can export reports from the data tab in the Survey123 website, but no one can export records (since the feature service is non-hosted).
Hey @MattLayman,
To verify the user trying to run the script has the _results feature service view (or _stakeholder if the survey is older) shared with them? This will be different than the parent feature service the survey may be submitting to:
Is the same user able to export reports from the Data tab in the Survey123 website?
Hi Zach- yes, our entire organization has the results shared with them.
Hey @mike_totti @AndrewThompson_SCE @MattLayman,
In the Survey123 website under the Collaborate tab > Share results, are the results of the survey shared with the user trying to run the script?
The method is trying to use the _results view to pass into the Survey123 report engine. Does the user running the script have access to the _results view?
Andrew- yes, this seems to be the case for me as well. Problem is, I want a user who doesn't own the form to have the ability to run a script that exports Survey123 results. Can anyone at ESRI advise on a workaround?
I found out what it was for me. You have to be using the owner of the form. I got that error when running it from ArcPro and wasn't logged in using the form owner.
I too have this issue- incredibly frustrating. @Ismael any thoughts?
I just got that same error. It was working fine the other day now I get that error. Did you get a solution to this error?
Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
