Latest Contributions by DougBrowning

On No 1.  You do not have to make a calc variable of 1 if you do not want to.  It will count up strings just fine. The issue I see with number 2 is if a team is using multiple tablets.  Or if a tablet say runs out of battery and they pick up a different one.  How is this handled? Thanks ... View more

Thanks Phil that is great but I think you are misunderstanding my ask/issue.  I am not talking about the speed of lookups, I am talking about making the lookups smarter and improving the workflow of data entry.  Like a Google search where it tries to guess what I want based on previous answers. Our old form is not fancy technology it simply puts the last choice at the top of list for the next repeat.  This way your list eventually gets sorted with the most frequent choices at the top.  I could see how this would be tough across forms but it should be pretty easy within a form, esp across repeats.  We do 50-100 repeats per form.  I think I saw somewhere that Survey will load the choice list once into memory and then use it for each question that hits that list (at least I hope as no reason to have it in memory several times but this could explain my memory issues).  Then as users pick choices the list would put that response at the top of the list for the next question or repeat. By having this sorted in memory list you could also implement limiting the number of times a choice can be made.  Lots of posts here about people wanting to remove an item from the list once it is picked. Speed of entry is key for field workers.  In fact almost nothing else matters.  So as I mentioned our number one user complaint on Survey123 is the slow and clunky data entry workflow.  My real work example I gave above is a big issue.  We did the math and since a user must always tap, then type in 3 chars, we add 1,800 taps to each plot.  They do 2-3 a day so low end that is 18,000 more finger taps a week!   We have looked at ordering the list by most common but most common choices change Plot to Plot, and for sure crew to crew, and throughout the season.  I am sure others have this.  Our species list is 1,700 plants (per state).  Odds are you will hit a plot with a bit of a cluster of the same plant.  So you will be picking this plant from the pick list maybe 1,000 times that day.  Before that just meant tap for drop down, tap for first choice.  Now they must tap, type in the 3 chars (since so many have the first 3 letters the same), then tap your choice.  Do that 1,000 times and you will probably start to think your form is kinda dumb.  Esp since old Access could do it. I hope that lays out the use case better.  I think this is a very common one.  Anyone care to chime in?  It is also what I meant by really looking at it from a field worker view, out in the hot sun, with 1,800 taps in front of them. I believe the next evolution for 123 is "smart" forms, or adaptive data entry, or whatever you want to call it. Hopefully this makes it on the list!  Thanks! ... View more

Yep I do this workflow with 9 forms all connected.  Works great and it allows us to have multiple tablets collecting at one time.  Plus we get to us Collector for spatial and survey for forms (best tool for the job). I have a write up here on how to connect it all together.   https://community.esri.com/thread/221263-mapping-with-survey123-within-a-polygon-or-admin-unit  Hope it helps. ... View more

You could create a View off the HFS that looks just like you want it to.  Then export that. Could also make a layer file to do the same possibly.  Direst to AGOL can be weird but an export would work. Also a search cursor (or view) in python would be easy.  And then you could push the data to a location instead of a manual copy/paste. If going to anther Arc table an append will work as is simply grabbing the matching fields it finds. ... View more

I would break them up into multiple forms.  Having one giant form with 900+ fields would be unbearable for the user and prob not a great design. For us it was a plus since it allowed multiple workers on multiple tablets to work at the same time.  I did then create one master Feature Service that had all 9 forms tied together via relationship classes.  That way it is all in one place in AGOL but still broken up into digestible pieces. ... View more

Forgot to say that for now I am using a once in the relevant and it seems to be working.  I am surprised it let me do that. So this relevant will cause the field to appear when they first pick something for TopCanopy then later if they X the field it will not disappear on them. once(${TopCanopy} != '') Not sure if it will cause other issues but ok so far. ... View more

There is a way to count how many choices are picked like count-selected(question).      How about in the constraint if(selected(None), count-selected(question)<1,1) type of If.  So saying if None is selected and there is more than one selection there is an issue.  If none is not selected then then 1 just lets it go. ... View more

If you do not need Yes on the backend you could do a label of yes but a value of 1. What I did is have a second field right below the choice the does your if statement If(field1=yes,1,0).   Make sure to bind it to type int.  Then at the end of the form I can just do a sum(field1).  Can also then avg by doing sum(field1)/count(field1). I did all of this across repeats though.  Maybe you want a repeat?  Then it is just one question with a repeat limit of 20. ... View more

You cannot reduce the list.  Lots of posts on this.  You can simulate it by using a constraint.  So Field2 != Field1.  It will let them pick it but then yell at them. ... View more

is the genus1= part in the choice_filter field?  You cut off the column names but choice_filter is not next to autocomplete. I did have one case where I had to ref a second field.  That was using a txt lookup though.  So I could not do list="woody" I had to create a note field and give it "woody" as the value the write it as stuff=${notefield} for some reason. Also make sure no commas at all in your choice lists. ... View more

Thank you Phil for a more complete answer.  Not trying to be difficult but I have a lot of people counting on this when they leave for the field on May 6.  Hard to get app updates out there when people are offline for weeks at a time.  Just wanted to make sure it is in the works. I am not seeing constraints work the way you say.  A constraint will not trigger right away on focus change if the field has a relevant on it however.  I think you may have said this is a bug?  But going to Field2 now for sure does not trigger anything if there is a relevant.  I have to hit next repeat for anything to happen. thanks ... View more

Turned out to be the 2GB limit - that is why it would not show.  It was a TPK file. ... View more

Phil are you saying that the next release will stop a user from going to Field2 if Field1 fails?  That is what the user is expecting but I am not sure Survey123 ever handled that.  If this did work correctly then relevant issue goes away. I know I brought some of these points up before but not all of them.  Understand that 100s of people and millions of dollars are wrapped up in this issue, and they are all calling me, so it is not just a small inconvenience.  Telling them to wait for the next version, that has no timeline at all, is hard to get people to swallow.  Comments on here seem to down play this issue but really this bug disrupts the heart of the program and makes it unreliable and almost flat out not usable. As others have mentioned when there is a core bug like this it really needs to be hot fixed and not stretched out months.  I love the speed you guys develop at but Core functions need to be made more important over new features. Thanks! ... View more