Hi there, S123 feature report keeps failing. I dont know if ESRI changes anything from their server side, we have not changed anything from our side. Has anyone noticed this issue? Thanks,
@abureaux ,
If your survey that can reproduce the issue was created from blank (with no value for submission_url), would you mind sharing the XLSForm file and the report template file with us so we can understand the issue better?
If possible, you can attach files here or send them to zwang#esri.com (replace # with @)
Sorry, but no. The Features that were having errors for me were created Blank in Connect and had no associated Features.
Unless you mean the error was caused simply by having a repeat question type?
No luck for me:
@lannguyentl @LeDangNguyen @KyleWeaver @abureaux @Andrew-Bowne @CristianChavarini ,
After investigation, we found this issue relates to "relationships between multiple layers" in the behind feature service, I assume your surveys are created from existing service that has relatively complex relationships, although the survey itself may involve only one layer in the service.
In this case, we need your help to test the fix to ensure it can work for your workflow.
We had the fixed installed on the Beta website https://survey123beta.arcgis.com , can you please test your surveys on the beta website?
If everything goes well, we plan to apply the fix to the production website next week.
Thanks,
Zhifang
As mentioned by James here, we have rolled back yesterday's update. The report service should work as previously now on the Survey123 production website.
However, the issue should still be reproducible on the current Survey123 Beta website (https://survey123beta.arcgis.com), it would be helpful if you could share the XLSForm and report template files with me or James Tedrick, or contact Esri Support Service to report this issue so that we can apply the fix to this issue before our next update.
In our case, by reverting the update we can send reports again. Apparently the services published with related tables were the ones that did not allow to generate reports, this also broke MAKE automation modules.
Just saw this post, so it's probably better if I respond to this.
I can confirm that my reports are working agin.
The issues seems to have been resolved on Esri's end, and I am now recieving reports again.
Hi all,
Given these reports of functionality impairment, we have reverted the update to the feature report system. We would appreciate your help in diagnosing this issue; if you have an case open with Esri Support, I have asked them to forward your information to us if you are willing. Otherwise, please reach out at jtedrick@esri.com.
We are having the same problem
I sent you my XLSForm and report Template. Thank you for taking the time to look at it.
The issue only affects the report capability and does not affect the web app or the field app when collecting data.
It may relate to a change that parses relationships between layers. Although it is directly related to the report template, it can only help us when we have both the XLSForm and the report template file to reproduce the issue.
At least for my workflow (generating preview reports), the issue appears to have been fixed. Thank you!
Would this be an issue with the XLSForm? I have ~50 forms created over the last couple years (aka, some on the most recent template, and others not). They are all having the same issue with querying Esri for a Feature Report.
It is important to note that I (and I assume others?) can still write data to the Feature Service. It's only when we try generating a report that the error pops up:
Also of note, I am on Enterprise. I don't have a test environment on AGO, but I believe all S123 Feature Reports query the same service, so the error likely is happening there as well?
Same issue here. Using ArcGIS Enterprise Portal and data is still being written however reports are not being generated.
@lannguyentl @LeDangNguyen @KyleWeaver @abureaux ,
We have just rolled out an update yesterday, I apologize for the inconvenience that the update affects your report workflow.
From the original screenshot, it's hard to tell the details of the issue. Can you please share your XLSForm file and the report template file to help us better understand the issue? You can also send files to zwang#esri.com (replace # with @).
This is indeed a global issue. Several cases already opened with Esri tech support. They are escalating to Esri Inc. right now.
Same issue here as well!
Oh, I just posted and having the same issue. At least I know this is a global error.
Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
