Hans Christian Andersen Release (3.9)

04-02-2020 07:33 PM
Esri Frequent Contributor
10 34 3,768

Hans Christian Andersen was born in Odense, near Copenhagen, Denmark, on April 2, 1805. He is famous for his fairy tales, such as "The Little Mermaid", "The Emperor's New Clothes", "The Princess and the Pea" and many others. Fairy tales are short fictional stories for children's entertainment. They generally involve animals, plants, forces of nature or folkloric characters such as elves, witches, fairies... fairy tales often have happy endings, but Andersen never took that very literally.

Coinciding with Andersen's birthday and International Children's Book Day, today we release Survey123 version 3.9. This update also has a touch of magic in it...

Survey update notifications in the Survey123 field app

Many of you have contributed with your comments and voted up ArcGIS Ideas‌ from Mike Bruening‌ and James Botterill‌ on survey update notifications. So far, these are among the most popular of all! 

With this update, the Survey123 field app will let you know if a new version of a survey on the device is available for download. This check happens automatically when the application starts, or when a new user signs in to the app. You can also manually trigger the check by simply dragging down on the survey gallery.

Survey update notifications will appear after you re-publish a survey. For example, if you add additional choices to a list, fix a typo on a label, add new questions or adjust calculations, etc.

As of this release, it is up to the end user of the app to decide if and when a survey update should be downloaded. We are aware that many of you would like to force survey updates in some cases and this is something we are working on implementing in a future release.

We trust this new feature will streamline much of your field work out there!

New Map question in the Survey123 web designer (line/polygon support added)

With this release, we have replaced the geopoint question type in the Survey123 web designer with a new Map question type. The Map question is useful when you want end users to provide the location of an event, just like you did with the geopoint question, but it also supports line and area modes.

Survey123 designer now includes a new map question type

In the screenshot above, for example, the Map question in the form is configured to let end users draw an area (polygon), instead of a single location (point). The new Map question type works well in the Survey123 web and field apps and features vertex-by-vertex and freehand drawing tools.

Since the ArcGIS data model is limited to one geometry field per layer, it is only possible to add a single Map question to a form. Additionally, once a survey is published, it is no longer possible to switch the type of geometry in the Map question. That is, you cannot for example switch from line to area. It is possible to change the drawing tool mode from freehand to vertex-by-vertex, but not the geometry type. If you ever need to make such a change, you can save a new copy of your survey and change the geometry type before publishing your new survey.

We want to thank all of you who provided feedback through the Early Adopter Program and our Holistic Testing sessions during the development of this new question type. In particular to Charlie Fitzpatrick‌, Joseph Kerski‌ and Education‌ colleagues.

Custom Survey123 feature report filenames

Many of you have requested more control over the name of the output files created by the Survey123 feature report service. You can now include a question placeholder in the output report file name that you pass into the service. This placeholder value will be dynamically replaced when the report is generated.

In the screenshot below for example, you can see that the name of the output report file generated includes the household id value from the survey record.

Custom report file names (Survey123 report service)

You can use question placeholders when defining the report output filename in the Survey123 website, or from the Integromat module. The placeholder looks as follows: ${question_name}. For example, below I set the placeholder to use the value from the field hhid (Household ID). You can combine if you wish multiple placeholders.

New Survey123 web app JavaScript API

The Survey123 web app JavaScript API is designed to help web developers more easily embed, style and interact with live Survey123 smart forms within their applications. It is a simple, yet powerful way to integrate Survey123 within larger business workflows. Through this API, you can choose at runtime what survey you want to display and how it will fit within your web application. You can bidirectionally send messages between your form and the web application. To learn more about this API check the https://community.esri.com/groups/survey123/blog/2020/03/05/introducing-the-survey123-web-app-javasc... blog post.

Survey123 web app Draft mode

