Guide to Generate Feature Reports in Power Automate (Enterprise and AGO)
I have. But, I don't have anything specifically to attribute to it. The typical culprits include:
- Tables (these can be tricky sometimes).
- Content Control elements (example below).
- Comments.
In most cases, it's a tag crossing some element resulting in unintended consequences. E.g., When content is dynamically added or removed while crossing a comment, it can result in this error. Example of how to not place a comment in a Feature Report:
Sometimes, the easiest solution is to play 20-questions with your document. E.g., Cut out the bottom half of the content and then run the report. If the issue persists, restore the bottom half, remove the top half, and run the report. If the issue is resolved, restore the cut content, and then cut the restored content in half.
Essentially, you are just narrowing down where the error is originating from.
If you are having trouble, you can upload your Feature Report and I can have a look.
Hi @abureaux ,
Thank you so much for posting your flow here. I tried it today, but unfortunately, I am receiving an error, please see the following code and screenshot:
"<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
<title>404 - File or directory not found.</title>
<style type="text/css">
<!--
body{margin:0;font-size:.7em;font-family:Verdana, Arial, Helvetica, sans-serif;background:#EEEEEE;}
fieldset{padding:0 15px 10px 15px;}
h1{font-size:2.4em;margin:0;color:#FFF;}
h2{font-size:1.7em;margin:0;color:#CC0000;}
h3{font-size:1.2em;margin:10px 0 0 0;color:#000000;}
#header{width:96%;margin:0 0 0 0;padding:6px 2% 6px 2%;font-family:"trebuchet MS", Verdana, sans-serif;color:#FFF;
background-color:#555555;}
#content{margin:0 0 0 2%;position:relative;}
.content-container{background:#FFF;width:96%;margin-top:8px;padding:10px;position:relative;}
-->
</style>
</head>
<body>
<div id="header"><h1>Server Error</h1></div>
<div id="content">
<div class="content-container"><fieldset>
<h2>404 - File or directory not found.</h2>
<h3>The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.</h3>
</fieldset></div>
</div>
</body>
</html>"
Have you ever encountered such an error? If so, how did you resolve it?
Thanks in advance.
Hello.
I will have to edit my post as this is quite old now. I will try to get a simplified guide out in the next day or so, but I also want to include a complex guide for a more robust flow later.
Technically this method does still work, but Esri has released a new module for Enterprise users (and AGO) that can generate feature reports MUCH easier.
I highly recommend swapping to that method. Here is the blog.
The one issue you may run into is with the Custom Connector. If your Custom Connector is old (like mine was), then you will not see the new Create Report action.
If you want to know if your connector is up to date: Go into any flow > add a new step after your trigger (any trigger) > go to "Custom" > check for the "Create report" step (pictured below)
If you see "Create report", you are good to go!
If you don't see "Create report", you have three options:
1) Delete your old trigger and make a new one (If you have a lot of flows, I don't recommend this),
2) Make a new trigger with a new name and come to terms with all of your old surveys using a different trigger (my OCD wouldn't allow for this option), or
3) Make a new Custom Connector, copy the code from it and paste that new code into your old trigger (While I was terrified of breaking everything doing this, it worked beautifully. I was left with a single up to date Custom Connector, and no surveys needed to be updated by my users. A win-win!)
-------
Regarding your actual question 'no', I haven't actually seen that particular error before. My only thought is that something is wrong with the URI. Rather than fight with this method though, I'll loop back to my original suggestion of swapping to the new method.
