Manage 15+ surveys when you need to download report/excel everytime

Question

Hi everyone,

We have started utilizing Survey123 here in our local District and want to take it region wide but the issue we're stuck at is this: There is only one account to use for creating surveys, it will be shared with 3 people who will get email notifications in their respective Districts (there's 3 Districts) also the responsible managers for that survey gets notified. We 3 need to download the report and excel data and email it to the correct managers again. We would be receiving email notifications constantly from the 15+ surveys! Ideally, we wouldn't need to go into the Survey123 website for that specific survey and manually download the report/excel, it would be attached to the email notification. We are trying to have one location (web map) and a single method that people go to for submitting different surveys. Is there a workflow someone can share with me to figure this out? Or a workaround to get reports/excel attached to the emails? We're using Microsoft flow.

Thanks for any help

JamesTedrick · Answer

Hi Kassandra,

This can be possible with some advanced configuration.  In particular, you currently cannot use the Survey123 Flow connector as it does not support transmitting the token as part of the workflow, which is needed to accomplish this. You can manually set up a connector using the generic 'Request - When a HTTP request is received' trigger.  After that, the generation of an Excel document with the record can be accomplished with the Export Item REST endpoint (Export Item—ArcGIS REST API: Users, groups, and content | ArcGIS for Developers ).  This is an asynchronous task, so you would need use the 'Do Until' featured in the caller flow at Pattern & implementation for making long Async Http calls in Microsoft Flow : (part 1 : polling) | Serge Luca's Blog (Sh… .  The same can be done for report generation, though at this point the the API has not been documented (we are awaiting final release, as we may need to change parameters while in beta).