Latest Contributions by ChrisShuck

‎06-29-2023

We are also experiencing this type of user error. I could only come up with a workaround, which is to have the user enter Lat and Long into separate text boxes, then have those fields populate a read-only geopoint with a concat() formula. However, this workaround takes away the convenience of using the map from those users that do know how to use the map properly. We'd rather turn off location services within this particular survey (not for the whole app though).

‎04-15-2021

I've been using the new version of the app (3.13.110Beta) all day and have not had the issue with the app freezing upon saving. It has crashed twice inexplicably upon saving, but otherwise it has worked fine.

‎04-15-2021

Thanks for the update. I just downloaded it and will be testing it today.

‎04-14-2021

Same problem here. This happens intermittently. Most of the time I can save without an issue. Then I'll have a streak of 3 to 10 times that it freezes and I have to force quit and re-enter. Occasionally I have to republish a whole new version of the form to get it to work. This never used to happen prior to the last update. This happens on very simple forms and complex forms. I can't find any rhyme or reason for it. Very frustrating. Version 3.12.232.

‎10-09-2020

I filed a case with Esri customer care, and they were able to figure it out. In my case, the issue was that a couple of begin repeat and begin group fields did not have labels. Once the labels were added and the surveys republished, I again had the ability to create Flows and use dynamic content. I had gotten into the habit of not adding labels to some repeats and groups with repeats. It flattens the repeat and saves space to not have them; it keeps each record on one screen without having to scroll down. That makes it easier to navigate between repeat records. While it is unfortunate that I can no longer do that, it's a small price to pay to have the ability to create Flows again. A big thank you to Katelyn at Esri Customer Care!

‎09-23-2020

Hi James, I have several recently created surveys which do not have dynamic content available in Power Automate. Those same forms have the same issue in Integromat. I have been able to create test forms that don't have this issue. It seems about half of the new forms I create have this problem. I've been using Survey123 and Flow for years but have never run into this issue until recently. I've scoured the Power Automate forums but haven't been able to find anything helpful. Could this be related to recent Survey123 updates?

‎09-04-2020

My default keyboard was Gboard. It works fine on all other apps, but on Survey123, I cannot utilize talk to to text or swipe texting. I downloaded and set MS SwiftKey as my default keyboard. I can now use talk to text, but I still can't use swipe texting, my preferred data entry method. That seems to be disabled for this app, but it works fine on others. I'm happy to have talk to text capability now though. Thanks for the tip. -Chris

‎01-02-2020

I posted another solution idea here.

‎01-02-2020

I posted an alternative solution idea here.

‎01-02-2020

Repeat groups are an incredibly useful tool. However, navigating through repeat records in the field app to reference or edit a record when there a lot of them can sometimes be tedious and unbearable, especially given that the navigation arrows are at the bottom of a repeat rather than the top. This causes the survey to jump around when navigating between records of various lengths, and it is often not clear what record you are on without scrolling up. I have seen other Ideas listed that also concern this issue and have potential workarounds listed, but I believe the following would save space and would make it easier to find what a user is looking for. If repeats were set up in the same format as Survey123 pages, they we be much easier to navigate. When a user clicks on the page numbers at the bottom of the survey it brings up a menu with all of the various pages that can be navigated to in one click, and it also gives the option of typing in a page number. Repeats could be set up to have one field, probably the first, which will be the shortcut name of that record (analogous to the page name) that would be clicked on to navigate to that repeat record. The shortcut name would be something like an artifact ID number, a species name associated with a record, a nest number, or a unique ID. While this would be ideal, if it is not possible, at a minimum it is desirable to at least enter a repeat record number that would be navigated to, so the user does not have to scroll through all records to get close to the correct record. Other fixes mentioned in other posts include: Stacking repeat records vertically Positioning the navbar at the top and bottom of the repeat A number navigation popup to enter the number of the repeat Moving the navbar to the top of the repeat

‎01-02-2020

I posted an alternative solution here. If you click on the page numbers at the bottom of the survey it brings up a menu with all of the various pages that you navigate to in one click. Repeats could be set up so as to have one field which will be the name of that record, which would be the shortcut name that would be clicked on to navigate to that repeat record. This would save space and would make it easier to find what you are looking for than having to scroll through a huge amount of data vertically as suggested, although that would be a nice option to have too. Navigating through a lot of repeat records with the current setup is tedious and unbearable, especially given that the navigation arrows are at the bottom of a repeat rather than the top, causing the survey to jump around when navigating between records of various lengths.

‎03-04-2019

Hi Phillip, Thanks for providing the timeline. -Chris

‎03-02-2019

Thanks for your response. Do you have an estimated time frame? I'm trying to decide if I should go ahead and fix our surveys now, which will be quite time consuming, or wait on ESRI's fix. We rely heavily on those surveys and need them up and running as soon as possible. Thanks, Chris

‎03-02-2019

UPDATE: The problem has been solved. If the repeat name is MT, the field name cannot start with MT as in MT_Amount1. When all field names that started in that manner were edited, with those letters being removed, I was able to successfully generate reports. I'm sure this is related to the 3.3 update. Can anyone explain why it might be incorrect to start a field name with the same letters as the repeat name?

‎03-02-2019

This error has appeared on 5 or 6 of my company's surveys. All of these began just after the 3.3 release on 2/26. In each survey, there is a random field that receives this error. Prior to the appearance of these errors, reports for all of these surveys had been generating without issue. No changes were made by us. The only common factor that I can see for the fields mentioned in the error messages is that they are fields within repeats. I published a copy of one of these surveys, but the problem persisted. I also tried removing the tag that was prompting the error. After that, I received the error message for the next field within that repeat. It did not give an error for the very first field in the repeat.

Online Status	Offline
Date Last Visited	‎11-15-2024 12:36 AM

My Ideas

Latest Contributions by ChrisShuck

Re: Turn off location capture in Survey123

Re: Survey123 Connect freezes and takes a very long time when updating from CSV

Re: Survey123 Connect freezes and takes a very long time when updating from CSV

Re: Survey123 Connect freezes and takes a very long time when updating from CSV

Re: MS Power Automate not showing dynamic content fields for survey123

Re: MS Power Automate not showing dynamic content fields for survey123

Re: Survey123 and Speech Recognition integration

Re: Skip to desired repeat record

Re: Be able to position the repeat navbar at the top of the repeat section

Fix painful repeat navigation issues - have navigation mirror that of the pages group appearance

Re: Appearance option to view Repeats stacked in Survey123 app

Re: Survey 123 Report Template Error: Failed to parse/does not exist or cannot be found in current parsing scope.

Re: Survey 123 Report Template Error: Failed to parse/does not exist or cannot be found in current parsing scope.

Re: Survey 123 Report Template Error: Failed to parse/does not exist or cannot be found in current parsing scope.

Re: Survey 123 Report Template Error: Failed to parse/does not exist or cannot be found in current parsing scope.

Re: Survey123 and Speech Recognition integration

Re: MS Power Automate not showing dynamic content ...

Re: Survey123 Connect freezes and takes a very lon...

Fix painful repeat navigation issues - have naviga...