Latest Contributions by KYTCGIS

We have built a survey123 that is accessed and edited by users from within a dashboard.  The survey allows the user to record two locations: a geoshape that is stored as the records location and a point that is used to populate latitude and longitude reference fields used in geoenrichment.  It is important to note the point is not passed through with the record as the bind::esri:fieldType is null.  There are no conditions, repeats, calculations, relevants, etc... on either of these geometry fields as they are both required.   Users can create records without issue - the latitude and longitude reference points are populated as expected from a pulldata on the point geometry. The issue comes in, however, when users then go to edit the record from within the dashboard.  When a record is selected to be edited, almost all of the record's editable attributes populate - the geoshape question is populated as expected but the geopoint question appears blank, not carrying over the originally submitted point.    I've done a bit of troubleshooting, reviewing blogs and trying the suggestions but without success.  Any ideas on why the point is not coming back for editing?  Is it because of the null setting in the bind::esri:fieldType?  Some troubleshooting step tried so far: I tried defaulting the point location to be the stored latitude and longitude (hoping I could force it back to the originally submitted point when a user goes in to edit) but that did not work - the point was still gone I made a separate survey specifically for editing and pointed it at the original survey.  In the "editing" version, I removed the pulldata functions from the hidden latitude and longitude field, trying to avoind them getting reset when a record is edited.  While it looks like this would work, not having the pulldata functions means that if the customers do update that reference point to a different roadway, we won't be able to capture that information and geoenrich on the new location.  The record would be forever stuck having principal route information stored in the attributes which might not be accurate.  We typically try to avoid using repeats because they tend to get finicky - but this is the only other thing I can think of as potentially working. Is losing the second geometry while editing via a webform expected and I missed that somewhere? Or is it because of the null bind::esri:fieldType? ... View more

Is there a known bug where the Survey123 mobile application uses location services all the time - even though the location services is set to only run when the app is in use?  This is draining the battery for our users and causing the need to continuously turn the location services on and off every day for the short duration they need to use the app for completing inspections.  Our user has the option selected in location services to only track location when the app is in use.  When he closes Survey123, however, the blue bar saying the location is being used continues to appear at the top of his phone.  This is when the app is completely closed and will persist until he turns permissions off for location services.  His battery is drained quickly unless he turns the permissions off.  He is using an iPhone 7, 14.3 version with Survey123 version 3.11.164. We first experienced this problem several months ago and we could not find a resolution for it.  We uninstalled and reinstalled the app, played with location service settings and other settings, and never found a fix.  After several weeks / months, the problem went away on its own.  It has recently started happening again and we need a solution.   I've seen several threads on this issue although a resolution is never given and for some users, the issue will disappear on its own / reappear at a later date.  Is the occurrence of this phenomena associated with iOS or Esri updates?  Why is the setting selected in location services not honored on his device? Related posts: https://community.esri.com/t5/arcgis-survey123-questions/survey123-uses-location-services-in-background-drains-battery/td-p/805514/page/2  https://community.esri.com/t5/arcgis-survey123-questions/battery-drain-when-using-field-app/m-p/836457#M19743  https://community.esri.com/t5/arcgis-survey123-questions/survey123-field-app-drains-battery/td-p/849682  ... View more

Hi All. For the last few weeks I've been having some issues with Survey123 Connect.  Sometimes when I try to create a new survey (either from an XLS Template or an existing survey) I will have two new surveys appear within Survey123 Connect instead of one new survey to click on.  In those case, typically only one of the two new surveys will actually connect and allow me to access the XLS form.  Deleting one survey will delete both however and only one folder is created in my "My Survey Designs" folder.  I'll also say that when I look at the folder in "My Survey Designs" it never has the complete folder structure - it may only have an XLS in it with no media folder or any other files.  When I create one survey and it creates two - I always have to delete the survey and keep trying until it successfully completes a full survey.  This gets to be aggravating. On the flip side, sometimes when I create a single survey, it successfully creates a single survey in Connect but then when I open it to start playing with the fields or configuring the settings, it's like the survey cannot see the underlying XLS form and the button to get to the XLS isn't even there.  This happens - like the duplication - when I create a new survey from an existing survey, from an XLS template, or even an existing XLS only.  Image below.  I'm currently in version 3.9.120 of Survey123 Connect although I had these issues in a version 3.6.xxx and 3.7.xxx.  My solution has been to continually uninstall and reinstall survey123 Connect but it appears the problems follow me.  This is starting to interfere with my ability to efficiently create a survey and use the program.  I will say the problems consistently happen so doing a screen share would work if someone needed to see it happen.  Please let me know what to do next and thank you,  Emily  ... View more

