Latest Contributions by bobwright

‎09-21-2017

Hi John, That's what I was looking for. Thanks for the prompt reply. Bob

‎09-20-2017

I am setting up a form where some check stations will need to complete additional information and others will not. For example, if the user selects the Forestville check station, we want to know whether or not the deer was harvested in the park. For all other check stations this question is irrelevant and I don't want to confuse those users with a label for something they don't have to respond to. Is it possible to hide both the item and the label? I tried just not including a label in the spreadsheet and got an error message. Please see the attached screen shot and spreadsheet. Thanks. Bob

‎09-14-2017

I am doing an external select for several attributes, then concatenating them into a unique ID for a pulldata operation. The values are coming in with 1 decimal place instead of integer and I am unable to enforce integer. Example: select_one_external dpas I have tried both esriFieldTypeString and esriFieldTypeInteger in the bind::esri:fieldType column, to no avail. See attached for screen shots and spreadsheet. Thanks. Bob

‎11-01-2016

This worked James. Thanks.

‎10-31-2016

Our data entry protocol requires that each survey be entered and completed by one person, then saved in the Outbox for another person to review for accuracy entry prior to sending. The "preview" of the attributes for each survey in the Outbox appears to be random; they are not necessarily in the order of their entry into the survey form, and how the attributes are displayed varies by person. When are large number of surveys are in the Outbox waiting for review, this makes it difficult to select and keep track of records that have been or need to be reviewed. At a minimum it would be helpful if the preview always displayed the attributes in the order in which they are entered in the form and/or displayed in the attribute table. Knowing this, the form developer could set the data entry up so that a unique identifier (e.g., SampleID) was always first. This in reference to v. 1.8.21.

‎10-31-2016

I forgot to mention that it is version 1.8.21 for all 3 platforms.

‎10-31-2016

We have been training field staff in the use of Survey123 for deer check station work this coming weekend. One of them discovered what appears to be a bug when presented with the connectivity on "Survey Completed" options. If one chooses the "Continue this survey" option, returns to the form, makes changes (or not), completes the survey, then chooses "Send Later", an extra record is found in the Outbox. If "Send Now" is chosen, the duplicate record is also generated and is sent along with the intended record. If one chooses to "Continue this survey" a second time an additional record is generated. We have found that additional record is generated each time e.g., you choose to "Continue this survey" 5 times for a particular survey, 5 duplicate records are generated. We have documented this on Windows, Android and iOS platforms.

‎10-12-2016

Hi Ismael. Thanks for the prompt reply and the suggestions. Bob

‎10-12-2016

I have series of deer check stations where the station's location does not need to be collected by the user, but is needed for later data displays. I've employed the pulldata function to populate the field, but would like to hide it from users, especially because many of the stations will not have connectivity anyway. I tried using type "hidden" and defining the field as esriFieldTypeGeometry, but when I try to publish the form I get an error message that it has 2 geopoints and only one is allowed. In the screen shot below the field of interest (station_loc) is listed as Type string though the ESRI Type is Geometry. The second geopoint does not show up in the spreadsheet, but does in the schema (last row). Is there a workaround? Thanks.

‎10-06-2016

Hi Ismael, Thanks for the prompt response. Yes that would work fine for me. Thanks for the offer. I actually started down that road and got as far as converting it to a string. I wasn’t sure how to proceed from there. You’ll see that in the attached spreadsheet. And while we’re at it, I would also like it to be a hidden attribute; I need it but the end user does not. Bob Bob Wright|GIS Specialist/Certified Wildlife Biologist Phone: (651) 539-3318 | robert.wright@state.mn.us<mailto:robert.wright@state.mn.us> 5463-C West Broadway, Forest Lake, MN 55025 @

‎10-05-2016

Greetings. I've read Ismael's post regarding this, but it doesn't address the specific question I have. I understand that using the type "date" results in 10/5/16 12:00, but I would really like it to be 2016/10/05 12:00 so I can sort properly on them (10/21/16 sorts before 10/5/16 for example). The type "datetime" results in 16/5/10 which doesn't help much either. Changing the date format in the Regional settings of Windows does not help any. Suggestions? Thanks.

‎09-21-2016

The file that James provided backed worked as both xls and xlsx files...until I populated them with the real data. Once I did that, the external select no longer worked and editing the spreadsheet back to the original from James did not correct it. Thinking that perhaps there is a bug in Survey123, I used the same spreadsheets (choices and external choices versions) to create and load forms in ODK Collect (https://opendatakit.org/). Same issue. Attached are more complete spreadsheets for our Chronic Wasting Disease surveillance operation this fall, with complete cascading select choice lists (over 5000 records). Putting these choice lists in the "choice" tab works, but it definitely responds slower and I'm worried about devices locking up in the field. So, now that I have a bad case of tunnel vision I'm hoping that someone can point out an obvious overlook for me. Thanks for any help! As an aside and perhaps a clue, I have been getting the error message below, but cannot document a pattern other than if I close both 123 and the spreadsheet, then open 123 and the form of interest I generally don't get the message.

‎09-20-2016

Attachment?

‎09-20-2016

Hi James, Thanks for the response. I looked at the schema and see what you mean. I’m not sure if you meant the ranges and sections filter or the filters for both the ranges and sections, so I tried it both ways. Neither worked. I also tried re-creating the spreadsheet from scratch with no luck. Bob type name label choice_filter select_one dpas dpa Deer Permit Area select_one_external towns town Township dpa=$ select_one_external ranges range Range town=$ select_one_external sections section Section town=$ and range=$ type name label choice_filter select_one dpas dpa Deer Permit Area select_one_external towns town Township dpa=$ select_one_external ranges range Range dpa=$ and town=$ select_one_external sections section Section town=$ and range=$

‎09-20-2016

Greetings Everyone, I can create a regular cascading select, but when I convert it to an external cascading select the choices that are in the external_choices tab do not show up in the form. I believe I've followed the guidance provided here (http://xlsform.org/#external) and in the spreadsheet example it references, but I've probably got tunnel vision by now. Perhaps it's a bug? Source spreadsheets attached. I am using Excel 2013 on a Win 7 machine. Any suggestions would be greatly appreciated.

Online Status	Offline
Date Last Visited	‎03-08-2021 01:35 PM

My Ideas

Latest Contributions by bobwright

Re: Completely hiding a cascading select

Completely hiding a cascading select

enforcing survey123 integer type

Re: Control of survey attributes preview in Outbox

Control of survey attributes preview in Outbox

Re: "Continue this survey" results in duplicate records?

"Continue this survey" results in duplicate records?

Re: Hiding a geopoint populated via pulldata

Hiding a geopoint populated via pulldata

Re: Formatting date in Survey123

Formatting date in Survey123

Re: External Cascading Select Not Working

Re: External Cascading Select Not Working

Re: External Cascading Select Not Working

External Cascading Select Not Working

Re: Publishing Failure: Error Code 499

Publishing Failure: Error Code 499

Re: Publishing Failure: Error Code 499

Spatial Join

Re: Hiding a geopoint populated via pulldata