|
POST
|
Hello @ANRGIS, You can use the not operator (!) to catch null submissions. The syntax would look like: ${embankmentdraintypes}${if ! embankmentdraintypes}None${/} Thank you, Zach
... View more
09-21-2021
03:24 PM
|
0
|
1
|
1688
|
|
BLOG
|
Hello @DataOfficer, That statement is no longer relevant, since the 3.9 release of ArcGIS Survey123 an update notification system was implemented. After the media folder is updated Survey123 will recognize that the form item has been updated and display a notification that an update is available. In Survey123 Connect under the options you can enable "Require update to the latest version of this survey" so that when someone selects the survey they will need to update it before starting a survey. ZacharySutherby_0-1632260718910.png Thank you, Zach
... View more
09-21-2021
02:45 PM
|
2
|
0
|
8965
|
|
BLOG
|
Hello @StuartMoore, @MillerDerek is correct the clone_items() method will clone the full item instead of a specific record in a survey. Please see the clone_items() Python API documentation for more information. Thank you, Zach
... View more
09-21-2021
02:31 PM
|
1
|
0
|
8276
|
|
IDEA
|
Hello @JonathanPendleton @JoshHabel @GaryElsner @erica_poisson, This workflow can be accomplished using custom JavaScript functions in your survey. The JavaScript function queries the feature service the survey is pointing to and returns the most recent submission and populates the questions in the sample. I have attached a sample XLSForm and JavaScript function that demonstrates the workflow. All that is needed is to publish the XLSForm and then update the REST URL in the JavaScript function with the REST URL for the feature service that was created when the survey was published. Please note this workflow will not work for select_one or select_multiple questions. We do have the search() appearance which can be used with select_one or select_multiple questions, but there is a known issue at the moment where defaults will not work with the search() appearance. Thank you, Zach
... View more
09-09-2021
01:45 PM
|
0
|
0
|
3550
|
|
POST
|
Hello @jaykapalczynski, Let's schedule a call to discuss the workflow and get it set up and running. Please feel free to email me at [email protected] and we can schedule a call to clear it up. Thank you, Zach
... View more
09-08-2021
05:55 PM
|
1
|
0
|
1883
|
|
BLOG
|
Hello @StuartMoore, Yes this workflow can be used to clone a single survey within the same organization, you would just need the code from the Clone full survey folder section of the sample notebook. Although if your survey was created in the Survey123 website you can use the "Save as" option in the website to create a copy of your survey. Thank you, Zach
... View more
09-07-2021
03:36 PM
|
1
|
0
|
8605
|
|
BLOG
|
Hello @DataOfficer, The script in this blog is quite old and is intended for ArcMap the modules used by the script have been superseded by the ArcGIS API for Python. We have updated this script to use the ArcGIS API for python and the updated script is present in our Survey123-tools github repo. Thank you, Zach
... View more
09-03-2021
03:59 PM
|
2
|
0
|
9305
|
|
POST
|
Hello @Anonymous User, In testing on my end one field that seems to be causing the error is the Project Name field. For the bind::esri:fieldLength it is set to 30 but the value that was submitted in my test survey is "MedBow Springs/ WYNDD Survey 2021" which is 33 characters. Thank you, Zach
... View more
09-01-2021
10:24 PM
|
1
|
1
|
2881
|
|
POST
|
Hello @RSchaffner, If possible would you be able to share the survey to a group with ZSutherby_Survey123 added to it? I don't need access to the underlying data just access to the survey. With access to the survey I can compare the files with the published survey and the zip attached to identify any differences that may be causing the publish failure. Thank you, Zach
... View more
08-25-2021
11:42 AM
|
0
|
1
|
2217
|
|
POST
|
Hello @DataOfficer, I've tested on my end with the sample form structure from above and I am not able to reproduce the same behavior. If you publish a new test survey using the form structure above are you able to reproduce the same behavior? Thank you, Zach
... View more
08-25-2021
09:20 AM
|
0
|
1
|
2079
|
|
POST
|
Hello @kborst, If you would like users using the Survey123 field app to view other submissions you will need to enable the inbox in Survey123 Connect for the survey. Please use this link for reference regarding editing and viewing existing survey data: https://doc.arcgis.com/en/survey123/desktop/get-answers/editexistingdata.htm#ESRI_SECTION1_47C2CB8342244924B1D99EBB35EAFFFE Thank you, Zach
... View more
08-24-2021
04:07 PM
|
0
|
0
|
723
|
|
POST
|
Hello @LuisGarcia6, If possible may we ask for a diagram of your desired end goal? There is a workflow that comes to mind, but want to make sure it aligns with your use case. Thank you, Zach
... View more
08-17-2021
09:27 AM
|
0
|
0
|
978
|
|
POST
|
Hello @JuneAcosta, Using the Survey123 Web App JavaScript API there is a setOnFormSubmitter event that can be used in conjunction with a custom function that will close the window. Please use this link for more information on the Survey123 Web App JavaScript API: https://developers.arcgis.com/survey123/api-reference/web-app/#setOnFormSubmitter Thank you, Zach
... View more
08-16-2021
01:51 PM
|
0
|
0
|
1492
|
|
POST
|
Hello @PedroGabrielBuenoCesar, IOS tends to be more strict capitalization in file names and file extensions. In your XLSForm you have select_one_from_file municipios.csv whereas the name of the csv file attached is municipios.CSV. That difference in capitalization with the csv file extension is what is causing the issue in IOS. Changing the file extension to a lowercase csv to match what's in the XLSForm works in IOS. Thank you, Zach
... View more
08-16-2021
01:24 PM
|
1
|
0
|
1935
|
|
POST
|
Hello @MathieuBoonen, The syntax is a little off, given how the Onecall API returns it's JSON if you are looking for the days description the syntax would be pulldata("@json", ${weather_json},"daily[1].weather[0].description") This will return the weather description for tomorrow. If you are looking for other days you would change the index after daily. For example daily[0] would be today and daily[2] would be two days from now. It also looks like the Onecall API has an exclude parameter so if you are not interested in the minute forecast, hourly forecast, or alerts you can exclude them and make the response smaller. Thank you, Zach
... View more
08-04-2021
06:54 PM
|
1
|
1
|
4506
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | a month ago | |
| 1 | 06-04-2026 03:20 PM | |
| 1 | 05-22-2026 03:26 PM | |
| 1 | 02-27-2026 02:55 PM | |
| 6 | 12-17-2025 01:51 PM |
| Online Status |
Offline
|
| Date Last Visited |
yesterday
|