Latest Contributions by IsmaelChivite

AuGeo, latin for ‘augmented’, is an Esri Labs initiative to explore the possibilities of using ArcGIS data in an augmented reality environment. Available to ArcGIS users (Viewer User Type and above) for free in the iTunes and Google Play stores, the AuGeo mobile app allows you to easily bring data from your existing ArcGIS point feature layers into an augmented reality mobile app. At Esri Labs we see many potential uses for Augmented Reality in GIS. While we love maps, locating assets around you can be easier through the lenses of a camera on your phone or tablet. Through an augmented reality view, we can more intuitively represent hidden assets (underground, covered by vegetation or snow), reducing the time needed for people to find what they were looking for. Will augmented reality help perform asset inspections more quickly? Will it guide rescue teams towards a fire hydrant that otherwise would be missed? Will it provide the ultimate mobile user experience for the most technology averse real estate agent? Will it be the next cool way to explore tourist destinations in a city? As a Research Project from Esri Labs, our intent with AuGeo is to make interesting technology available to you, so we can explore the possibilities together. To start with AuGeo, all you need is an ArcGIS Online subscription, some point data and a mobile device. Preparing your existing data for use within AuGeo is very straight-forward as described in this tutorial. We encourage you to experiment with AuGeo using your own data and scenarios. In our own experience, how accurately your GIS data is shown in AuGeo’s first person view is highly dependent on the quality of sensors in your device. The location accuracy and compass calibration in particular are key.  Of course, the quality of your own GIS layers is critical as well. Only through use and experimentation you will learn what practical uses you can give to AuGeo. We would love to hear your feedback through our Github Repository and evolve what already looks like a gold (Au) mine of possibilities. The source code of this application is also available with AppStudio for ArcGIS. If you are a developer (no need for mad skills by the way), you can embed the AuGeo functionality into your own applications, or even brand AuGeo for your own purposes.  We took the AuGeo AR view for example and embed it within another Esri Labs app called Trek2There.  Common questions: Do I need an ArcGIS account to access AuGeo? Yes. You need to sign-in with your ArcGIS credentials to start using AuGeo.   Initially, you will only see a handful of sample layers we have published including coffee places and such, but you can add your own point layers. How can I add my own data into AuGeo? Follow steps as described in this video-tutorial. Why I cannot see any data when I select a layer too be added to the app?  After selecting a layer you need to use the  Refresh Data button to download data into your device. We use the current extent of the map  to define the data to be downloaded. Does AuGeo work offline? Yes, once  you have downloaded the data you can use it while disconnected. Can I display polylines and polygons? Not at the moment. AuGeo right now only supports points. Why is the location of my GIS features not correct in the First Person View? Your location or  compass calibration may not  be accurate. Will AuGeo drain my smartphone battery? It will! Just like when you keep your camera preview constantly open. Is AuGeo a supported product from Esri? AuGeo is supported through the public AuGeo Github repo. It is not an official Esri Product and as such it is not supported by Esri Technical Support. How was AuGeo built? AuGeo has been built on top of AppStudio for ArcGIS. Esri Labs projects are released to public as non-commercial offerings but are NOT official Esri products. These projects do not have to go through the standard rigorous software development lifecycle and testing as other official Esri products. Esri Labs projects may not be holistically tested or documented, and are NOT supported by Esri Technical Support. ... View more

