Latest Contributions by danbecker

confirmed working. Thanks everyone. ... View more

Looks like the beta site has the fix now. I successfully exported a feature report for a record that previously failed with the supportsPagination error. Thanks Zhifang! ... View more

There isn't a fix. For us 10.8 users, we are out of luck until 10.8.1 gets released. Just tell your field crew to stop posting attachments to the s123 form, then you can at least generate the feat. report. The problem is that the 3 July s123 website release started using the queryAttachments REST API query (if 10.8 is detected), and there is a bug in 10.8 that throws  the supportsPagination error. That bug is supposedly fixed in 10.8.1. So, if your on <10.8, then no issue because the older attachmentInfos query is used, as queryAttachments isnt supported on <10.8. ... View more

I can see the hesitation in editing the new s123 release since it uses the 10.8 documented procedure. The real fix is updating to 10.8.1 that has the bug corrected. The question is, when can we expect 10.8.1, is it weeks or months away? ... View more

I would consider a new workflow that doesn't involve editing the dropdown values, i.e. coded value domain. Each time the dropdown values are edited, you have to re-publish the survey so others can view your form changes. Likewise, others then have to refresh the survey form in the s123 app. Seems clunky to me. Some options off the top of my head: --Put all possible values that will ever exist in the dropdown, then filter the results --Change the select_one question to a text box. Maybe after they enter the project name once at the top of the form it auto-populates other entries below, limiting entry mistakes. ... View more

Add a READ ONLY "status" select_one field to your survey that has a default value of "Submitted". The other option for the "status" select_one question would be "Reviewed". This requires no input by the user, in fact it's read only. Since new forms will contain the default value of "Submitted", the user doesn't do anything. Look into webhooks, I recommend Integromat. You can configure the webhhook to fire on editData (not addData). So, your webhook will only fire if the form has been edited, i.e. reviewed. In Integromat, use the HTTP module to make a applyEdits REST request to the survey123 feature service. Apply Edits (Feature Service/Layer)—ArcGIS REST API | ArcGIS for Developers  applyEdits would use the update parameter to set the value of "status". Both the initial form submitter and later reviewer wouldn't have to do anything and you could see the status change on the feature service after the workflow had been completed. ... View more

Thank you for the detailed explanation. One of the reasons we updated to 10.8 was because queryAttachments was added, the attachmentInfos method of retrieving files added clunky code IMO. I find it hard to believe someone would have more then then default maxRecordCount = 1000 attachments. But I guess it's difficult to get the length of the queryAttachments json return (necessitating/not the need for resultOffset and resultRecordCount) without first sending the request. Perhaps remove resultOffset and resultRecordCount params from queryAttachments in the beta site, just to get reports running until 10.8.1? ... View more

In my case, it's very specific. I only get the supportsPagination error when trying to export a feature report for record that: contains a repeat, that repeat HAS to contain an Image type question that repeat that contains an image type question has to have at least 1 image attachment, i.e. the user didn't leave the repeat blank If either of those conditions aren't true the report prints fine. ... View more

I get the same "supportsPagination" error on https://survey123beta.arcgis.com. I opened a support case as well. ... View more

I'm in the same boat, except with our Enterprise Portal (10.8) I'm getting a "supportsPagination" error, see here: https://community.esri.com/thread/256233-survey123-feature-report-anticipated-fix  My feature reports were working fine until the Survey123 website was updated on 3 July. In my case, a related table (relate) contains a image type question. This allows the user to attach as many photos as desired (via the repeat) to the survey form. If that repeat contains at least 1 photo record, I get the supportsPagination error. If the repeat is empty, then it prints fine. I have not been able to get any answers from ESRI, I guess I'm going to try and open a support case. I can't help but feel like ArcGIS Enterprise users were forgotten about with the 3 July update, after all, we don't consume credits ... View more

The beta site doesn't fix "supportsPagination" bug, see here for details: https://community.esri.com/thread/256233-survey123-feature-report-anticipated-fix  We really need to get this working! ... View more

Are image type questions inside a repeat no longer supported in feature reports? It doesn't look like the feature template help docs have been updated for awhile now. Should I open a support case? We need answers as to why feature reports stopped working after the latest release. ... View more

This behavior just started after the most recent updates to feature reporting. The survey was created in Survey123 connect then published to ArcGIS Enterprise 10.8. Our base deployment of Enterprise obviously includes ArcGIS Server, which has a relational data store registered. That relational data store is ArcGIS Datastore 10.8.0.12790 (Linux Ubuntu, See Below). So, the survey123 database is ArcGIS Datastore. I looked at the REST endpoint of the hosted feature layer that was created by publishing the Survey123 Connect Survey, and it says pagination is supported, See below. After more testing, the supportsPagination error I'm receiving is due to a conditional statement in the feature template, (see below). Since we cannot include photos in Enterprise feature reports, we print the photo filename in a table of the feature report. In the S123 form (below), the yuma_photos repeat contains an image question and a hidden photo_name question. If an image is captured, it's filename is copied to the photo_name field. A join() is used outside the repeat to add all the filenames together in a comma separated string and stores them in photo_tally. If photo_tally is blank, the feature report prints to PDF correctly. If photo_tally contains filenames (or any string for that matter), the PDF feature report errors out with the supportsPagination error. Edit, additional information: If the yuma_photos repeat contains any records at all, then the feature report errors out, regardless. I tried removing the above pictured ${if photo_tally} section of the report, including the table it contains, then updated the feature template. I then attempted exporting a feature report for a record that contains yuma_photos repeats and it STILL produced an error. The inverse is also true. Using the original feature template that contains the ${if photo_tally} section, then exporting a feature report for a record with NO yuma_photos repeats; it's successful. I can successfully export feature reports for other surveys that contain repeats, but they DO NOT have image questions in the repeat. All signs are pointing to issues with handling repeats that contain image questions. ... View more