nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Survey123 feature report - anticipated fix?

danbecker

Are there any updates or a timeframe for fixing the survey123 feature reporting issues? We desperately need to print feature reports using Enterprise 10.8 and cannot do so after the July 3rd update.

This is the error received after trying a default template that I downloaded from the survey123 "manage feature templates" dialog.

Find more posts tagged with

Accepted answers

All comments

danbecker

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?

danbecker

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?

ZhifangWang

Hi dan becker‌,

Thanks for your feedback and the detailed information.

Since you mentioned that it's ArcGIS Enterprise 10.8 you are using, I can confirm and share the details that this issue is caused by the combination of the following two:

In the latest update of the Survey123 website, we use /queryAttachments instead of attachment info as long as the feature service's supportsQueryAttachments is true (Enterprise >=10.8). Also, we will use pagination approach to query all attachments in case the total account exceeds the maxRecordCount, as long as the feature service's supportsPagination is true. Your ArcGIS Enterprise satisfies both.
In ArcGIS Enterprise 10.8, there is a bug that if resultOffset and resultRecordCount are used in queryAttachments, ‘Pagination is not allowed unless ''supportsPagination'' is true.’ error occurs even supportsPagination is true in the layer. You can tell this by trying in the service directory as below.
- This issue is fixed in the coming ArcGIS Enterprise 10.8.1

From Survey123 perspective, we are trying to figure out a workaround for the issue in ArcGIS Enterprise 10.8 so it will not affect feature report users.

Thanks,

Zhifang

danbecker

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.

danbecker

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.

IsmaelChivite

Hi Dan. Per information in this article Error: Pagination is not supported it looks like this could be caused by an underlying database not supporting pagination. Pagination is a critical feature to allow the creation of large reports. Could you confirm what is the underlying database and version you are using?

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.