Latest Contributions by DougBrowning

This is what I do in the form. Have a calc field that counts only non 0 answers answers if(${HeightHerbaceous}>0,1,0) Then I have a second field to do an avg using Sum.  sum(${HeightHerbaceous}) div sum(${nonzeroherbhgt}) You can also use things like count() to see how many total. You could do this then you will have a field in your form that already has the Avg for you.  Then you can use this field directly in Ops Dashboard. In your example of  if(selected(${name},'somevalue'), 'Yes', 'No') Change to  if(selected(${name},'somevalue'), 1, 0) Of course if someone edits the data directly later the calcs will be wrong. ... View more

Did you ever figure this out?  Same issue.  Kinda makes sense in the flow but what to do about it? ... View more

What about a second field inside the repeat that just calc to ${loc}.  Then use this field in the join...? ... View more

I guess it does make a cycle.  Try this.  Add another field that has a calc of if(${lastChoice}= 'R1','L1','R2') then add this field as the calc value for loc.  That may trick it. ... View more

You are missing a ' in R2 value on the loc field.  Should be 'R2' but you have R2' Also note that sometimes it will add the value you just added to the list then say it is there.  If that happens wrap it in a once(). ... View more

Yep known bug that is killing me and others!  You can actually use stops_completed inside the repeat (and inside a group) then it will catch it on a repeat add.  Sorry if I wrote this wrong before - it is just min and max that need to be outside the repeat. Give it a shot. ... View more

It all looks good to me.  It could be you are now hitting the current bug in 3.3 that constraints are not working right.  Try this.  Put the ${stops_completed} question inside of a group that contains just that field - see if that will trigger it.  I did have to do this in my form due to the open bug (there are some posts about this).  Does it trigger when you try and send the form? The calculation on ${stops_completed} is join(", ", $stop_point) or similar.  I just saw that mine is actually inside the repeat and in a small group so you can try that also. ... View more

Seems like your if is wrong.  Try posting it here.   ... View more

I am not sure where relevant is coming in?  I would do it as a default or even a calculation. Create a field - ${caploc} - outside the repeat that does a join(${loc},"") (no spaces needed since your codes are always 2 chars).  This will then be a list of ALL your repeat values.  But you know that the last repeat value will be at the end. For ease of understanding I would create a second field - called maybe ${lastChoice} that strips just the last 2 chars off of the join field.  So  substr(${caploc}, string-length(${caploc}) - 2, string-length(${caploc}))  Not sure syntax is perfect - you are just trying to get the last 2 chars. Then in the default (which sometimes does not work) or a calculation column (which should always work) for ${loc} put your big If statement based on ${caploc}.   So If(${lastChoice} = "L1", "R1", etc. Does that make sense? ... View more

I have a script that just downloads the entire Hosted Feature Service as a GDB.  I found that when I got to about 700-800 MB it died on memory.  I then ran it using PyScripter 64 bit and it now works at well over 1 GB.  So i would try that.  Tip - install 64 then 32 again so that all your Arc paths stay happy.  You may need to install background 64 bit processing patch depending on the script. ... View more

So basically you need to adjust based on the value of the last repeat right? My only idea if a text field with join() outside the repeat.  You could then pluck the last 2 chars off the end of the join. So something like substr(joinfield, string-length(joinfield}) - 2, string-length(joinfield}))  Since you cannot index the repeat this is all I can think of and have used in the past. Then your default would need a big If statement using the value created above.  If lastval = L1, R1, if lastval = R1, etc. ... View more

Send the ID you decide to use via the URL also. Then create a Relationship class in the Hosted Feature service that links the form feature class to the collector feature class.  (If you need to publish a service that has both of the feature classes and relationship class then repoint your form to it). ... View more

I vote for doing this to ALL inputs.  For example a horizontal-compact a user should be able to tap anywhere on the label. A common user complaint is all the buttons are too small when you have big dirty hands and are out in the sun. Thanks! ... View more

Create a set of hidden fields - then pass the values to them (or use Notes if you want the user to see the values).  Then base the relevants off these hidden fields.  You can then even default the hidden in case values are not passed in. ... View more