In the Survey123 website, if you visit the Collaborate tab, you will find a new Draft mode section. If you choose to use the draft mode, data entered through the Survey123 web app (from a web browser) will be stored locally until your survey is sent or cleared. This is useful for long surveys where people may choose to work on your form for a while, and then come back to it later after having closed the browser. Data will not be lost even if the end user navigates away from the survey or closes the browser; when they go back to your survey URL, all the entered data will be there until submitted.

You will want to turn on this option selectively, as this could compromise the privacy of entered data if used from a shared computer. For example, if someone is working on a form with sensitive information and draft mode is enabled, it is possible that data could be compromised if that person forgets to submit or does not reset the data in the form. Anyone loading the survey URL at a later time from that shared computer will see the data.

Draft mode is only available in surveys published with version 3.9 or above.

When draft mode is on, a link to reset the draft will be shown at the top, as illustrated in the screenshot below.

Other fixes and enhancements

Whilst the new features above are important, many of the fixes and enhancements that follow are just as relevant. I will highlight here a few that could easily get lost amongst the list below:

3.8 and earlier versionsSupportedNot supported
3.9SupportedSupportedUse this version to migrate!
3.10 and beyondNot supportedSupported

  • We very strongly recommend that you transition away from objectIds as the days for them are counted!  With 3.10 we will completely drop to support and exclusively use globalds.
  • In the Survey123 field app, you will notice that the sign in workflow has been revised. It features a cleaner, more informative and easier to use UX. This was part of a larger effort to accommodate random sign out issues and to incorporate multiple enhancement requests to facilitate login/logout workflows. The UX for connecting the app to your own ArcGIS Enterprise portal has also been revised.
  • In the Survey123 website, the Analyze tab now includes a much improved user experience for navigating long forms.
  • If you work with XLSForms, you should also note that starting with this release, select_multiple questions now support calculations.
  • If PKI authentication is of interest, on top of SAML PKI support, the Survey123 field app now also supports PKI authentication from your ArcGIS Enterprise web adaptor.
  • For Windows users: You can also now download the Survey123 app and Connect directly from the Windows Store.

Survey123 field app and Connect

  • Never get randomly signed-out again: Multiple fixes have been applied to accommodate scenarios where the Survey123 field app would randomly sign users out: BUG-000128933
  • Enhanced PKI authentication support: While support for PKI through SAML has been available in Survey123 for a while, this update brings new enhancements to support PKI authentication at the ArcGIS Enterprise Web Adaptor level. This provides additional flexibility to deploy Survey123 in environments that adhere to this standard. For more information regarding PKI support in Survey123, check this help topic.
  • Windows Store: The Windows 64-bit and 32-bit setup files of the Survey123 field app and Connect can be found from our Survey123 download page. Additionally, starting with this release you can also download Survey123 Connect and the Survey123 app directly from the Windows Store.
  • Addressed multiple issues related to double tap sensitivity: BUG-000124309BUG-000125208BUG-000127278BUG-000109661.
  • Split View on Apple devices: You can now arrange the Survey123 field app in iOS split view.
  • BUG-000125609 ArcGIS Online allows the organization short name to include uppercase characters leading to case sensitive related errors when using the organizations URL.
  • BUG-000127518 Creating a form in Survey123 for ArcGIS with a geopoint question type and esriFieldTypePointZ field type does not allow the feature geometry to update in ArcGIS Online Map Viewer.
  • BUG-000127816 The surveys displayed is changed when multiple languages are set up in the survey.
  • ENH-000125365 Have Survey123 honor the "Remember Me" functionality when using a IWA login from Portal.
  • ENH-000105906 Add functionality for Survey 123 Connect to have a "remember me" option for usernames.
  • ENH-000121154 Support Trimble Rx GPS receivers in Survey123 on iOS devices.
  • BUG-000122130 One page will be automatically added when collecting the survey in the survey123 app created from survey123 web designer with more than one page.

