Latest Contributions by ZacharySutherby

‎06-13-2023

Hello @MicahTrierweiler, Survey123 3.11 does not support pulldata("@layer"), this functionality was originally released with Survey123 3.16 and is available in our current 3.18 release.

‎06-13-2023

Hello @Andrew-Bowne, There is a service disruption impacting the Survey123 report API at this time. We are monitoring the situation and will update when it has been resolved.

‎06-13-2023

Hello @MT_JenAmes, The name and label columns in your CSV should be lowercase. Please see the External choice lists documentation for more information. The Survey123 webapp and typically the Survey123 Field App on iOS are more strict about capitalization.

‎06-13-2023

Hello @GBayMnidooGamiiBiosphere, Would you be able to provide a diagnostic log when the crash is reproduced? Would it also be possible to share the XLSForm for the survey to try and reproduce the issue on our end?

‎06-12-2023

Hello @Sharouff, You should be able to use the orderByFields parameter to sort the results descending. Please note a very strange quirk about the search() appearance is because the question mark is used to separate the table name from the URL the ampersand is needed to separate the URL from additional URL parameters. I've attached an example that sorts counties from Z to A using the orderByFields parameter.

‎06-12-2023

Hello @bsklaohfl, I would suggest making the change in the surveys XLSForm, if the issue is the main layer doesn't match you can set it in the form_id column of the settings worksheet. If the issue is a related layer or table doesn't match you will need to update the name of the begin repeat in the survey worksheet. Assuming you are using a submission_url Survey123 shouldn't let you republish the survey unless the schema matches.

‎06-09-2023

Hello @bsklaohfl, Are you using ArcGIS Online or ArcGIS Enterprise? If you look at the schema for your survey and compare it to the layers and tables for your feature service item do they match?

‎06-08-2023

Hello @beachcamp, I'm glad that worked out! In theory it shouldn't like you saw with James' comment in the post you originally linked after the XLSForm is converted you could update the value in the surveys XML. The core issue is with the library that's used to convert the XLSForm to XML incorrectly throwing an error message.

‎06-08-2023

Hello @AlmaA, Correct the way the update_geometry script is currently written it assumes original_item and fixed_item are items in your content. That doesn't necessarily have to be the case if you have the GNSS coordinates as attribute fields in your services' table you can just make a connection to that layer pull the coordinates from the attributes then update the geometry with those values. It just happened in the scenario where that script was written there was a second feature service that had the correct geometry.

‎06-08-2023

Hello @beachcamp, Thank you for passing along the XLSForm! Moving the today() function from the calculation column to the default column should do the trick.

‎06-08-2023

Hello @beachcamp, Testing in the current release of Survey123 Connect (3.17.55) I am not seeing this behavior. If you update your Connect to the latest version is the same behavior observed? As a side note if you install Survey123 Connect through the Microsoft Store you will receive updates automatically when they are released.

‎06-07-2023

Hello @Trippetoe, There's a bit of a mismatch in the parenthesis. The second parenthesis shouldn't be after the selected() function but instead after the if() statement. Try: (.>0) and (if(selected(${productId},'prod1'), .<=2,.<=500))

‎06-07-2023

Hello @AlmaA, You will need to update the features geometry with the coordinates from the external GNSS equipment. The manual way of doing this directly in Survey123 is to load the feature in the Inbox, open the feature from the Inbox, open the geopoint question, select the globe on the top left to change the Search mode and change it to Map coordinate input only, enter the coordinates that were provided from the GNSS receiver, and submit the data. You can also use Python for a more automated approach, please see this Esri Community post for more information on an automated workflow. I've attached a workflow that uses the ArcGIS API for Python instead of ArcPy like in the Esri Community post that will use geometry from a second layer to update the geometry in a first layer. Since each scenario will be unique you will likely need to modify the code to meet your environment.

‎06-07-2023

Hello @MaryGraceMcClellan, Thank you for this information! While there is no pulldata("@geoshape")/pulldata("@geotrace") formulas currently I have recorded this feedback to look into supporting in a future release. Please feel free to reach out to Esri Technical Support to log an official Enhancement for this functionality. In the meantime there is an alternative workflow that will allow you to reach your end goal. You can populate/calculate a geoshape/geotrace question using an aggregation of geopoints. When aggregating those geopoints (vertices) you can capture the GNSS metadata you're looking for in order to extract the average, min, and max from the metadata. I've attached a small sample that demonstrates how this workflow works.

‎06-06-2023

Hello @VickiG, Since you mentioned you revisit known locations I assume you are using the Survey123 Inbox to edit existing GIS features in a feature service. Within the Survey123 Inbox there is a map tab that can be used as a reference map. If having the map in the form is of more interested you can add a geo* question (geopoint, geotrace, geoshape) which will add a map to your form. In the XLSForm under the bind::esri:fieldType column you can set the value for the geo* question to null so that nothing is submitted to the feature service the map would just be available in the form for reference. In both cases the Inbox map and the geo* map neither have measuring tools or more advanced spatial capabilities it's mainly just pan, zoom, and focus on the devices location. You wouldn't be able to navigate like in ArcGIS Navigator, but you could specify a specific basemap and if that has features in it you could navigate by seeing if your position indicator is around a feature.

Online Status	Offline
Date Last Visited	2 weeks ago

My Ideas

Latest Contributions by ZacharySutherby

Re: Query a Feature Layer by ArcGIS_Survey123 Not Working

Re: Error when Generating Report

Re: Pulldata function not working in web form

Re: survey123 app crashing after deleting draft Android (13)

Re: Dynamic Search Appearance Results Descending Order

Re: Send Error: Layer not found in feature service

Re: Send Error: Layer not found in feature service

Re: Bug in format-date function

Re: Correcting Point Data from Survey123 with GNSS coordinates

Re: Bug in format-date function

Re: Bug in format-date function

Re: Can a survey have conditional constraint ranges of values?

Re: Correcting Point Data from Survey123 with GNSS coordinates

Re: Is it possible to capture GNSS metadata for geoshape and geotrace?

Re: Map in Survey as reference only?

Re: Does the python Suvey 123 api support creating...

Holistic Testing - Survey123 Mobile, Survey123 Stu...

Re: Survey opens in web browser and not in Field A...

January 2026 ArcGIS Survey123 Beta Testing

November 2025 Next Generation Survey123 Beta Testi...