Repeat groups offer a good way to collect soil profile data, as profiles often have differing numbers of horizons and each horizon requires roughly the same details to be recorded about it. However, the Survey123 app only shows one repeat record (e.g., one horizon) at a time, requiring users to toggle left and right between them. When evaluating a soil profile to determine if it is hydric, it's important to be able to view all the horizons at once, so the app is not conducive to this. The Web Form displays each record stacked on one another, which would make the evaluation easier, but people collecting soil data in the field often do not have internet/4G access. Therefore, it would be nice if an Appearance option could be added for Repeats in the Survey123 app to appear with each record stacked on one another so the user can view multiple records at once and simply scroll up and down between them. I realize some people may like toggling between single records to reduce screen clutter, so the default Appearance could remain that way, but adding a "stacked" option for Appearance would allow for more layout flexibility, which is one of the main things Survey123 currently lacks in my opinion. I think the grid-theme that's in development would mesh well with this option to reduce screen clutter.

Idea:

Add Location Profiles as a configuration parameter in Survey123

The Problem: 

You need to apply a datum transformation in Survey123 (perhaps, to utilize an RTK network) but you cannot configure the Location Profile in Survey123.

Location Profiles can currently be configured in ArcGIS Field maps to apply datum shifts, but this functionality has not been extended to the Survey123 app.

The Current Work-around:

For EOS receivers, a datum shift needs to calculated and applied outside of Survey123 in the EOS GNSS app.

A point collected in Field Maps using the desired Location Profile and a second point collected using the 'Default' settings can be used to calculate a datum shift in ArcGIS Pro or ArcMap. This shift can then be input into the EOS GNSS app, which will apply the datum transformation prior to logging the location in Survey123.

Thus, collecting high-accuracy location information in Survey123 is possible using the EOS work-around to apply a datum transformation.

Solution:

The current work-around is complex and involves several steps and four different types of software.

This workflow could be greatly simplified if a parameter to configure a Location Profile could be added in Survey123 for Users needing a datum transformation for locations collected in Survey123.

I think a "Dark Theme" button...especially for all apps to the field workers would be optimal in a sunny day. 

I feel the addition of a default "Yes/No" question would be quite useful and time saving within the Survey123 web app. Having it as an option would eliminate quite a few extra steps needed to create this option out of the standard "Single Choice" option. Currently if you want a simple Yes/No each time you create that you need to go through the following:

rename choice 1 to yes

rename choice 2 to no

delete choice 3

set to horizontal(not required but is a cleaner layout for this question)

This sounds small but when making a survey with dozens or even up to 100 questions of this type it becomes tedius.

Thank you for your consideration in this matter

Survey123 Connect | Esri can you add the option to auto-magically create a Hosted, View when publishing

I usually need this at crunch time, and it would be nice if we had the choice to create it during publishing.

The jr:choice-name function currently returns an error if used in the instance_name field. The instance_name returns blanks if a field that uses the jr:choice-name function in the calculation is used as the instance_name. This functionality would allow the domain label to be used in the instance_name in the Inbox. 

The post here: Using jr:choice-name... talks about possible workarounds but the functionality hasn't been implemented. 

@IsmaelChivite

@Anonymous User 

I love the new address type question, so much easier to use than a map question when you want to collect the point location of a respondent. Next, it would be nice to be able to either have some conditional formatting or a way to restrict the geographic area that we'll accept response from.

Example: we're running a trick or treat candy delivery program in our city, and in order to sign up you have to be a resident. So if someone from a neighboring city tries to sign up, we want the survey to tell them, based on the address they entered, that they're not eligible for the program. That way they can't go through will filling out the rest of the survey only for us to have to reach out to them to tell them thanks but you can't actually participate.

For us being able to filter using our city boundary as a geofence would be great. But alternatively, we could make it work if we could use our own geocoding service so that people can't fill out the question and submit the survey unless they can find a matching address.

Currently the deprecation item flag is mostly useless. It can be a deterrent from new users picking a service but there is no way for existing users of a deprecated item to realize they are using a deprecated item. 

Allow the different API's to see the deprecated flag on a feature service and then display UI to notify clients of deprecated service usage. Bonus points if you add UX to navigate to the item page to read about the deprecation and hopefully find a replacement.

As it currently stands, the deprecation flag is not helping to remove the usage of deprecated items. Make deprecations useful please. 

It would be helpful to include information in a webhooks payload that is not part of the feature layer data.  For instance, there is data I would like to collect in a survey that I do not want to store as feature layer data but would like to use for filtering in my webhook.  It's not necessary to store this data as it's used in my case only for filtering.  This could be accomplished by allowing null data types with hidden questions to be passed as user defined information.

See attached images for illustration

Thanks for the consideration!

I would like to see the ability to use calculations (specifically sum) on geometry questions in the web interface. I have a geopoint in a repeat. I am using those repeated geopoints to generate a geoshape for the containing entry. This is useable in the Field App, but for my users, downloading and using the Field App can be one more thing that stops them from using the system.

On a custom “thank you screen” defined in Survey123 Connect, it would be very helpful to have the ability to run JavaScript functions right after a survey is submitted. Currently, this is not possible, per this post here: https://community.esri.com/t5/arcgis-survey123-questions/survey123-connect-custom-thank-you-screen/m...

One example where this would be helpful – to provide the user with a URL that allows them to copy the survey they just submitted. A JavaScript function could be run right after submitting (on the thank you screen, in the “generated_note_prompt_submitted” line) in order to fetch the globalid value and create a copy link using Survey123 URL Parameters.

Users can abandon a survey and discard the data collected.  However, when data is primarily collected through repeats (particularly when devices are offline for extended time) some users have accidentally discarded a significant amount of data they actually wanted. They report it is too easy to mistakenly choose discard when they just want to close or after an app crash. My suggestion is to make the 'discard' procedure more interactive to ensure users really want to permanently erase the data eg: clear warnings and second chances. Ideally a simple parameter would set how many hoops a user must jump through before the data goes forever.