S123 error when generating report with geopoint

[OrrinFeril]

An interesting issue popped up yesterday around 12:00 pm CST in Make.com that the S123 module was unable to generate a report. 

Troubleshooting steps:

1. I accessed the survey's data via AGOL and the data looked valid. I attempted to create a  "Preview sample report" to test that the data would properly load into the report template. I received the error below.
2. I updated and republished the survey in S123 Connect. 
3. I checked that the custom web map would load properly via AGOL. The data loads properly in the web map with the "GMD5 Subbasins" layer loading properly.
4. I've disabled the "GMD5 Subbasins" layer in the web map to determine if it is a layer issue or something bigger.
5. Other surveys that do not have a geopoint map within the report template process properly.
6. However any survey that has a geopoint map embedded into the report template seems to result in the same error.

Let me know if there are additional troubleshooting steps other than "delete the survey / data" and restart. 

[ZhifangWang]

@OrrinFeril ,

Thanks for the feedback. When you disabled (or removed) the layer "GMD5 Subbasins" in the web app, was the report generated successfully using the same template including the map? Can you please confirm what the coordinate system is for the layer "GMD5 Subbasins", and is there any hidden layer in the web map?

[OrrinFeril]

Good morning,

When the subbasins were disabled in the web map, the survey report still fails. I should have clarified earlier, the troubleshooting steps noted previously did not work to get the survey reporting working. 

The coordinate system for the subbasins layer, like others layers in the web map, is: Projected WGS 1984 Web Mercator 

As for hidden layers in the web map, no layers are hidden. There are some that are invisible based on the map scale but none hidden by default. I "disabled" GMD5 Subbasins layer by hiding it. 

To further check for issues, I removed the GMD5 Subbasins layer from the map completely. I still received an error, but for another layer within the same geodatabase hosted within our organization's AGOL. So I don't think it is specific to the layer. 

I have confirmed that the web map and underlying geodatabases are available to everyone in the organization. To test this further, I have temporarily made the geodatabase public. 

Here is the link to the geodatabase. (once this is solved, this geodatabase will be reverted to organization use only. So if you are seeing this after there is a solution, it may not be visible to you.)

[BrianNorman]

Hi, I am experiencing exactly the same issue, I can't export reports from several different surveys either as 'preview sample' or 'full word' output. I've tried cleaning up the maps that the report uses but nothing has helped. I just get a summary page output with the error message 'Reports have been generated with some issues'. This was not a problem about a week ago.

[OrrinFeril · Accepted solution]

When I got to the office this morning, I did a quick check to see if the error still persisted. To my surprise, the error did not present itself and the "Preview sample report" worked fine. So I jumped over to Make.com to see if it would process the automated report generation and process the growing queue of surveys that have accumulated. 

It worked perfectly.  There were no modifications/changes done on our end. I do not know what caused the issue but it is working fine now. 

[CBarrett]

My guess is the email I got this morning is relevant:

BUG-000181101 has been addressed.

Description: ArcGIS Survey123 fails to print custom reports that include a web map {$map} when one or more layers are hidden or the visibility is turned off.