topic Re: Guide to Generate Feature Reports in Power Automate (Enterprise and AGO) in ArcGIS Survey123 Questions

Guide to Generate Feature Reports in Power Automate (Enterprise and AGO)

abureaux — Thu, 01 Feb 2024 18:32:07 GMT

This post describes the old manual method of generating Feature Report within Power Automate. Technically, this method does still work, but it is a LOT of extra work. There is a much easier method now! Check out my post above for more details.

I have tried to post this several times over the last few days, and it has kept failing. As such, I have opted to go with an attachment. My apologies for the extra download and mediocre formatting!

This is a guide for users new to using S123 in the Power Automate (PA) platform, and is a repost from an earlier post I made. That thread is kind of hard to follow now because I didn't start it, and this is also an updated flow to fix a bug with geopoint questions not working before. The guide fully details how to generate a feature report for S123 using PA.

Please let me know if you have any questions!

Environment:

ArcGIS Enterprise.

AGO has a new built-in connector. Just use that rather than trying a custom approach.

Requirements:

Power Automate Premium workspace.
Admin access to your Portal.

Scale:

This guide is for a simple one-step flow. I do not recommend this for large-scale deployments as it does not have adequate error handling capabilities. I use a two-step process which I can detail later. Basically, I dump the initial response from S123 into SharePoint and then process that. This will give you all the basics though!

Versions:

v2 - Updated step for the Do Until loop

Re: Guide to Generate Feature Reports in Power Automate (Enterprise and AGO)

abureaux — Mon, 18 Apr 2022 20:57:47 GMT

Just responding to myself so this can be marked as solved. If you try the steps and something doesn't work, feel free to respond though! I did test this today and everything seemed to be working. PA can be finicky though.

Re: Guide to Generate Feature Reports in Power Automate (Enterprise and AGO)

Aneel_Kumar_M — Thu, 21 Apr 2022 09:40:10 GMT

Dear abureaux

Thank you so much, yes, it is working with Geo Point.

It is solved.

one query, there is count in "Do Until" how is that helps? can we reduce it to 10 or 5 ? Please advise.

thanks & best regards,

Re: Guide to Generate Feature Reports in Power Automate (Enterprise and AGO)

Aneel_Kumar_M — Thu, 21 Apr 2022 09:42:28 GMT

Dear abureaux

It is solved.

yes, it is working with Geo Point.

Thank you so much,

Re: Guide to Generate Feature Reports in Power Automate (Enterprise and AGO)

Aneel_Kumar_M — Thu, 21 Apr 2022 09:47:12 GMT

Dear abureaux

How to remove this default link comes in the automated email from the power automate, as shown below :

thank you,

Re: Guide to Generate Feature Reports in Power Automate (Enterprise and AGO)

abureaux — Thu, 21 Apr 2022 16:54:27 GMT

Sorry. I don't recall seeing that email from my Power Automate. Do you get that from all your automations? This flow should only send an email if you added that step in.

Re: Guide to Generate Feature Reports in Power Automate (Enterprise and AGO)

abureaux — Thu, 21 Apr 2022 17:01:19 GMT

Count: 60

Timeout: Leave as PT1H

Thanks for the reminder. I will update the guide with this.

Normally this doesn't take more than a few tries. But sometimes is can be slow. I found that 60 is a good number, and it hasn't resulted in any unwanted timeouts for me. You don't want to go too low because if the Survey123 server takes a little longer to respond, you could have the flow give up before a success. Also, having a larger number doesn't slow anything down. As soon as the loop sees a success, it ends and carries on to the next step.

Re: Guide to Generate Feature Reports in Power Automate (Enterprise and AGO)

ISP_graynic — Tue, 26 Apr 2022 18:17:37 GMT

@abureaux Is there a way to have a feature report run on a layer that is not shared publicly in ArcGIS Online? I've got this to work in PA, but only when the layer is shared publicly with the settings below which exposes all responses to the general public. Basically I have a public facing survey where the "Editors can't see any features, even those they add" is selected so that the responses can't be viewed publicly, but when I have that setting PA errors out. It only works when I change that setting to "Editors can see all features" which exposes my responses to the public.

Thank you again for this post! It's a great tool.

Re: Guide to Generate Feature Reports in Power Automate (Enterprise and AGO)

abureaux — Tue, 26 Apr 2022 19:16:14 GMT

Hmm. That is not something that I have encountered. I can try and do some tests over the next week though.

What permissions does your service account have with respect to the survey in question? As long as the account that published that survey is the same one accessing that survey via PA (and your custom connection), it shouldn't matter what your sharing settings are because that service account always has full permissions.

Re: Guide to Generate Feature Reports in Power Automate (Enterprise and AGO)

ISP_graynic — Tue, 26 Apr 2022 19:35:43 GMT

The account has admin privileges and since the survey is on AGOL I didn't create a custom connector but rather used the standard "When a survey response is submitted" in PA since the survey isn't on my own portal but just AGOL. The error message I get in PA is just a 400 error "This operation is not supported' when trying to create the report. When I change the feature layer settings in AGOL to the "Editors can see all features" however it works fine and generates the report.