Our Developer Summit conference is approaching fast.  We at Esri always put a lot of energy into this event. It is an opportunity to meet face to face with many of you, share our work, discuss new features and road map plans.  2019 will be very special for us as we will make 4 years since we announced the graduation of Survey123 from an Esri Labs proof of concept into a full fleshed ArcGIS Product. This year we will announce details on ambitious plans for the new releases to come: direct connections to external GNSS receivers in the field app, added support for polygon and line features, a release date for our Survey123 report services, enhanced integration with Spike laser measurement tools, a new extensibility framework and many more great news. Members of the Survey123 team from our offices in Beijing, Australia and Redlands will come to Palm Springs. We are really excited for the opportunity to meet you again. Today we want to share with you some tips and a guide for anything Survey123 at these events. The Events App I highly recommend that you download the Esri Events app, so you can always be on top of last minute changes and manage your schedule.  As of the time when I write this post the detailed schedule is not yet up in the app, but it will be available shortly.  This app will be a good companion throughout the entire conference. Pre-Summit Hands-On Training Our Esri Pre-Summit Hands-On training sessions take place on Sunday 3 and Monday 4. These are full day sessions with a mix of lessons and practical challenges. You bring your own laptop, so you can take all homework home. Massive learning guaranteed!   Our sessions start at 8:30 sharp. You can register starting at 7:30 at the Hotel Riviera. Mastering Smart Form Design with Survey123 and XLSForm. Sunday, March 3 from 8:30am to 5:00pm Royal II at Hotel Riviera Palm Springs. Extending Survey123 for ArcGIS. Monday, March 4 at Royal II from 8:30am to 5:00pm Royal II at Hotel Riviera Palm Springs Esri Showcase and GIS Solutions Expo   The GIS Solutions Expo area opens Monday from 2:00pm to 7:00pm at the Primrose Ballroom. This is a great place to meet many partners who work closely with Survey123.  Here are a few: Microsoft. Diamond sponsor this year. Showcasing the Survey123 Microsoft Flow connector. Bad Elf, EOS Positioning Systems, Trimble, GENEC:  Providing GNSS receivers for which Survey123 3.3 will provide direct connectivity capabilities. Zebra Technologies: Manufacturing rugged devices compatible with Survey123. Geo Jobe: Custom software development services. During this time, you can also swing by the Esri Showcase area to visit the Survey123 team in the Apps area. On Tuesday from noon to 8:30pm, Wednesday from 1:00pm to 6:30pm and Thursday from 9:00am to 4:00pm the Esri Showcase will continue open in Oasis 1 and 2. Come to the Showcase and look for the Survey123 booth. This is your chance to meet people from the Survey123 team, have a relaxed conversation, ask questions and network with other Survey123 users. Meet the Teams The Meet the Teams event will take place from 6:00pm to 8:30pm in Oasis 1 and 2 on Tuesday. In other words, at the Esri Showcase area. Drinks, food and GIS to spare. Esri Dev Summit Technical Workshops These are 60 minute sessions. All take place in the Palm Springs Convention Center. A good place to learn from the best, ask questions and meet other Survey123 users. What's new in Survey123 for ArcGIS Wednesday, March 6 from 5:30pm to 6:30 pm San Jacinto room. Extending Survey123 for ArcGIS Thursday, March 7 from 5:30pm to 6:30pm Pasadena/Sierra/Ventura rooms. ArcGIS Mobile Apps. The Road Ahead Thursday, March 7 from 2:30pm to 3:30pm Primrose B room. Other related Technical Workshops If you plan to extend or customize Survey123, the AppStudio sessions are a must. Building Native Cross-Platform Apps with AppStudio: An Introduction Tuesday, March 05 from 1:00pm to 2:00pm Mesquite C Building Native Cross-Platform Apps with AppStudio: Advanced Topics Wednesday, March 06 from 2:30pm to 3:30pm Primrose C-D   Survey123 Demo Theaters Short and to the point sessions focusing on very specific topics. Live demos and time for questions are guaranteed. All Demo Theaters take place at the showcase area. Workflow Automation with Survey123 Thursday, March 7 from 9:00am to 9:30am Demo Theater 2 Inter-app Communication with ArcGIS Apps Thursday, March 7 from 2:30pm to 3:00pm Demo Theater 3 Mobile Device Management and ArcGIS Field Apps Thursday, March 7 from 3:00pm to 3:30pm Demo Theater 3 Survey123 Special Interest  Group (SIG) This session is a great place to mingle with other Survey123  Ninjas and members of the Survey123 team. Keep your own lunch box because this SIG takes place at noon. We will break the ice with help from a special guest who will share his own work deploying Survey123. Then we will open an interactive Q&A session. Survey123 SIG Thursday, March 7 from noon to 1:00pm Primrose A at the Palm Springs Convention Center ... View more

