Latest Contributions by ZacharySutherby

Hello @MihaRobar,  At this time smart assistants in Survey123 do not support OCR text extraction. We have an issue in our backlog to support this in the future.  ... View more

Hello @TaylorGroves, Unfortunately pulldata("@layer") is an online only function at this time and does not work offline. We have an internal issue to support this in the future, but is in our backlog.  ... View more

Hello @Cristian_Galindo @AbraaoAlves @EuSau,  Thank you for your interest in automating publishing Survey123 surveys! We are excited to note that the ability to publish surveys using the ArcGIS API for Python is ready to test in a Beta state!  Please check out our Early Adopter Community documentation to get started configuring your environment to test. We are planning on holding a live beta testing event mid January focused on creating and publishing surveys through Python. I'll add another comment when the registration is ready.  Please feel free to log feedback in our EAC feedback forum we would greatly appreciate it!  Please note that the methods are in Beta availability so please only run on test surveys and avoid using production surveys.    Thank you,  Zach ... View more

Hello @PaulTHEDUDELang,  To resolve the issue:  - Set the default value for the status question to lowercase open to match the name of the choice in the choice list. This will fix the issue for new survey records submitted.  - To fix the issue for existing records you will need to field calculate the status field. My suggestion would be to use Arcade, the following expression should do the trick:  if ($feature["status"] == "Open"){     return "open"; } else {    return $feature["status"]; }   ... View more

Hello @PaulTHEDUDELang,  With version 3.19 of Survey123 which was released on November 14th we updated the Survey123 website to use the 4.X ArcGIS API for JavaScript (the same as Map Viewer). This update to the 4.X JS API is what caused the change in behavior.  The same behavior will be observed if you open the attribute table for the feature service in Map Viewer:   ... View more

Hello @PaulTHEDUDELang,  Default values for select_one questions need to use the name of the choice and not the label:    The standard behavior of Survey123 is to set choices configured in a select_one choice list as coded value domains when the feature service is created. This is unless the Create coded value domains from choices publish option was disabled on initial publish, the feature service is going to have a coded value domain list configured with the field that use the name of your choice as the Code (stored value) and the label of the choice as the Label (displayed value).    When Open is set as the default value since this doesn't match any of the choice names in your choice list Survey123 is going to send the string "Open" to the feature service. Since the string "Open" does not match any of the Codes in the domain it will be stored as the string "Open".     This is why you see two Opens in the screen capture you originally provided:  One Open is the string being sent by Survey123, and the other Open is the domain label which are two different things.  This difference is the reason you cannot change the value in the table.  ... View more

Hello @PaulTHEDUDELang,  The issue is Open set in the default column and open set as the choice name are not the same. So essentially forms submitted with Open as the default are not using the open from your choice list and therefore not using the value in the domain.  So your data table has the domain open (code) / Open (label) mixed with strings that are set to Open. The string Open is not connected to the domain open.  ... View more

Hello @PaulTHEDUDELang,  Do you have a default value set for the Status question in your XLSForm, and if so does that default value exactly match the name of the corresponding choice in the choice list?   ... View more

Hello @VickiG,  Usually issues with exporting data is on the feature service end, the Survey123 website uses the same export operation as exporting from the Item Details page of the feature service.  If you do see the behavior again in the future it's good to double check exporting from the Item Details page and assuming the same behavior is observed, contacting Esri Technical Support. ... View more

Hello @KeithSalmon,  With Survey123 version 3.19 the ability to set rules on all question types has been implemented which changed the location where you configure the rules on the question.  Setting rules is now in the questions settings    Please see this documentation for more information.  ... View more

Hello @abureaux,  Using 3.19.114 on iOS 17.1.1 I'm seeing the SwiftKey keyboard working in the app. The only place I see it not work is when authenticating with my ArcGIS organization. Is that what you are seeing as well?    ... View more

Hello @RichardPasquale,  The style nor target attributes are supported for the <a> html tag.  The error message is indicating the html attribute used is not supported.  ... View more