Survey123 website, web app and report services


  • DE-000003535,BUG-000126960 An error is returned when trying to generate a feature report in the Survey123 for ArcGIS website for a survey published using the 'Feature Service' option.
  • BUG-000128390 Surveys created and accessed through the Survey123 for ArcGIS website returns the error message, "Survey does not exist or is not accessible" when special characters exist in question or choice labels.
  • BUG-000128110 GeoPoint question's map for the surveys created using Survey123 web designer (after the recent update) does not appear in Survey123 field app (on both desktop and mobile devices).
  • BUG-000126008 After removing a single choice grid from a group, republishing the survey, and adding it back into the group, any changes made to the single choice grid questions are given identical, generic schema names preventing the user from republishing the survey
  • BUG-000127630 In Survey123 for ArcGIS, when a survey has a geotrace or geoshape question type, the map scale setting is not honored when including a map in the feature report
  • BUG-000126425 Boolean expressions do not work in the Survey123 for ArcGIS web app
  • BUG-000128085 In the Survey123 for ArcGIS website, images in a Note element cause the survey to fail to publish if they are on the same row separated by a space
  • BUG-000128548 The background set for a survey is displayed as distorted in the web form if the “style settings” is set to “pages” and “appearance” for groups is set to “field list”
  • BUG-000124744 HTML markup codes appear at the start of the published survey in Survey123 for ArcGIS
  • BUG-000116598 Survey123 for ArcGIS error 'Privileges of stakeholder role are required to access this page. You're currently in field worker role.' when accessing the survey..
  • BUG-000117843 When using the em dash 'ー' (UTF-8 Enconded \xE3\x83\xBC) in a single line text question, the words are broken up into separate responses in the wordcloud section of the Analyze tab
  • BUG-000125151 The Survey123 for ArcGIS Website does not retain the Layout Element settings (Header and Footer Settings) for a survey if the Survey has been published through Survey123 Connect
  • BUG-000111740 The Survey123 website returns the 404 error message in network traffic when loading a survey in a web browser
  • BUG-000126848 Viewer and Editor roles with the 'feature report' privilege enabled by default are unable to generate a feature report in Survey123 for ArcGIS as the 'create, update, delete content' privilege is also required.
  • BUG-000122896 Surver123 for ArcGIS does not provide a character count on text questions with repeats. 
  • BUG-000129358 Some organizations are unable to publish any surveys in the Survey123 for ArcGIS web app
  • BUG-000125046 A geopoint location is rendered as an empty map image in the exported report from the Survey123 for ArcGIS website when the survey is created from an existing feature service.

Documentation and templates

  • BUG-000128228 Unlisted built-in (reserved) geodatabase field names cause the publishing error with Survey123 for ArcGIS that is returned when using a reserved keyword for a field name, "Error: Dataset not found. Code: 500. Publishing failed."
  • ENH-000127952 Displaying the 'name' field instead of the 'label' field for select_one type questions in Survey123 reports
  • ENH-000128878 Survey123 - Documentation - orderBy Parameter - is missing of examples, case application and a more detailed description for the function
  • ENH-000128477 Improve documentation for Repeats in Survey123 to contain information on the abilities and limitations of nested repeats
  • ENH-000126920 Currently the text for when Configuring Survey123 with a feature service published to ArcGIS...
  • ENH-000127608 Please update Product Life Cycle page for Survey123 to indicate Classic was 2.9 and below and is now retired as of a certain date

Next steps

Survey123 3.10 is already in the making. You can access the latest builds from the Early Adopter Community. Our focus is aimed towards a few critical aspects:

Survey123 field app fix-only update for iOS (for release before end of April 2020):

  • Specifically for iOS, and for specific surveys, you have observed consistent crashes in the Survey123 app. These issues are currently being worked on and we are aiming at releasing an update for iOS to address these issues as soon as possible. BUG-000111086,DE-000003544, BUG-000108085,BUG-000128201,DE-000003543, BUG-000125015,DE-000003368, BUG-000126685. Beta builds with fixes to these issues will be shared through the Early Adopter Community as soon as they are ready.