[Updated February 28, 2020] [Updated April 2, 2020] [Updated July 13, 2020. Added autoRefresh] [Updated March1, 2021. Added mode copy] [Updated September 15, 2022. Added ?hide=leaveDialog] [Updated September 22, 2022. Added ?forceRecalculate] [Updated January 9, 2023. Updated ?forceRecalculate to ?recalculate] [Updated August 25, 2023. Updated sample links]   Many web applications support the notion of URL parameters and Survey123 web forms are no exception. URL parameters allow you to dynamically pass data into your survey. This data can be used to prepopulate questions, hide questions, change the language of a form and many other things with your survey form. In this blog post, I will explore the options available in detail.   Before I start, I want to clarify that in the past we already covered how to use the Custom URL Scheme in the Survey123 field app. The concept of a Custom URL Scheme is similar to URL parameters, but they are two different things: the Custom URL Scheme applies to the Survey123 field app and the URL parameters discussed in this post only apply to web forms. That is, to forms loaded within a web browser, as opposed to loaded into the Survey123 field app in your device.   With that, lets get started:   The Basics   Lets first get familiar with how surveys get loaded into the Survey123 web app. Take the following URL:   https://survey123.arcgis.com/share/1cb28b212b5542acbbdbaa35feba0765    The first part of the URL refers to the Survey123 web app: https://survey123.arcgis.com/share/ We host the Survey123 web app in our ArcGIS Online servers, and it is used to render your surveys as web forms.  The second part of the URL is the unique identifier of your survey. In this particular case, it is: 1cb28b212b5542acbbdbaa35feba0765   The complete URL will open the Survey123 web app in your web browser and immediately present the survey id specified , in this case it is an Quick Tree Hazard Report survey.   So far, no URL parameters have been used, but now we are going to add one parameter to automatically populate one of the questions. Try the following:   https://survey123.arcgis.com/share/7fdcf75abfad4ae29f0156e161740d27?field:submitted_by=Fernando    You will notice that now the Submitted By question is automatically adding the name Fernando in the survey.  Immediately after the basic URL of the web form, I added a question mark (?). The question mark indicates that what follows are URL parameters. Next, I added the name of the parameter, which in this case is field:submittedBy and a value for that parameter: Fernando after the = sign.   You can add multiple parameters by simply separating them with an ampersand (&). For example:   ...?field:submittedBy=Fernando&field:common_name=Oak   Next, lets learn about the different URL parameters you can pass to Survey123 web forms. Setting values on questions (field:fieldname)   In the previous section you saw how a URL parameter can set a value to a question in your form, but lets take a closer look at how it works. The syntax is simple:   ...?field:common_name=Oak   The name of the parameter is made  out of two distinct parts. First, you have the field: suffix and then you have the name of the question where you want to put a value.  Figuring out the name of a question can be tricky. The question name should not be confused with the label of the question. The label is what users see in the form. The question name represents the column in your feature layer  where the response will be stored.    If you author surveys in Survey123 Connect, I am sure you already know what  I am talking about: The question name is represented by the name column in the survey worksheet of your XLSForm.  If you design your forms in Survey123 web designer, then finding out the exact name of your questions deserves a more detailed explanation.   After adding a question into your survey in web designer, you need to set its label and other properties, but not the name. The name of your question is automatically assigned by Survey123 web designer.  Assigning a valid question name needs to follow very strict rules (the name cannot start with a number, cannot have special characters, or  spaces and must be unique within your entire form) and that is why we put that out of your way in designer. This simplifies  authoring for beginners, although in cases like this it obscures what is really going on.   In any event, you can look at the question names by using the 'Modify Schema' link during the publishing process.      The Modify Schema dialog will let you define the exact names of your questions only when you add your questions to the form for the first time. Once you publish your survey, questions that already exist in your survey will appear as read-only in the Modify Schema dialog.   In my case, I really did not want to change anything, I simply wanted to get the names so I could use them with my URL parameters.   Question names are case sensitive. You must pass the exact name. For example, in the oak survey, field:commonName=Oak will work, but field:CommonName=Oak will not work. ...?field:common_name=Oak     Centering geopoint questions (center)   The center parameter lets you set the default location of the geopoint question in your survey.  It looks like this: ...?center=34.1,-117   This parameter accepts a latitude/longitude coordinate pair where the values are separated by a comma.  Now. there are a couple of important things to remember when using this parameter:   This URL parameter only takes effect if the geopoint question is flagged as required, AND If authoring from web designer, the option to 'Ask user's location when opening this question' must be disabled'.   If the geopoint question is not required or the user location is used, the values from this URL parameter will be overridden at runtime when the end-user opens the question.   Hiding questions and survey elements (hide)   The hide parameter is handy when you want to control visual aspects of your survey. You can load a survey and hide questions, the navigation bar and more.  This parameter takes as an input more or more values, separated by a comma.   Parameter Value Description navbar Hides the navigation bar. That is, the bar at the top of the survey that includes options to login/logout and to change the language. This is particularly useful when you embed your survey within a website. Example. header Hides the survey header. The header typically includes the title of the survey or alternatively a banner image. This is particularly useful when you embed your survey within a website. Example. description The description element is optionally included if you author your survey in web designer. footer Hides the footer element, which includes the Powered by Survey123 link, or an alternative link if you modified it. Also useful when embedding your survey within a website. Example. theme Use the theme value to disable any custom theme applied to your survey.  Example. field:fieldName This value is used to hide specific questions within your survey. If you want to hide multiple questions, simply add their names separated by a comma. If you want to hide a question within a group, reference it by its full path: field:groupname/questionname. Example hiding the Submitted by and Survey Date questions. leaveDialog Use this value if you do not want the web browser to request user confirmation before leaving the web browser survey page. IsmaelChivite_0-1663634138443.png     The hide parameter is very flexible, allowing you to hide multiple elements at once. That is, you can hide the navigation bar, the footer, description and as many questions in the survey as you like.   To hide multiple elements, you simply need to keep adding comma separated values to hide the different components. For example:   ...?hide=field:submittedBy,field:surveyDate,theme,footer   Another interesting thing you can do is hide a question and at the same time set its default value through a URL parameter. For example, you can hide the Submitted by question in the Oak survey and also set a value for it through your URL parameter.   Adjusting the width of the survey in the screen (width)   The width parameter sets the width, in pixels, of the survey in the screen. For example: ...?width=1500 Automatically reload the survey after a record is submitted (autoRefresh)   Using the autoRefresh parameter your survey will reload immediately after a survey is submitted. This is very useful when people are expected to repeatedly send data from a survey. ...?autoRefresh=true Do not forget that the parameter is case sensitive. Works with version 3.10 and above.   Edit existing records and opening surveys in view-only mode (mode)   The mode parameter supports the values edit and view.  Combined with the globalid parameter, you can easily open specific records in edit or view modes. For example, here is how you can update an existing record: ...?mode=edit&globalId=56cf0f7a-def7-4402-bd2c-536b717637bb There is a lot you can do with this (mode=edit) alone. Go to https://community.esri.com/groups/survey123/blog/2019/05/24/survey123-tricks-of-the-trade-editing-records-in-a-web-form for more details.   Similarly, you can also open a survey in view-only mode. ...?mode=view&globalId=56cf0f7a-def7-4402-bd2c-536b717637bb   If you get an error like shown below when opening a record in view mode, you will need to adjust the sharing.     When a survey is shared for viewing, the Survey123 web app uses a special feature layer view built so users cannot edit your data. This feature layer view is created only when you share your survey results for viewing. That is done through the Collaborate tab in the Survey123 website, by selecting the Viewer section and then sharing with the appropriate groups (and clicking save... ).     Recalculate values when in edit mode (recalculate)   Use the recalculate URL parameter to force certain fields to be recalculated, even if the record is opened in edit mode. This can be very handy, for example, if you want to record the name of the person editing the record, or to refresh the date when the record was last edited.   ...?recalculate=field:question1,field:question2 Copying (cloning) existing records   The mode parameter supports a third value: copy.  It is used to load the smart form with information from an existing record and to create a new record when the user submits: ?mode=copy&globalId=56cf0f7a-def7-4402-bd2c-536b717637bb    Set the app that will open your survey (open)   You can use the open URL parameter to determine the app to use with survey. Valid values for this parameter include: web, native and menu.   ...?open=menu  Parameter Value  Description web Opens your survey in the Survey123 web app, as a web form. This is the default.  native Will open your survey in the Survey123 field app. This option will only work if the Survey123 field app is already installed in the device.  menu Will open web page to let the end user decide if the survey should be open in the Survey123 field app or within a web browser.    Set the language of your survey (locale)   You can use the locale parameter to define the language of your survey. For more details on mutiple-language surveys refer to https://community.esri.com/groups/survey123/blog/2019/01/23/introducing-multiple-language-surveys  The locale parameter accepts ISO language codes. For example: locale=zh-cn  or locale=en. Below is a clever example where this parameter is used to help end users switch the language of the survey right from within a note in the form.  You can see the different links added. Each of these links uses the locale parameter to reload the form in a different language within the web browser. IsmaelChivite_0-1614705559990.png Encrypt URL parameters   If you are concerned about having your URL parameters in clear text, you can encrypt them. To learn more check out Survey123 Tricks of the Trade: Encode URL parameters in the web app. ... View more

