Latest Contributions by ZacharySutherby

Hello @jdaniel,  It sounds like when you designed your form in the web designer you used the address question and for the "Data to submit" setting it was set to "Address text and point geometry". What you can do is switch that setting to "Address text only" then add a map question and that will allow capturing the geopoint. If the address question is set to required you can remove that and then you will be able to capture a geopoint without an address.  ... View more

Hello @ErikHerbergMETC,  Thank you for reporting this! This looks to be a defect, I've gone ahead and logged an internal issue for this behavior. Please feel free to reach out to Esri Technical Support to log an official BUG.  ... View more

Hello @dwold,  The selected() function would go in the choice filter for the Indicator question not the IndicatorOther question.  ... View more

Hello @Anonymous User,  The where clause will help refine what record is returned, without it the calculation will return the first record in the query response. As for why nothing is being returned in the feature service you are referencing in the calculation do all records in the feature service have ID values in the attribute table?  ... View more

Hello @dwold,  For the other choice in the component column you can comma separate all the components (ex. Law Enforcement / Security,Fire Service,Search & Rescue) then use the selected() function in your choice filter column. The choice filter would look like selected(${Component}, component). ... View more

Hello @MiltonSolano,  The Search() appearance is going to display values as they are returned by the server. When date fields are queried from the feature service they are returned in epoch timestamps which is why it's displayed like that in Survey123. What I would suggest is in your initial registration survey adding a hidden or calculate field to store the formatted date as a string in the feature service, then use that string field in the search() appearance.  ... View more

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.    ... 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