Latest Contributions by ZacharySutherby

Hello @DrJumaKhudonazarov,  The survey form is not a valid item to add to a web map. If you are looking to embed the survey in a dashboard you will need to use the full survey sharing URL as opposed to the short URL. Please see this Esri Community blog for more information on embedding a survey in a dashboard.  ... View more

Hello @Anonymous User,  It may be cut off but from your screen capture of the calculation in the web designer the where clause looks to be missing. The calculation should be something along the lines of `extract X from ABC_layer where Y is <someValue>`. The where clause tells Survey123 what exact record to extract the value from the X field. If you edit your calculation is there a filter set (step 3)?   ... View more

Hello @CrypticCartography,  You can point your survey to the existing feature service, you don't need to create a new feature service with the survey. Please see this documentation for more information on using an existing feature service in Survey123.  To edit existing records in the Survey123 field app you will need to enable the Inbox within Connect. The Inbox is where field users can access and update existing records. Please see the Prepare to edit existing survey data documentation for more information.  ... View more

Hello @StevenHughes44,  It's not possible to apply a uniform text size to an entire form, but if your users are using the Survey123 field app they can increase the text size from the Settings and when they load the form the text size will be larger.  ZacharySutherby_0-1679698124544.png   ... View more

Hello @SteveGingerich,  Survey123 returns the error returned by the server and there wouldn't be a way to modify the error from the Survey123 side.  Our recommended workflow would be to use the same logic you used for your validation rules in the constraint column of the XLSForm so that the validation occurs on the Survey123 side prior to submission. Using a constraint allows you to customize the constraint message which will be displayed in Survey123. ... View more

Hello @KateDoughty1,  After you publish your survey you can use the width URL parameter to make the width of the survey a little wider and remove the scroll bar.  ... View more

Hello @Hopkins_Gina,  If you look at the domain in the feature service for the State/Province field does Arizona and Arkansas have the same domain name?  ... View more

Hello @ChristinaCroll,  As long as randomize=true isn't in the parameters column of the XLSForm the choices should display in the order they're in the choices worksheet.  ... View more

Hello @JoeGross,  The first suggestion/consideration is decide if you want your QR code to link to the Survey123 web app, the Survey123 field app, or let the user decide. This is because the URL to use is slightly different for each workflow.  From there you will need to use the field:fieldname=value URL parameter(s) to prepopulate the field in the survey.  Good places to start are the Survey123 Tricks of the Trade: Web form URL parameters and Understanding Survey123's custom URL Scheme Esri Community blogs. Depending on if you are planning to use the web app or field app the Integrate with other apps documentation has really nice tables that show what URL parameters are supported for both workflows.  Since you are want to use a QR code if you want to open the Survey123 field app the custom URL scheme isn't going to work, but Survey123 links will (https://survey123.arcgis.app) although both use the exact same parameters so the information in the custom URL scheme blog also applies if you are using the Survey123 link As for the same QR code being scanned by two different people, saving a survey to a draft is only local to person 1's device. Person 2 on their own device would not be able to access a draft survey that's on person 1's device. The workflow I would suggest to answer the second question assumes you already have the assets in your GIS infrastructure (meaning you already have a feature service with the asset locations and asset ID in the attribute table) and you only need to edit the data as opposed to collect new records.  In this scenario I would suggest using URL parameters to edit the existing record so that when person 1 scans the QR code they are brought to the record and can fill out the delivery information. They will need to submit the survey, then person 2 can scan the QR code again, the same record will be opened and they will be able to complete the receiving information.  Depending on how you want this set up it may require some logic in the form to only show or hide sections of the survey depending on what's already been filled out.  ... View more

Hello @WilmerWoudwijk1,  This is a defect with the Survey123 website (BUG-000154545) please feel free to reach out to Esri Technical Support to attach yourself to the defect.  Unfortunately there isn't a workaround to the issue, but the issue is a UI glitch meaning the survey will function as expected and any updates or republishes of the survey will complete successfully the issue is the notification is incorrectly displaying.   ... View more

Hello @Sven_Harpering,  I had brought this up with the team and the decision has been made to remove CAPTCHA (beta) from the 3.17 local website installation and is not anticipated in the final release.  There are a few technical reasons it has been removed from the local website install, but one of the major reasons is a disconnect in how we are seeing CAPTCHA used vs how the Survey123 local website is used.  We have seen CAPTCHA used in public surveys to prevent spam submissions, but we have seen the Survey123 local website used internally within organizations. With the local website used within organizations and not with public surveys CAPTCHA doesn't quite make sense.  We wanted to reach out and ask what the use case of CAPTCHA in an internal survey is?  Please feel free to follow up offline if that's preferable, feel free to email me at [email protected] or the Survey123 team alias at [email protected] and we'll be happy to discuss.  ... View more

Hello @DataOfficer,  It looks like you may be using an older version of the notebook, if you navigate to line 129 in your redacted.py file there will be a line of code that says  itm.update(surveyProp,updateZip) Try switching the surveyProp variable in that update method to an empty dictionary `{}` does that resolve the issue?  From the error it looks like the size of the request generated from the update() method is very large. Typically this could be due to a very large dictionary containing the properties of the survey. While the properties are required for the update() method it can be an empty dictionary.  If the behavior still persists after switching the properties in the update() method to an empty string the issue is then likely your survey form item is very large. If it contains redundant or unused files in the media folder it may be worth considering removing them.  ... View more