National Weatherperson's Day, also known as National Weatherman's Day, is observed on February 5 primarily in the United States. It recognizes individuals in the fields of meteorology, weather forecasting and broadcast meteorology, as well as volunteer storm spotters and observers. It is observed on the birthday of John Jeffries, one of the United States' first weather observers who took daily measurements starting in 1774. Jeffries also made the first balloon flight over London in 1784 with the purpose of gathering data for a scientific study of the air at high altitudes. Our forecast for the 3.2 release is as follows: Bright like the sun, new features and enhancements in the morning, particularly in the Survey123 website and web designer. A joyful rain of fixes for the Survey123 field app at night, including massive improvements to repeats and nested repeats.  Pages for your web forms In this update you can organize questions in your surveys across multiple pages. Pages are particularly useful when working on very large forms, helping you logically organize your questions and giving end users a sense of progress across the entire survey. In the example above, I added a welcome image and text on the first page to create a cover for  my survey. Note that the first page does not expect any input from the survey. It is just a welcoming page, or cover.  Next, I organized the actual questions within my form into pages, giving each page a descriptive title at the top.  As users move from page to page, a progress bar at the bottom shows how close they are to the end of the survey. You can combine groups and pages to further help organize questions within your survey! If you use web designer to create your surveys, you will find that we have added a Page option in the main panel. Just like you do with other question types, simply click on Page, and it will be added to your form. You will be able to drag and drop questions into your new page, move questions from one page to another and even merge and duplicate pages! If you want to work with pages in Survey123 Connect, you need to do two things: First, in the settings worksheet of your XLSForm, you will set the value of the style column to pages. Then, in the survey worksheet, you will use the field-list appearance for any XLSForm begin_group question type that you want to turn into a page.  Also note that when using the pages style, pages will be automatically created for any question outside field-list groups. Whilst the implementation for pages is complete in our web form, currently in the field app constraint and required checks will not be performed when you leave a page.  These checks will only be done when you attempt to submit the survey. In some scenarios this can make it difficult for end users to identify the exact question in the form where the validation rules were broken. Make sure you define good error messages for your required and constraint rules. Other than that, pages work pretty well in the field app! Embedded public web forms You can now embed public web forms in your own web site. As shown below, the Collaborate tab of your survey will now include an Embed option from which you can copy the HTML code needed to embed your survey within a web site. A handful of embed options let you quickly configure your embed HTML code to hide elements of your survey that you may want to hide, such as the header, sign-in, multiple language options, footer, etc.  You can even disable the theme colors to provide a more neutral presence of your embedded survey within the web site. Below is an example showing a Survey123 form embedded within a web page.  Note that the header, footer and themes have been disabled to make the survey fit better within the web site. Better word clouds The Survey123 website includes a number of reporting capabilities to help you understand data captured through your surveys. The Analyze page, for example, aggregates responses for categorical, date and number questions and creates charts and maps to more quickly identify trends on your data.  Questions with free text are always trickier to aggregate, but that is where word clouds come to help. A word cloud takes the most common words found in your data and sizes them according to popularity. The bigger the word, the more repetitions. It is a simple concept but it often gives great insight.  Unfortunately, the most common words in our language are far from interesting in this context. Think about it: this, that, of, a...  all pretty useless stuff in a word cloud, don't you think?  These words are known as stop-words, and now you can set a filter to ignore them. In English at least. Here you can see how word cloud filters made a difference for our friends at City of Lakeland, in Florida: In this particular scenario, the survey asked people in the city 'What are your thoughts on how can we better educate drivers to pay attention?'. The most popular words among the responses are 'the', 'and', 'to' and 'of', but if we  apply the stop word filter, much more relevant words will come out:  speed, signs and people.  With stop word filters you can more easily understand certain relevant trends in your data. More on custom themes We introduced Custom Themes not long ago. Definitely a good addition to give your surveys a nice final touch! If you haven't already, I highly recommend you watch this video-tutorial or read the Introducing Custom Themes blog post. In this update 6 new theme templates have been added. 5 of them will help you quickly switch through different color combinations. You can also make tweaks in them, of course, but they provide a nice start.  The sixth template is more interesting, in that it will mirror the Shared Theme of your ArcGIS organization.  If you are not familiar with this concept of Shared Theme, have a look at Ian's blog post Introducing Shared Theme: a new app styling capability in ArcGIS Online.  The Shared Theme is set by the administrator of an ArcGIS Organization defining the basics for styling configurable apps in it: text and background color, etc.  Now, you can easily match that style! Web designer: Option to automatically center map at the device's location in web forms A new option has been added in web designer to automatically center the map at the user's location when a geopoint question is open within a web form. Lets describe in more detail what is going on here, because this option only makes sense once differences between the behavior of geopoint questions across web forms and the Survey123 field app are understood.  Geopoint questions in the Survey123 field app are by default centered at the user's location. In a Web Form, the behavior is very different.  When your geopoint questions are shown within a web browser, the location of the map remains as set by the author of the survey. The Survey123 web app by default will not attempt to gather the user's location. Otherwise, as soon as the survey is loaded, the web browser will automatically present a dialog to the end user asking for permission to gather the device's location.  Without proper context on why that  message is appearing, this would cause distrust in many users. The user can change the location of the map by either manually panning the map or centering it at a particular address or at the user's location. By enabling this new option, the map, once in edit mode, will automatically center to the user's location.  This will trigger the web browser to require confirmation before handing over the location to the Survey123 web app, but this will happen in context.  Users will understand at that point why the survey is attempting to gather their location. For the reasons described above, this new setting has no effect when the survey is loaded in the Survey123 field app. Other enhancements and fixes Survey123 Website BUG-000112899 Publishing a survey on survey123.arcgis.com connected to a Portal for ArcGIS using Integrated Windows Authentication (IWA) returns the error message, "Unable to publish the survey. Unexpected token < in JSON at position 0". BUG-000116898 Renaming the survey under 'Edit Survey Info' in survey123.arcgis.com will cause the feature service to change the name from _fieldworker to _stakeholder. BUG-000117623 When survey123.arcgis.com is accessed via Portal and only one record is present in the service, the default extent and zoom level configured on the survey are not honored when viewing from the Data tab. BUG-000116269 When printing a web map in a custom report from the Survey123 for ArcGIS website, at least one element of the web map must be public, otherwise the error message, "An error occurred while generating report(s)" is returned. BUG-000117239 Survey123 does not honor survey’s viewer collaboration with a group in ArcGIS Online if the survey has been authored through Survey123 Connect using an ArcGIS Server secured feature service added to ArcGIS Online as item with Credentials stored. BUG-000116800 Reports generated from the Survey123 for ArcGIS website show the Object ID as a date. BUG-000116268 When printing custom reports from survey123.arcgis.com, the web map in the report fails to display all layers in the map. BUG-000118284 In Survey123 for ArcGIS, the map scale setting is not honored when including a map in a report. BUG-000118703 Surveys with calculate type questions that use pulldata() on a geopoint question within an if statement display the error "Error: Initialing Form... FormLogicError: pulldata with incorrect number of parameters found: pulldata('@geopoint', // , '')" and load without form logic when opened in the Survey123 Web App. Custom Reports can now access all fields within the underlying feature service. Custom Report syntax in Microsoft Word documents is now checked immediately after uploading the template. Added support for the XLSForm function @property in Web Forms. Survey123 Connect Survey123 Connect will no longer overwrite survey settings (such as web hook configurations) updated through the Survey123 website. BUG-000111392 Survey123 Connect installed on a Windows 2012 R2 machine crashes when publishing a survey to Portal for ArcGIS 10.5.1 configured with enterprise logins. BUG-000119026 Delete refresh token stored in SecureStorage if auto login fails with invalid refreshtoken error. BUG-000097165 - Copy images used for form background into the media folder. Survey123 Field App Various fixes affecting repeats and nested repeats (BUG-000117852, BUG-000117987, BUG-000118094, BUG-000118449 and many others). BUG-000117852 : Surveys for geopoint, picture and select one questions are not displayed for the second and subsequent repeat questions/related tables in sent folder if those questions are relevant questions. BUG-000117987 : Calculation fields fails to retain submitted values in Inbox if the field are part of "Repeats". BUG-000118094 Relevancy questions within repeats do not save the information when the survey is saved as a draft. BUG-000118449 : When including a signature field in a relevancy controlled group within a repeat in Survey123 Connect, the first signature entered is not displayed in the outbox (drafts). BUG-000117493 "SSL Handshake failed (6)" error is generated in Survey123 app when using Android 7.0 or higher and using non-CA certificates for Portal. BUG-000110786 - Survey123 cannot change from an Windows Authentication (IWA) portal to another. BUG-000113293, BUG-000113294 - User signed out when losing network connection. BUG-000098854: Survey123 App Portal cannot be added after tapping "Add Portal" in Windows Mobile. BUG-000118375 Mathematical calculations from Inbox do not trigger when NaN or null values are used. BUG-000106578, BUG-000112873 - When choice_filter used, the name text is saved as the data value, instead of the label text. Did you know that using XLSForm you can choose to save the label of the selected item in a list instead of the name? For more details see: https://community.esri.com/groups/survey123/blog/2018/12/02/survey123-tricks-of-the-trade-xlsform-functions-for-lists  ENH-000109073 - Include a comma (thousands separator) in decimal questions. Various bug fixes for localization issues. For more details on the 3.2 release, check out our What's New Help Topic, which also includes an archive of all new features added in previous releases. ... View more