Re: Guide to Generate Feature Reports in Power Automate (Enterprise and AGO)

abureaux — Tue, 26 Apr 2022 20:40:06 GMT

Out of curiosity, is there a reason you can use Editors can only see their own features (requires tracking)? I'm not too sure how that interacts with a Public Survey though.

This could be a limitation of the flow, but Esri support may be able to shed some light on that.

Re: Guide to Generate Feature Reports in Power Automate (Enterprise and AGO)

ISP_graynic — Tue, 26 Apr 2022 20:56:23 GMT

I think the problem there is technically anyone who anonymously fill the survey out is out is seen as 1 user, so therefore it's their "own" features. Meaning anyone who submits anonymously can see anyone else who's anonymously submitted data which is what we are trying to avoid. That's why we had to change it to the last setting. I also have an email to an ESRI contact to see if they have any ideas.

Re: Guide to Generate Feature Reports in Power Automate (Enterprise and AGO)

abureaux — Tue, 26 Apr 2022 21:02:08 GMT

Darn. That's what I was afraid of. I was hoping that each submission would be a different "user".

Hopefully Esri has a suggestion that will work for this. Please respond back if you find a work around! Sorry I couldn't be of more help.

Re: Guide to Generate Feature Reports in Power Automate (Enterprise and AGO)

ISP_graynic — Wed, 27 Apr 2022 15:21:23 GMT

I think I may have figured a workaround. In Step 7 "Add 3 Set Variable steps" I changed the featureLayerUrl to the the service URL of a view layer that's not shared publicly out instead of the dynamic value from the Parse JSON. It seems like adding a new entry to the public layer via the survey still triggers the flow but the actual report is generated off a view layer.

Re: Guide to Generate Feature Reports in Power Automate (Enterprise and AGO)

OlivierPontbriand_Pare — Wed, 22 Jun 2022 15:21:42 GMT

Hi! One quick question.

I'm connected to S123 through AGOL and I'm not sure what's supposed to go instead of NAME (the blacked out section) in the HTTP blocks.

https://survey123.arcgis.com/api/featureReport/jobs/JOBID?portalUrl=https://NAME.com/portal&token=TOKEN

I've tried a few things and nothing seems to work.

thanks a lot!

Re: Guide to Generate Feature Reports in Power Automate (Enterprise and AGO)

abureaux — Wed, 22 Jun 2022 16:19:53 GMT

Unfortunately I don't have explicit steps for completing this in AGO. As all our corporate content is in Enterprise, it's very rare I look at AGO workflows.

If anyone has a workflow for AGO, I would be more than happy to update my initial post to include steps for both environments so that everyone can benefit! If I get lucky with some free time, I'll try to put something together, but not sure when that will be though.

Re: Guide to Generate Feature Reports in Power Automate (Enterprise and AGO)

BenGultch1 — Tue, 19 Jul 2022 16:41:09 GMT

Have you tried omitting the portal section?

So something like https://survey123.arcgis.com/api/featureReport/jobs/JOBID &token=TOKEN

Re: Guide to Generate Feature Reports in Power Automate (Enterprise and AGO)

JessicaBennett — Wed, 25 Jan 2023 14:24:44 GMT

I am running into issues in the Do Until > Parse Json – Result Info step. It appears that it is the *Content Body option that is throwing this error. I currently have this set to Body (HTTP – Get Job Status). I have tried setting this to another Body file and the script will run through completion, but always results in the failed email. Has anyone else experienced something similar?

Re: Guide to Generate Feature Reports in Power Automate (Enterprise and AGO)

Blevins_Mark — Wed, 17 Jan 2024 23:49:07 GMT

I am getting an error from PA if I have a geopoint question..."An error occurred when rendering by the report engine. Failed to print map for `${RepeatObservation.photolocation |drawingInfo:\"currentLayer\" | where:”ParentRowID=RowID !important” | map:” f87e4997dbad4d34828ef8f3763370f4”| size:600:0}`. Waiting failed: 180000ms exceeded"...if I remove the geopoint question i can get it to run...anyone know how to get around this?

Re: Guide to Generate Feature Reports in Power Automate (Enterprise and AGO)

abureaux — Thu, 18 Jan 2024 16:06:31 GMT

Oh man. This error...

To be honest, I don't have a silver bullet for this (but I do have a suggestion below). This has happened to me a few times in the past. It appears seemingly randomly, and then disappears just as mysteriously as it appeared. Nothing I do seems to affect this error (other than removing the geopoint, as you pointed out).

I have meant to followup with Esri on this while the issue is present, but haven't been able to yet (I'm also not experiencing this issue right now).

A potential workaround would be to use the new report generation method rather than the custom method I have detailed here. I am only saying potential workaround because I haven't seen this issue after swapping to the new method, but this error seems to pop up so infrequently that it's hard to say if this change has resolved the geopoint issue.