Survey123 3.10:

  • Mapping enhancements in the Survey123 field app: for quite some time now we have been shipping the Survey123 field app with a Beta feature that lets you bring your own web maps, vector and mobile map packages into the map. We are now finalizing this work, which should be fully supported in the 3.10 release.
  • The Survey123 feature report service is getting ready to see its first major feature update since release. We are working on supporting summary reports where you can bring all or a subset of features in your survey into a single report. As part of this effort, we are also adding new syntax to support statistics within reports.
  • Ranking question: we are working on a new ranking type of question to help you define sortable lists within a form. With the ranking question, end users will be able to express preferences over a predefined list of choices: drag and drop choices to set their order!
  • Finalizing the on-premises setup of the Survey123 website and API.
  • Improving web accessibility in the Survey123 web app.
  • Support for ArcGIS Enterprise in the Microsoft Automate connector.

A complete list of Beta features is available in the Early Adopter Community, as well as user forums and documentation. If you are interested, have a look!

Occasional Contributor III

Thanks for the hard work.  Can't wait to see the code in AppStudio in the next couple of days!

Esri Frequent Contributor

Very grateful for lines and polys now in Survey123 and the many other enhancements, Ismael! The education community (and beyond) will be most appreciative, as is the entire education team!

Joseph Kerski

Occasional Contributor III

The new survey updates look great. However something seems to have happened to the notes questions within the web creator. I have notes that come up as a warning only when no is selected in the previous question. Now these notes are viewable before the previous question is answered. Yes it is faded to give it a somewhat hidden look, however because the warning notes are red and the rest of the text is black, it really stands out even as a faded red. I’ve checked my question rules and have created a test mimic of these questions and notes but I’m still getting the same result.

New Contributor III

James Tedrick I noticed some updates were made to PKI authentication. Were any existing authentication methods for Enterprise decommissioned with this update? Our users are running into issues logging in via VPN with this latest update. When they try to add a portal they get an error message that says "Unexpected" - and when they try to log in again they just get a spinning circle. I have been able to replicate this issue. Feel free to email me at bspendlove@socalgas.com for more specific information. 

New Contributor III

James Tedrick As a side note, a co-worker on my team did test this on the Beta 2.9 version and it worked in our portal.
And as an update, it turns out that occasionally they can log in, but often they cannot. Trying to troubleshoot now whether this is a vpn or Survey123 problem or a combination of things...

Esri Esteemed Contributor

To note, I am following up with Blythe directly on this matter.

Esri Esteemed Contributor

Hi Naomi,

Can you share your XLSForm or an example that also shows this?  I tried a sample form that has a note with a relevant statement, but wasn't able to duplicate the issue.

Occasional Contributor III

Hi James

I have some images from the survey that I can share with you.  The notes, in red, should only show when NO has been select.

Below you can see that nothing has been selected yet the notes show.  In fact the question dictating to the translator note is hidden, therefore this should be doubly hidden!

Below you can see that yes is selected and that you can clearly still see the notes.

Below is the difference between the note 'showing' i.e. No selected, and the note 'hidden' i.e. Yes selected.  The hidden note is faded in comparision, but barely.

Here is an example of the rules that I am using to hide the notes.  The notes have a blank space as their title, as a title is not appropriate for this surveys question.  For this one the note is #2. I have the same rule for question 3 which leads onto note #4 if No, alternatively jumping onto the next question if yes.

All of this has been done in the web survey builder.  As mentioned when the survey was first created these notes were correctly hidden.  The survey has been republished with some minor changes to other questions further below the survey i.e. no changes to these notes or to the questions that lead to the notes.

Occasional Contributor III

Thanks for the great update! I have a follow-up question about:

As anticipated in our earlier Upcoming changes to Survey123 web form's query parameters announcement, the mode query URL parameter in the Survey123 web app now supports the use of globalIds.  To facilitate migration of your existing work, we have extended the life of objectIds in 3.9. We very strongly recommend that you transition away from objectIds as the days for them are counted!  With 3.10 we will completely drop to support and exclusively use globalds.

