|
POST
|
@Anonymous User Thanks for the help. I followed the directions for embedding the form I want to review/edit into our dashboard and it works... Except, when you click on the record you want to review/edit in the List, the embedded web form does not perform the age calculation, which in turn forces you to complete the guardian info required fields. Is there any work around for this? Is there a way to change URL to include calculations? If I author another survey from the feature service and embed that webform and simply don't include the dob, age, and guardian info fields will that data remain intact and still allow me to edit the other parts of the survey? Cheer, RyanE
... View more
06-23-2021
11:46 AM
|
0
|
0
|
1303
|
|
POST
|
Hi @Anonymous User , Can you recommend an article for setting up the dashboard with edit mode? Would I be able to edit the survey data in a "detail" feature? the geopoint as well? Or would you have to specifically designate which fields are available to be edited and then create a "list" feature? With the different surveys option, since they would both be linked to the same feature service, would my dashboard need to be updated? I could conceivably just enable the sent box on the one survey and not the other which would eliminate my issue with editing the location from the data page? Chur, RyanE
... View more
06-17-2021
12:39 PM
|
0
|
2
|
2965
|
|
POST
|
@Anonymous User thanks for the response, When you mention that I can adjust the sent folder options beyond 'edit/resend' and/or 'copy to a new survey', how do I do that? We're using the desktop field app now because of the theme grid style and we sometimes need to collect data when we're offline (our network goes down a few times a year). Does the web app in a browser support theme grid now? What does editing online look like? is that through the inbox/sent box? The ideal situation would be for different logins to have different editing access to that survey. Like if 'username1' could only create and send new surveys (maybe view sent surveys), but 'username2' could review all of the sent surveys and edit/resend. Cheers, RyanE
... View more
06-14-2021
08:05 AM
|
0
|
4
|
2994
|
|
POST
|
@Anonymous User Thanks for the quick response on this, I was wondering if you could make a suggestion for my workflow. I found a problem with my work flow due to fixing incorrectly placed geopoints through the data tab in the Survey123 website. The survey is an "incident form" where we collect patient information including an incident location. Some of our employees are part-time and put the geopoint in the wrong place. Our staff uses a shared creator/user login to complete all of the surveys in our first aid room. When they complete the survey in the first aid room, they set the geopoint. This incident form includes a section where the patient dob is input and then an age is calculated which cues a guardian information section if the patient is <18yr old. Our work flow has a small group of employees with a separate creator/user that allows them to edit records. They login to the survey123 website and then review the days surveys from the data tab. They complete a few questions at the end of the survey via the table in the data tab. However, to fix the location we use the "form view" and then we "edit." When we edit the location in the "form view", it then changes the age to 0 which cues the guardian info section (if relevant, this is a required field). When we update things in the table view this doesn't happen. We cannot use the Inbox for this, because we collect two signatures in the form and they are required fields. We left the sent box disabled as well becasue we didn't want the entire staff to have editing access to any sent forms. Are there any other work flow options or work arounds? Is there a way to change my age calculation to prevent it being set to zero and we can keep our work flow? Is there a way to enable the sent folder, but prevent all users from having editing access?
... View more
06-04-2021
09:06 AM
|
0
|
1
|
3067
|
|
POST
|
Hi Ismael, Any update to this? I have field app v.3.11.164 and connect 3.11.123 and want to enable the inbox, but I need signatures to be required fields. Cheers, RyanE
... View more
06-03-2021
09:22 AM
|
0
|
3
|
3083
|
|
POST
|
I found a problem with my work flow due to fixing incorrectly placed geopoints through the data tab in the Survey123 website. The survey is an "incident form" where we collect patient information including an incident location. Some of our employees are part-time and put the geopoint in the wrong place. Our staff uses a shared creator/user login to complete all of the surveys in our first aid room. When they complete the survey in the first aid room, they set the geopoint. This incident form includes a section where the patient dob is input and then an age is calculated which cues a guardian information section if the patient is <18yr old. Our work flow has a small group of employees with a separate creator/user that allows them to edit records. They login to the survey123 website and then review the days surveys from the data tab. They complete a few questions at the end of the survey via the table in the data tab. However, to fix the location we use the "form view" and then we "edit." When we edit the location in the "form view", it then changes the age to 0 which cues the guardian info section (if relevant, this is a required field). When we update things in the table view this doesn't happen. The reason for the work flow going this way and not via the inbox is we didn't want the entire staff to have editing access to any sent forms (the sent folder is disabled too). If we could have the inbox enabled and then limit editing by adjusting the user access that would work too. Is there a way to change my calculation? Is there another way to change the work flow besides enabling the inbox? Is there a way to enable the inbox, but prevent all users from having editing access? My age/dob section of the form is attached.
... View more
06-01-2021
10:39 AM
|
0
|
2
|
1144
|
|
POST
|
Any update to this issue? Now the error is "location inaccessible" whenever I start the S123 field app. None of the machines we use need to collect a gps location. Locations are set on a map or not at all. Thanks!
... View more
05-26-2021
12:01 PM
|
3
|
0
|
3802
|
|
POST
|
When I removed the pt_dobdate row and then changed the types in the pt_dobstring row (bind::type and bind::esri:fieldtype to esriFieldTypeDate and dateTime respectively) it worked! Thanks for the help, RyanE text pt_dob DATE OF BIRTH: mm-dd-yyyy 10 99-99-9999 calculate pt_month month substr(${pt_dob},0,2) null calculate pt_day day substr(${pt_dob},3,5) null calculate pt_year year substr(${pt_dob},6,10) null calculate pt_dobstring dobstring concat(${pt_year},'-',${pt_month},'-',${pt_day},'T00:00:00-07:00') esriFieldTypeDate dateTime note pt_age AGE: if(string-length(${pt_dob})=0,null,int((today()-${pt_dobstring})div(1000*24*60*60*365.25)))
... View more
08-05-2020
05:35 PM
|
2
|
0
|
1607
|
|
POST
|
I have a text field to collect a date of birth in mm-dd-yyyy. I then have a series of calculations to convert it to yyyy-mm-dd and turn it into a date field whereby I can then calculate a persons age. The age makes subsequent questions relevant or not (ie. is the person a minor or not). This works in my original form. I created a new form and copy and pasted that section into the new form for the same purpose. The new form now gives me an error message: Below is the sample of the xls form with the dob/age calculations: I initially did the 'paste only values' and I've tried deleting the cells and then rewriting from scratch, but both had no effect. I've checked the sheet for any connections and there are none. In the original form, the dob/age calculations are within a repeat and are not in the new form, but I don't see how that would affect this. Help! RyanE
... View more
08-02-2020
08:12 AM
|
0
|
2
|
1698
|
|
POST
|
I figured this out.....it didn't like having a name in the choice list be "other." When I changed the names in the choice list to be "othersurface" and "otherequip" everything worked as expected. The problem didn't occur if there was an additional expression in the relevant column as well - ie. selected(${example},'other') or selected(${example},'na').
... View more
07-31-2020
07:14 AM
|
0
|
0
|
1542
|
|
POST
|
I'm having a similar problem. I have a form that calculates a person's age from a date of birth text field. It works in my original form, but not when I copy and paste into my new form. I'm getting the same error a "type mismatch." I tried deleting the cells and then rewriting from scratch and that didn't work. Cheers, RyanE
... View more
07-29-2020
03:41 PM
|
0
|
0
|
2813
|
|
POST
|
I noticed while creating a feature report that some select_one fields did not show when an additional field became relevant. When I viewed the record in the data tab, the record in the data table is correct, but in the form view side panel the two of the fields do not show - both are a select_ones where if the user chooses "other" a text field labeled "describe" becomes relevant. Not only does the record not show appropriately in the form view, but, more importantly, it also isn't correct in the feature report. I tried rewriting the two lines in my xls form from scratch and republishing, but that did not fix the issue. I also rewrote the the choice lists for the select_ones. The syntax in the feature report also appears to be correct. I attached a photo below showing the problem in the data tab. The red circles contrast the data table and form view panel with the issue. The green circle shows fields with the same syntax/schema not displaying the problem. I also attached a snapshot of my feature report - again with the green and red circles. Samples of my xls form and feature report are attached too. Thanks for any insight, RyanE
... View more
07-14-2020
04:42 PM
|
0
|
1
|
1611
|
|
POST
|
I used an online regex checker and I've got what I want to work, but it won't work when I put it into my form via survey 123 connect. regex(.,'^(\d)\'(([0]\d)|([01][01])|(\d))\"$') I've had a similar issue before and simply retyping it vs copy/paste solved the issue, but not this time. I'd like the examples 0'11", 9'11", and 9'1" to all be valid. Thanks for the help, RyanE
... View more
06-11-2020
12:58 PM
|
0
|
2
|
1241
|
|
POST
|
That worked! Thanks so much for your time on this. Cheers, RyanE
... View more
03-24-2020
05:18 PM
|
0
|
0
|
5795
|
|
POST
|
This is the error I keep getting. I should have mentioned earlier that our users are not always the most computer savy folks. This is the secondary reason for the text fields over the date and time fields - just typing the numbers is more straight forward for some of them.
... View more
03-23-2020
01:57 PM
|
0
|
2
|
5795
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 07-13-2022 02:49 PM | |
| 1 | 03-23-2020 11:26 AM | |
| 1 | 10-07-2022 11:58 AM | |
| 1 | 05-10-2022 01:23 PM | |
| 2 | 08-17-2021 02:43 PM |
| Online Status |
Offline
|
| Date Last Visited |
Saturday
|