[Updated December 12, 2020] [Updated November 14, 2023. Added link to Survey123 web designer video]   Using multilingual surveys you can present questions to your audience in the language they are most comfortable with, and analyze all survey results in a single data set. This article describes how to author multilingual surveys in Survey123 Connect.  If you are interested in translating your surveys using the Survey123 web designer, check this video instead.  Before we start   Before we get into how to translate your survey, I want to discuss how the Survey123 apps handle multiple languages. First of all, we need to draw clear distinction between the Survey123 app, and your own survey. The Survey123 web and field apps are translated by Esri.  When you open the Survey123 app in your device, it will automatically switch to the language used by your operating system. The list of supported languages includes: Arabic, Bosnian, Catalan, Croatian, Czech, Danish, Dutch, English, Estonian, Finnish, French, German, Greek, Hebrew, Hungarian, Indonesian, Italian, Japanese, Korean, Latvian, Lithuanian, Norwegian, Polish, Portuguese (Brazil), Portuguese (Portugal), Romanian, Russian, Serbian, Simplified Chinese, Slovak, Slovenian, Spanish, Swedish, Thai, Traditional Chinese (Taiwan), Traditional Chinese (Hong Kong), Turkish, Ukrainian, and Vietnamese. It is not possible for you to add additional languages. If your operating system uses a language not present in the list above, the app will default to English. Translating the survey that gets loaded into the Survey123 app, is your responsibility. It is up to you to decide how many languages you want to support. When your survey is loaded in the app, Survey123 will automatically try to find a translation of your survey that matches the current language used in your operating system. The match is performed comparing the language BCP 47code of your operating system with that of languages available in your survey (more about this later).  If a match is not found, the survey will use the default language as defined in your XLSForm.  Be aware that the list of supported languages for your survey translations is much larger than the limited number of languages we support in the Survey123 apps. For example, while the Survey123 apps are not available in Euskara (a language spoken in Spain and some parts of France), you can still translate your survey to Euskara.  The Survey123 app will be shown in Spanish or French, but your survey could be presented in Euskara. The same applies to other languages such as Welsh and Swahili. The Survey123 apps (web and field), will also let the user manually change the language of the survey. For example, if you translated your survey into 3 languages, the list will show these three languages.  The language chosen for your survey will display question labels, notes and choices in the corresponding language. Additionally, numbers and date values entered by the user within your survey will be formatted accordingly as well. Adding language codes to XLSForm columns   There are many aspects of your smart form that can be translated. Question labels, hints, constraint and required messages, choice labels and even media (banners, diagrams...).  The technique used to add translations to all these is the same.  The following table demonstrates how to translate question labels:   type name label::English (en) label::Greek (el) select_one animal animal What is your favorite animal? Ποιο είναι το αγαπημένο σας ζώο   Note that each language column is qualified with a descriptive string for the language it represents, followed by its corresponding BCP 47 code  enclosed in parenthesis. For example, the XLSForm column with the question label in Spanish is label::Español (es), and the label for English is label::English (en). The hint, constraint_message and required_message XLSForm columns are translated following the same pattern. For example:   type name        label::English (en) hint::English (en) select_one an animal What is your favorite animal? Choose an animal from the list   And the same applies to the choices worksheet in your XLSForm:   list_name name label::Español (es) label::Ελληνικά (el) media::image::Español (es) media::image::Ελληνικά (el) animals cat gato γάτα cat_es.png cat_gr.png animals bird pájaro γάτα bir_es.png bir_gr.png   Once you start adding new languages into your survey design, you will want to add translations for every question and choice label at the very least. If you use optional columns such as hint, contraint_message or  required_message, make sure you translate them into every language. The same goes for the media, audio and image columns!   Translating the survey header (title), footer and other elements   There are a number of survey elements that are translated by adding note questions with specific names into your survey design. The next screenshot provides the details:   006 Survey123 Multilingual Support.png   The survey header (title) is used in both the Survey123 field and web app. The remaining elements (submit button text, footer and thank you screen), are only relevant in the Survey123 web app.   How to launch a survey using a specific language   When a multilingual survey is loaded into the field or web app, Survey123 will automatically try to match the language of your survey with the language of your operating system.  This is why using the ISO codes is important.  For example, if the language set in your operating system is (es), Survey123 will look for the (es) translation in your survey and if found, switch the language accordingly.  If no match is found, then the default_language will be used.  The default language is defined in the settings XLSForm worksheet:   form_title form_id instance_name default_language Multiple Languages     English (en)   If using the Survey123 web app, you can also always force a survey to be displayed in a specific language (independently from the language of the operating system).  This is done through the lang URL parameter. For example:   https://survey123.arcgis.com/share/{itemID}?locale=es   Of course, end users always have a choice to manually change he language if they choose to. Both the Survey123 field and web apps will provide a menu listing all the available languages. How to tell in what language the user completed the survey   Use pulldata("@property", 'language') to retrieve the language used by the user to complete the survey. You can use this expression in a calculate question for example. type name        calculation calculate surveylang pulldata("@property", 'language')   Other resources   Create the whale survey—Monitor Whales with a Multilingual Survey | ArcGIS  Multiple language support—ArcGIS Survey123 Help Topic  Multilingual surveys, YouTube video tutorial   ... View more