Is the upgrade to using GlobalIDs only require if the survey is re-published with 3.9, or is this something we should be doing regardless if using the edit mode URL parameter?

On a related note - is there any timeline on when we can expect BUG-000126498 to be resolved? This bug makes it so that when using Operations Dashboard with an embedded web form using edit mode fails to retain the geopoint questions XY location, requiring the editor of the form to re-enter the geopoint any time edits are performed. I helped to document this bug back in November 2019 and was hoping to see it addressed in this release, however I don't see it listed above.


Occasional Contributor III

Is there a beta testing opportunity for the Power Automate in 3.10?


Esri Frequent Contributor

Hi Gary Bowles‌  We will be sharing instructions at earlyadopter.esri.com to help you configure the Survey123 connector in Power Automate against ArcGIS Enterprise.  Please stay tuned through earlyadopter.esri.com. Thanks!

Occasional Contributor III

Thanks Ismael. Looking forward to getting Power Automate working in ArcGIS Enterprise.


Esri Frequent Contributor

Hi Erica Tefft‌ 

The upgrade to globalId implies:

  • Republishing your survey using 3.9
  • Modifying your apps so the globalId parameter is used instead of the objectId

BUG-000126498: This is still under investigation.

New Contributor II

Awesome!!! Thanks a lot Ismael, appreciate all your works. ESRI Rocks!!

Occasional Contributor III

If additional examples/evidence are needed of BUG-000126498 I am happy to provide it.

Esri Esteemed Contributor

Hi Naomi,

It looks like you replied via e-mail; GeoNet doesn't include the images from e-mail responses.  Can you update your post via the GeoNet website with the images?

Occasional Contributor III

Sorry, I've updated it with the photos back in.  

I've just been called by one of our uses who was worried when she saw the red text appearing even with yes ticked!

Esri Esteemed Contributor

Hi Naomi,

I am able to duplicate the behavior you are seeing with a web designer created form.  You can download the form into Survey123 Connect and republish; this resolves the issue with no change to the form design.

Occasional Contributor III

Hi James

I'm a bit nervous trying to publish from Connect as I get an error message XLSForm converted with warnings.  It then goes on to mention my notes fields as 'Question has no label'.  This is our live form we are using for our COVID response so I don't want to stuff it up.

Esri Esteemed Contributor

Hi Naomi,

You can safely re-publish - the warning appears because some of your notes do not have labels (the bold part of a question).  By the way, we are working on an incremental update to the website that should address this as well.

Esri Contributor

Hi Naomi,

This is fixed on Survey123 web designer and web form, please have a try.


Jody Zheng Liu

Occasional Contributor III


It's looking good from my side   Let's see if we hear anything from the rest of the team when they jump back in tomorrow.

Occasional Contributor III
Occasional Contributor

Any possibility that multipoint geometry will be available in addition to point, line and polygon as a geometry type? 

Esri Esteemed Contributor

Apologies for the delay - the AppStudio template is now available.

Occasional Contributor III

No problem, thanks for the great work!

Occasional Contributor

You can use question placeholders when defining the report output filename in the Survey123 website, or from the Integromat module.

Could you give some guidance on how to define the output filename in Integromat?

Esri Esteemed Contributor

Hi Maaza,

Apologies for the delay in response.  We currently do not have multipoint geometry planned - can you provide an example of a collection workflow that would collect a multipoint geometry?

Esri Esteemed Contributor

Hi Dante,

Apologies, but support for custom filenames has not been added to the Integromat connector yet; the enhancement in this release timeframe was to select the output file type (now that PDF is supported). I've noted this for a future enhancement.

Occasional Contributor

Ok no worries! Wanted to make sure I wasn't missing something. Having it in the Integromat module would definitely be appreciated!

Occasional Contributor

Hello, James,

