Survey123 Create Report action in Microsoft Power Automate (Preview)

[IsmaelChivite]

[Updated July 2023: Added new note with link to a more recent and complete video]

Note: You may want to watch this video instead for a more recent take at this functionality

Just a few days a new Create Report action was added to the ArcGIS Survey123 connector for Microsoft Power Automate. While this action will not be officially documented or supported until the upcoming February 2023 release (currently planned for February 22), you can start playing with it now.

The video below will give you a quick tour to get you going. Enjoy!

If you have any feedback, please let us know by posting a comment below or adding your comments to the Survey123 Early Adopter Community website.

Note:  Since this action was added to the connector, some of you have reported that any flow previously authored from a Microsoft Power Automate template, stops working when you edit it. To resolve this issue, the Survey123 connector needs to be deleted from your flow and added again.  We are working to understand if this problem can be prevented or not. 

[Eimear]

Thanks for the info Robert 🙂 

[ModernElectric]

Thank you for the information and the video, has been a real help in designing my workflow. One of the issues I am having, and not sure if its something in Power Automate or the Survey123 Connect app/excel I need to do. 

In the time fields, it allows the user to enter the time normally (ie 8:05 AM). However, when the report is printed, either from Survey123 (website) or thru my workflow in Power Automate, the time comes out in military time format. Looking thru the syntax, it doesn't allow me to format the time, as I can with a date entry. Any idea how I can fix this, since it was asked that I format the time entry on the printed PDF report to not be in military time.

Thank You

[nnolasco]

Is there a workflow for this using Survey123 connected to Enterprise?  The issue is that from within the Enterprise connection the file has to be saved directly rather than being saved within Portal, thus there is no URL to download from.

[FionaNicholls]

Hi, I have used this flow twice successfully and then added to it, as I wanted to copy the reports from my OneDrive to SharePoint for access by other users in my firm.  I am finding that the survey123 reports consisting of only 1 page copies and opens successfully in SharePoint but the Survey123 reports from another survey consisting of 3 pages will not open in SharePoint.  I am having to manually recreate the reports in Survey123 connect and overwrite the pdfs for them to open.  Are you able to have a look at this with me?

[RobertAnderson3]

Hi Fiona,

Just to confirm, you have Survey1 using Flow1 successfully creating Report1 which is a single page works properly and opens in SharePoint.

But on Survey2 using Flow2, it creates Report2 which is multiple pages and it does not open in SharePoint? And when you run the report manually and the output opens fine?

Does it provide any error messages when you try to open it? Can you share screen captures of the flow that's not working properly?

[FionaNicholls]

Hi Robert

Thanks for responding to my message.

Attachments are as follows:

Screenshot of error message when opening the pdf "...no preview available".
When I try to download the same pdf "...can't open this file".
I have attached the 3 page and 1 page reports that I am creating. The flows are the same but of course use different template.
In the zip file I have included snippets of the flow and the paths where the reports are saved.

The report is created, saved to my one drive, (where it opens just fine!), then it takes that path and copies the file to SharePoint for all users to access, (where it doesn't open).

I am manually having to open the surveys in Survey123Connect and overwrite the pdfs in SharePoint for the team to view them.

I have scoured the settings to see if there is some feature about multi pages but haven't been successful in finding anything to help.

[RobertAnderson3]

If you meant to include attachments to your reply it seems you forgot to attach them or they got lost in the ether. But it seems that the issue is somewhere in the Get file content or the Create file if it works fine when it's put into your OneDrive! It's odd that it only happens with multi-page reports though.

This screenshot shows these steps in my flow. However I don't currently have any reports that really go multiple pages (tables will make them multiple pages on occasion) and I much more often export my reports using the docx (Word Document) format as it allows changes to be made later in the work flow more easily.

[MariusVerdes]

Hi,

I am trying to create a Power Automate flow to automate a report creation based on the above tutorial, but I am getting an error, please see the message below:
"

{

    "statusCode": 400,

    "headers": {

        "Cache-Control": "no-cache",

        "Pragma": "no-cache",

        "Transfer-Encoding": "chunked",

        "x-ms-request-id": "2f9989ee-93a1-4269-95c3-ffef68d53016",

        "X-AspNet-Version": "4.0.30319",

        "X-Powered-By": "ASP.NET",

        "Timing-Allow-Origin": "*",

        "x-ms-apihub-cached-response": "false",

        "x-ms-apihub-obo": "false",

        "Date": "Wed, 31 Jan 2024 13:23:19 GMT",

        "Content-Type": "application/json",

        "Expires": "-1"

    },

    "body": {

        "status": 400,

        "message": "A value must be provided for source path.",

        "source": "api.connectorp.svc.ms"

    }

}"
Does anyone else have this issue? If so, how did you manage to resolve it?

I tried the solution proposed in this thread, as well, but I am also getting an error...

Thanks in advance for any suggestions.

[MariusVerdes]

And, for more context, this is how my flow looks like:

Where the URL from the Upload file from URL (OneDrive) is the "URL of the first result file"

[SeanNagy1]

I am running into the same error. Ive had no issues previously and now it wont upload the file from url. When i try to edit the flow it then trys to add an "apply to each" function for some reason. Did Power Automate make a change that messed up these flows?