POST
|
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
08-14-2023
08:25 PM
|
2
|
0
|
331
|
POST
|
Thank you for your quick response Shwu-jingJeng. Unfortunately - and as I mentioned in the post - the users location continues to be tracked when the app is closed completely - in both the foreground and background. This is why we are wondering if it is a bug between survey version and iOS version. The app should stop tracking his location when it is closed completely but it is not honoring the selected option for only tracking the location when the app is in use. Is there something else we should try?
... View more
01-26-2021
06:19 AM
|
0
|
1
|
887
|
POST
|
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
01-25-2021
09:25 AM
|
0
|
3
|
920
|
POST
|
If anyone else has this happen we found the solution and it was a bit of a face-palm moment. In the titles of our surveys I had been using a period for the version (i.e. v1.0) and that is a no-no. Silly mistake but hopefully someone else can learn from sharing it! Thank you to the Survey123 team for their quick help on this.
... View more
04-10-2020
12:03 PM
|
0
|
0
|
1412
|
POST
|
Hi Ismael - thank you for the response. I'll email and schedule a screen share. Hope all is well and thank you, Emily
... View more
04-10-2020
07:56 AM
|
0
|
1
|
1412
|
BLOG
|
This is some excellent and helpful information on repeats - thank you! We've got a survey123 right now to inventory items being added to a pallet - it has a repeat inside of it which holds item information and outside of the repeat is information on the pallet. To facilitate the FME process on the layers, I've added hidden fields to the repeat schema calculated from fields in the parent record like the pallet barcode and final pallet destination. This is similar to what you've shown with the household ID when you brought it into the repeat as a hidden reference. We're having a problem though - not all of the fields I'm adding in come before the repeat. The fields in the parent record which are answered after the repeat is completed only appear on the last item entered as a repeat. If we enter five items, the fifth one is the only one which will have the references to the parent attributes entered after the repeats were entered. Ideally, I could reorder the survey so those questions are before the repeat but in how a pallet is assembled, the questions would still be blank when the items are added and I think that is a part of the problem - if all attributes in the parent record are not complete before people start adding to the repeat, those hidden references won't be populated. How can I get around this? We've built our process around having the parent fields referenced in the repeat and I can't figure out how to get them to all populate. This work is being done in support of the COVID pandemic going on right now and time is absolutely of the essence in figuring this out. Please let me know what we could try instead - we're open to suggestions. Thank you, Emily
... View more
04-09-2020
06:43 PM
|
1
|
0
|
56831
|
POST
|
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
04-09-2020
02:24 PM
|
0
|
8
|
1459
|
POST
|
Hi James, The issues have not resolved on their own - I'm still getting that error message when I try to republish the layers. The item details also show the layers are present. Please let me know what to do from here - thank you! Emily
... View more
04-07-2020
05:29 AM
|
0
|
2
|
741
|
POST
|
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
04-06-2020
07:32 AM
|
0
|
4
|
789
|
POST
|
Hi Phillip, I was on a version 3.6.??? and am now on version 3.7.62. I have attempted to delete the following permanently (the file paths were too long for the recycling bin): original survey folder created in the My Survey Designs location (which contains hundreds / maybe more subfolders all repeating the same naming convention) the My Survey Designs folder the ArcGIS folder All of the attempts above failed - file explorer would attempt to permanently delete the files, it would read anywhere between 2000 and 1300 items in the folder, and it would then crash. I would try to delete it again, it would display either a higher or lower item count (that part was never consistent), and then it would fail again. I contacted our IT department and they remoted into my computer to take a look and attempt to get rid of the files. We were not successful. We were able to rename the main ArcGIS folder to ArcGISOld and create a new ArcGIS folder. When I opened Survey123 Connect and made a test survey, it redid the folders within the new ArcGIS folder without a problem and I no longer have duplicate surveys appearing within Connect. A slight win. That being said, I still have the ArcGISOld folder which contains the hundreds / thousands of extra folders. The only way our IT department can get rid of those is if they create a new profile for me on the computer, we transfer everything but the old ArcGIS folder, and then they blow away my old computer profile. I told them I would check with Esri first before we start messing with my profile and potentially loose / corrupt data. I've attached a screenshot below showing how the duplicate folders were created. I think somewhere down the path there are folders containing more than just the next empty folder because in Connect, there were hundreds of surveys instead of the 10 or so I had before attempting to make a copy. That being said, I have clicked into the next folder for quite a while and never found the end of the path or more than a folder as contents. We'd really appreciate any help or guidance we can get on this - please let me know if there is anything else we can do. Thank you! Emily
... View more
03-12-2020
06:44 AM
|
0
|
1
|
1770
|
POST
|
Hi Phillip, We have run into the same issue - I tried making a copy of an existing survey and in that process Survey123 Connect froze. A few minutes passed and I forced the program to close. At this point I noticed we had hundreds of surveys as opposed to the 10 ish we had before - it duplicated every single survey which was on the computer. I have spent over an hour attempting to delete all of the folders unsuccessfully (while it only duplicated the surveys a few hundred times, it created thousands of extra folders all within the main folder for the "new" survey). I've continuously been trying to permanently delete the main folder but file explorer crashes and I'm not sure if it is actually deleting any of the folders. Our organization has file path limits and I believe that is an issue because thousands of folders were created. I have restarted my computer, installed the newest version of Survey123 Connect, created new surveys without the duplication, and had zero success on deleting the folders. Any advice? Thank you, Emily
... View more
03-10-2020
11:49 AM
|
0
|
3
|
1770
|
POST
|
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
08-26-2019
09:32 AM
|
0
|
1
|
297
|
POST
|
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
07-26-2019
10:48 AM
|
0
|
2
|
815
|
BLOG
|
Hi - question on a change I've noticed since this release in a survey that was already published. I'm wondering if it relates back to this: ENH-000109073 - Include a comma (thousands separator) in decimal questions. I have an integer field which is populated from a pull data function based on the username. It is a four digit integer which does not need commas within it and prior to last week, it did not have commas. When you are in the field app, instead of listing the entire four digit Unit Number, the field now lists the first three digits of the number in the form #,## and because I have a field length limit of four on the question, the fourth digit is not listed and users must delete the comma before being able to input their full Unit Number which should have been pre-populated. Screenshots are below showing the value as it is viewed correctly in the CSV, the XLS, Survey123 Connect, and how it is incorrectly viewed in the field app. This field was functioning correctly and is now changed. Any idea on how to fix it or what caused it? From searching solutions I've seen the option of changing it to a text field and only allowing number entry (https://community.esri.com/thread/203336-remove-commas-from-integer-field-type ) but this seems a bit silly to have to do for a strictly numeric field. XLS: CSV: Survey123 Connect: Field App: I'd appreciate any and all feedback. Also, if this isn't related to the update please let me know and I can create a question for this instead of commenting it here.
... View more
02-04-2019
11:32 AM
|
0
|
0
|
1771
|
Title | Kudos | Posted |
---|---|---|
2 | 08-14-2023 08:25 PM | |
1 | 04-09-2020 06:43 PM |
Online Status |
Offline
|
Date Last Visited |
3 weeks ago
|