I had raised the same question before and have given a set of scenarios that would make multi-point desirable geometry.  We are a transportation services agency and perform inventory of multiple assets.  Even though sometimes it would make sense to keep these assets in individual features, there are many instances that would make it easier to aggregate points.  One instance where multipoint geometry are a perfect fit and nothing else comes near is when one wants locations of a project where exactly the same treatment is carried out on multiple geographically (spatially) dispersed area.  The current solution is to have many point features that have the same attributes, we would like to have all the locations under one feature.  You may say, what about repeat points?  That is what we want to avoid! the extra management challenge associated with repeats is eliminated for many instances if there was a possibility of multi-point geometry store.  Some of the projects currently in our system include replacing sign posts along a roadway.   The work is exactly the same and the project has several hundred locations.  Multi-Point feature would be just a solution that fits the need. 

I am bit surprised by the delay in having a multipoint geometry as part of the arsenal!  It is after all  a polyline without the line, that would make it lighter and easier to maintain.  Why is it so difficult to have this feature when even shapefiles have multipoint geometry?

There are many use cases but I think the flexibility to have one more toolset in solving varied problems is worth the little effort it takes to add multipoint geometry.

Thank you, 

New Contributor III

I've noticed a few loopholes on the Survey Update notification and there are quite a few scenarios where a user will never see the message and will continue to submit records with an outdated form. This has caused a problem for my 20 field workers and subs who don't regularly check for updates and utilize the Collector > Survey123 relationship. They also do not "close" or kill Survey123 to revisit the "My survey" page. We have to resort to using Version Check command to pass a "version # in Collector/Explorer/Webapp to the Survey e.g. 1 = 1 to display a relevant question telling the user their form is out of date.

Here are a few examples of this that i could find. This is not all inclusive and is just quick notes  

  1. When a user is already in the Form and creates a new Survey. They will never see the Your form is out of date message. They need to "hit back" and see the My Surveys page on the device for it to do the "Search" and see that there is an update.
  2. If the user is in the form "Details page" were the outbox, sent, drafts etc" the page will not prompt a user to update the form.
  3. If the user is Opening Survey123 from outside the application using a Custom URL link Collector/Web map. it will not prompt the user to update the form. it will directly initialize the form before the "form version" is checked. Typically after submitting a record when Survey123 was not currently active in the iOS aka not loaded in memory. it bumps back out to the main Select a survey page because it doesn't remember what form it was in.
  4. if the user was already on the form page and clicks Collect, then initializes the form from outside of Survey123 (collector/weblink) it will prompt the user to open the page. 
  5. If the user clicks to quickly when Survey123 opens up the Check will not be performed and they will continue to collect using outdated forms. This is that brief period of time where Survey123 is authenticating to either AGOL or Enterprise login. Since a user is able to continue to collect data w/o being signed in or having internet. There is a brief 1 to 2 second delay before it begins the search.
  6. Clicking Continued without Update, doesn't remind the user again that their form is out of date unless a specific scenario above is triggered or they go back to the main page. This isn't necessarily bad but could be if prolonged use of Survey123 app.

Its my assumption that the Form Notification Search only occurs on the "My Survey" page or if the application is closed and reopened. Many of the loopholes can be solved by simply "closing" and reopening the application on the iOS. But there still the chance a user can by-pass before the login is complete. There is of course having our field crews just actively go to the DOWNLOAD FORMS page every day and hit refresh... but thats never going to happen

This testing was done on an iPhone 11 Pro Max iOS  13.4.1 using Survey for iOS Version 3.9.148, using both AGOL and ArcGIS Portal published data and accounts.

I have opened a case with ESRI Support here 02555878 Case number. If others who like to request bug/enhancements please submit your own, you could reference the case above.

New Contributor II

The ability to include question responses in the feature report name is very useful.  I was wondering whether it is possible to use this functionality when producing reports using a script via the survey.generate_report method?  As I understand it, the report_title argument is only used internally by AGO and not to name the output file that is downloaded.

Also, is it possible to produce PDF reports using this method?

Esri Contributor

Hi Ismael,

You mentioned the fix of iOS crashing bugs in the 'Next Step' and they were planned to be fixed by end of April. I wonder if these bugs have been fixed.

Thank you.