Latest Contributions by BradenBurkholder1

The revised URL is working, but is not user friendly for folks to type in to their devices to download a survey. Most of my users are initially accessing my surveys from that link, and the Tiny URL format was very helpful even though it did route the user through a browser. If this is a permanent change, I will probably just send my users the Tiny URL from the 'ask' option from here on out. Braden ... View more

Thanks Phil! ... View more

Phil, I'm seeing this issue in 3.5.177, in both Android and iOS, as well as S123 Connect 3.5.166 in Windows. This didn't seem to be an issue in earlier releases of S123 (<3.5). The issue: When a time field is clicked, the current time (e.g. 11:52 AM) is displayed in the field box and that is the desired time for this field: But the time picker shows the field initialization(?) time (e.g. 11:51 AM) - this may not be form start time if relevant statement is used. When the user clicks anywhere to close the picker (i.e. without picking a time), the field changes to the picker time: Default of now() gets the time that the field initialized. This resets when clicked, but I need users to document the end time of their work (which may not coincide with the form end time). If time is manually changed, the indicated time is retained, so that's not an issue. The issue is that my users have been clicking the field in the past to document the end time of their work and since the behavior of this field has changed, we've now had a couple errors crop up since the time field is defaulting back to the initialization time without them realizing it. We'll be more cautious moving forward, but it would be nice to have the old behavior back.  Is this on the docket to fix or is this intended behavior of time fields for the future? ... View more

FYI: I never heard anything as to whether this was a bug or not, but this hasn't been an issue for me since 3.5 was released. ... View more

Now fixed as of Survey123 field app build number 3.5.177 ... View more

Thanks Philip! Is there a tentative release date/period for 3.6? ... View more

Have you tried manually adding the field to the feature service prior to publishing? https://doc.arcgis.com/en/arcgis-online/manage-data/add-or-delete-fields.htm That's worked for me in the past. ... View more

Same issue in Field App 3.5.164 on an older Samsung Galaxy S5 (Android 6.0.1): tpk maps won't display (but are present in survey folder on device) and map icon disappears when off network. Reinstall of App and survey didn't fix it. Survey and map worked just fine on Field App 3.3, offline map still appears in Connect 3.5. Maps also do not display on an older Motorola (Android 6.0) phone. However, maps do show on an older iOS device (iPhone 7). Example survey available here: https://arcg.is/898Xe  I made a brand new tpk with Kreator 1.3.30 and issue persists on a simple survey on the original offending device. ... View more

Any update on this enhancement request? Thanks! ... View more

Elliot, I, too, am having issues with loading surveys on some older devices, both phones and tablets. "Loading Survey" may appear, then the entire field app crashes. In my case the survey has a large external_choices table (7000 rows), and the frequency of crashing decreases when fewer rows are included in this table. Crashing is sporadic, however, not every time the survey is opened (~10% of the time). Brandon Armstrong‌ has been looking into this on my behalf. I'm hoping it's a bug, as I hadn't encountered this issue on previous versions of Survey123 (<3.1), but had also not attempted this large of a dataset previously. Could be our equipment is just approaching obsolescence though. Braden ... View more