Latest Contributions by JamesTedrick

‎08-07-2020

Hi, I don't see an existing Idea or Enhancement request for this. That being said, currently a CAPTCHA would be of limited use in that it would be able to protect the web page from loading automatically but would not protect the feature service submission endpoint, which can be reached outside of the Survey123 application. This is still a topic of research for the Survey123 team; if a solution to that issue can be found, it would make a CAPTHA implementation a viable enhancement.

‎08-07-2020

There are 2 components to this - Getting the hour numerically correct. This can be done by checking if the hour is between 1 - 12; if so it is correct. numbers larger than 12 need to have 12 subtracted; 0 needs to be 12. This can be done with the following if() statements: if(int(format-date(${q},'%h')) > 12, int(format-date(${q},'%h')) - 12, if(int(format-date(${q},'%h')) > 0, format-date(${q},'%h'), 12)) - Determining AM/PM - this can be done by seeing if the hour is less than 12 or greater than 11: if(int(format-date(${q},'%h')) > 11, "PM", "AM") Combined into a H:MM AM/PM string you have: concat(if(int(format-date(${q},'%h')) > 12, int(format-date(${q},'%h')) - 12, if(int(format-date(${q},'%h')) > 0, format-date(${q},'%h'), 12)), format-date(${q}, ":%M "), if(int(format-date(${q},'%h')) > 11, "PM", "AM") )

‎08-07-2020

Hi Alicia, This is somewhat difficult because select_multiple values store the choices in the order they were input. For example you could have a situation of: Q1: A,B,C Q2: B,C,A This would be regarded as different with your criteria, even though the same choices have been selected. What you instead need to do is check, choice by choice, whether a choice is selected in both questions. This can be done by using the selected() function. selected() returns True if a choice is selected; combining the selected() function for the 2 questions together: selected(${q1},'choice1') and selected(${q2},'choice1') We will get a True value only if both q1 & q2 have 'choice1' selected. We get flip that to False (which we need for a constraint to work properly) by using the not() function: not(selected(${q1},'choice1') and selected(${q2},'choice1')) When used as a constraint calculation, this will now throw an error if choice1 has been selected in both questions. To check all choices, we need to join copies of this for each choice together with 'and' statements, so that one of them being False means the entire statement is False: not(selected(${q1},'choice1') and selected(${q2},'choice1')) and not(selected(${q1},'choice2') and selected(${q2},'choice2')) and not(selected(${q1},'choice3') and selected(${q2},'choice3')) ... See the attached sample

‎08-07-2020

Hi Allison, I don't have a specific workaround, but it may be possible to create a workaround using the new javascript capability - take a look at Extending Survey123 smart forms with custom JS functions

‎08-07-2020

Hi Erica, Yes, the full payload for web hooks submitting on edit is supported.

‎08-07-2020

Hi Doug, Thanks for re-raising this. We are keeping track of this and considering it within the overall priorities of enhancements for Survey123

‎08-07-2020

Hi Jay, Yes branch versioning does support the 'supportsapplyEditsWithGlobalIds' property.

‎08-07-2020

Hi Hussam, This appears to be very unusual - the overview of the viewer appears to have more records available than the owner (according to the Overview tab). It also is odd that only one of the related tables it present when the Viewer looks at the data tab. This would probably require some interactive troubleshooting to determine what is occurring - can you open a support ticket with Esri or your distributor?

‎08-07-2020

Hi Rene, This sounds like something that could be done with eh new Custom JavaScript capability - Extending Survey123 smart forms with custom JS functions . Several of the samples for that involve retrieving data from a feature service and then manipulating it.

‎08-07-2020

Hi Dena, If version locking is turned on (which is the default), then a survey published with 3.9 or earlier will continue to support objectID. Turning the version locking off, or republishing with 3.10, will cause objectId to no longer work.

‎08-07-2020

Hi Hussam, A note on 2&3 - the attachmentKeywords (the property Survey123 uses to associate a question with a record) will only work for newly submitted data; additionally, support out of the box will be for hosted feature layers only. You can enable support for attachmentKeywords for services that use enterprise geodatabases, but we are working on providing documentation on that procedure currently.

‎08-07-2020

Hi Brandon, One additional thing to note - the name of the directory used to store the javascript changed from 'extensions' to 'scripts' during the beta process. Refer to the 3rd paragraph in JavaScript functions in survey forms—ArcGIS Survey123 | Documentation

‎08-07-2020

Hi Andrew, Support for co-authorship for Survey123 Connect Surveys is being looked into.

‎08-07-2020

Hi Erika, The list of BUGs above are the ones that affect the Survey123 field app & Survey123 Connect. BUG-000126498, which is a bug with the Survey123 web app, has been addressed with 3.10; you'll find it in the list at https://community.esri.com/groups/survey123/blog/2020/07/03/what-is-new-in-survey123-july-3-2020

‎08-05-2020

HI Michael, Apologies for the delay in response. Form your description, it sounds like you have multiple sections that each essentially represent a different view of a multiple choice question with a large number of values, is that correct? One way to work around this would be to have a separate form that you use to view the results where the end question that holds the choices is a multiple choice question instead of a calculation/text.

Online Status	Offline
Date Last Visited	‎11-05-2025 09:31 AM

My Ideas

Latest Contributions by JamesTedrick

Re: Adding a Captcha survey 123

Re: Dates and Time in Survey123

Re: Refresh of Calculated Field + Use of regex in Calculation

Re: Accessing values from a repeated select_one question outside of the repeat

Re: What's new in Survey123 (August 2020)

Re: Colors, grids, and repeats

Re: Survey publishing error: supportsApplyEditsWithGlobalIds

Re: Issue with Viewer in Survey123 Website

Re: HTML Links for Survey123 to just about anything (work in progress)

Re: Upcoming changes to Survey123 web form's query parameters

Re: Fixing the repeat records limitations in ArcGIS Enterprise

Re: Javascript function working in Survey123 field app but not browser

Re: What's new in Survey123 (August 2020)

Re: What's new in Survey123 (August 2020)

Re: Issues creating a checklist in a feature report template, question type is the issue, is there a workaround?

Re: Survey123 Tricks of the Trade: Photos

Re: Web app error initializing form Error not an o...

Re: Survey 123 form Error: Initializing form... Er...

Re: Survey123 Calculation referencing a null decim...

Re: Understanding Dynamic Labels in Survey123 for ...

Wildfire Response GIS