Select to view content in your preferred language

Survey123 Create Report Automation Failing

484
2
01-25-2024 07:16 AM
MariusVerdes
Regular Contributor

Hello,

I'm trying to set up a Power Automate flow with the Create Report function using a custom connector from our ArcGIS Enterprise 11.1.

However, after trying everything from this tutorial, I am still receiving an error at the "Upload file from URL"  (3rd step). Does anyone know how to overcome it? Or if there is a workaround?

I also found this thread in the community, but since I am a Power Automate novice, I wasn't able to follow all the steps.

My custom connector is working because I use it in another flow where I populate a predefined Word file with data from Survey123 and is refreshed every 14 days due to the token expiration date. 

Below is how my flow is currently structured:

MariusVerdes_0-1706195096287.png

MariusVerdes_1-1706195137496.png

MariusVerdes_2-1706195164196.png

Thank you in advance!

 

 

0 Kudos
2 Replies
abureaux
MVP Frequent Contributor

I have 2 recommendations.

1. To resolve your report issue, maybe try an HTTP Get after the report generation. Then, Use that HTTP step to upload:

abureaux_4-1706196592945.png

 

In my example, I am uploading to SharePoint. You can just replace that with One Drive.

2. The Create Report step is a self-contained Do Until. It will always "Do Until" a report is created. The issue is that it always succeeds even if report generation fails. As such, I would add this:

abureaux_5-1706196692725.png

Just be sure to choose this "status":

abureaux_6-1706196731510.png

Then, use a Condition. You want all of your flows "bulk" to be in the "yes" side of this condition.

abureaux_7-1706196760512.png

This is a simplified version of my flow, but really the most important parts.

0 Kudos
MariusVerdes
Regular Contributor

Hi @abureaux , 
Thanks for the suggestion. But when I try to replicate your first recommendation Power Automate automatically adds a "for each" condition to the HHTP GET (I use the "url" from the create report action to populate the field). Do you know why and how I can work around it?



0 Kudos