topic Re: Viewer user type creating a feature report on behalf of another user? in ArcGIS Survey123 Questions

Viewer user type creating a feature report on behalf of another user?

Jay_Gregory — Thu, 20 Mar 2025 17:41:06 GMT

We have some managers who have the Viewer user type in our ArcGIS environment, but still want to pull feature reports for surveys done in their division. Without upgrading them to Creator user type just to pull feature reports occasionally, is there any pattern where a Viewer can create a feature report on behalf of another user? I'm thinking a way to authorize the Feature Report widget in experience builder to use the owner's content and credits for feature report. Or possibly some other pattern that can get us around this issue.

At first I thought web tools might work, but Viewers can't run web tools. Any other suggestions?

Re: Viewer user type creating a feature report on behalf of another user?

abureaux — Thu, 20 Mar 2025 18:40:05 GMT

I create Feature Reports and then attach them to the layer. Then that layer is available in a web map for users to download the attached FRs.

Alternatively, there is an on-demand widget for Experience Builder to create Feature Reports now. I find this to be iffy at times, which is why I prefer to just automatically make them and attaching them to the FL.

EDIT: Also pretty sure there is a new view in the S123 website dedicated to FR generation that viewers may be able to use? I don't use that feature and I never direct users to that web interface as I find it too clunky for end users.

Re: Viewer user type creating a feature report on behalf of another user?

Jay_Gregory — Thu, 20 Mar 2025 18:57:40 GMT

Thanks - interesting idea. Though in our case they need to be created on demand since the data is updated often. Creating a new feature report after every update is a bit much.

Re: Viewer user type creating a feature report on behalf of another user?

abureaux — Thu, 20 Mar 2025 19:50:07 GMT

In that case the new widget sounds perfect for you.

For any normal application, it works beautifully. However, I will warn that I have had trouble with it on massive surveys (E.g., surveys with >60 repeats). But even in that case, it may have just been a bug as it worked as expected after republishing.