Hello - we're publishing multiple surveys for the COVID-19 response within KY and I'm coming across a similar error when trying to make updates to the surveys once they've been published.  I'll make a change to a published survey which I know is allowed (like adding a text field or making a question NOT required) but when I do - Survey123 Connect  warns me the changes will wipe the survey.  The error message is pasted below.  These surveys are published from the XLS form and are not writing to an existing service nor are we using enterprise.  When making small, needed changes we cannot wipe the existing data so we've been having to forgo needed changes which normally should be able to be published.  In the last week I've had this happen on two surveys - one did have repeats within it so I assumed there was an issue with that but this survey in particular does not have any repeats and I was not changing anything which would wipe the existing survey - I wanted to make a required field not required.   I authored the survey in Survey123 Connect and we are on version 3.9.120.  I will say I've only received this error on  surveys I've published with this version of Connect - I don't know if it is a bug.  We do have a version on the survey which I haven't used too much before but other than that it is the standard geopoint, barcode, image, text, and date fields.  No repeats, some of the fields are use an esri type of null so they don't write back to the layer, and there are quite a few calculations and relevants.  Folks can submit to the survey without a problem or error but I cannot update it at all.  Any advice would be greatly appreciated.  Thank you! Emily  ... View more

This morning I noticed a few minor changes to the user interface within the Survey123 app (button appearances, etc...) and I had to sign back into some applications (Collector). This is fine, but settings I had on our geopoint question (a bounding box limitation giving the user an error message if they select a location outside of our state) now seem to be broken.  Regardless of the location (in or out of state), the bounding box error message displays.   Was there an update last night?  Is anyone else experiencing this?  I'd appreciate any and all feedback - this is being noticed on one of our higher usage apps and if it will be an ongoing issue or bug, I need to notify users and take next steps.  Thank you,  Emily ... View more

Creating choice lists within Survey123 Connect leads to duplicate domains within a file geodatabase export.  If you have a choice list (the equivalent of a domain for databases) and apply that choice list to multiple questions, you will have a domain in your FGDB export for each question a choice list was applied to (there are photos below to demonstrate this).  I've noticed this within Survey123 for several years - while employed by different organizations and through different Survey123 versions - and thought it was the way things were supposed to be.  I asked the Survey123 gurus at the 2019 Esri UC a few weeks ago if this would ever be updated, however, and was told this is actually a bug that needs to be reported.  I thought I'd ask here before going down that route. Does anyone know if there is a reason for this or has anyone noticed it before? I'm including a bit more dialog below to show what I'm referencing.  On the database side of things, having more domains than you need is a bit messy - especially if you have a survey with 50 + questions using the same choice list (i.e. yes_no).  In your file geodatabase export, instead of having one yes_no domain, you have 50 + yes_no domains because every question gets their own domain (i.e. cvd_question_one, cvd_question_two...).  Some steps with photos are included below to demonstrate this. 1. Make a choice list 2. Apply that choice list to as many questions as you need to 3. Publish the survey, complete surveys, and download the file geodatabase export 4. View the file geodatabase properties and notice the duplicated domains This isn't limited to a single survey we've created or a specific version of Survey123.  I actually created this short one right before making this post to see if it was still happening.  Does anyone have any idea of why this is happening?  Is it an actual bug?  It's been like this for years and I have a hard time thinking I'm the only one to notice it so I'm thinking there is a reason out there I'm just not aware of.  I'd appreciate any feedback, thanks! ... View more