Latest Contributions by DougBrowning

I am not allowed to share the whole form but this should help. Inside the repeat you would have the field you want to hold the Auto Incremented number - lets call it PointNbr.  That field would have a calculation of once(count(${RecKey})).  Where RecKey is any other field in the repeat.  You cannot count itself so I just picked a field. You are basically saying count up all the repeats and use that number as my Auto Increment number.  The Once tells it to just do that calc when the repeat is first created.  Otherwise it would constantly change when you went back to a old repeat record. Hope that helps ... View more

Ran several hundred Samsung Tab As for years and they work great.  Only had 3 die in 3 years!  Was getting them for $169.  But they are rather slow now and I would no longer suggest them. The best bang for the buck is probably the Samsung Active 2 now.  Fully ruggized from the start.  Writes in the rain even.  Not a bad price. I do wish Samsung made a new budget line but not so far. ... View more

Are you in a repeat?  I had this issue for months and finally tracked it down. If you have a drop down in a repeat and that drop down has a choice_filter that uses a field that (like fulllist=${fulllist})  and that field is also in the repeat it is super slow.  All I did was move the field used in the choice_filter outside of the repeat and my form went from 20 seconds to 1! Check to see if you are doing this. ... View more

Well it turns out that either SearchCursor  (or cause it is a in_memory FC) in Python will not take Similar To.  A Similar To query works just fine in ArcMap Def Query but when I try it in a SearchCursor it says Invalid SQL statement with no other info. Long sigh.  Back to writing the whole thing out I guess. Proof we at least need a doc that shows all of these inconsistences. ... View more

Well it turns out that either SearchCursor  (or cause it is a in_memory FC) in Python will not take Similar To.  A Similar To query works just fine in ArcMap Def Query but when I try it in a SearchCursor it says Invalid SQL statement with no other info. Long sigh.  Back to writing the whole thing out I guess. Proof we at least need a doc that shows all of these inconsistences. ... View more

Ok so % works in SQL with LIKE but [] does not. % does not work with SIMILAR TO but [] does. And some of this only works in 10.6.1. That was some work to unravel.  Thanks a lot I am just going to use TopCanopy Similar To 'AG[0-9]*' ... View more

Ok so % works in SQL with LIKE but [] does not. % does not work with SIMILAR TO but [] does. And some of this only works in 10.6.1. That was some work to unravel.  Thanks a lot I am just going to use TopCanopy Similar To 'AG[0-9]*' ... View more

Found more documentation and this seems to work TopCanopy Similar To 'AG[0-9]*' It just does not like []% ... View more

Found more documentation and this seems to work TopCanopy Similar To 'AG[0-9]*' It just does not like []% ... View more

Using Similar To or LIKE? I tested the heck out of it and never got it going.  On 10.5.1 using a File Geodatabase (.GDB) Watch But strangely this works And this does not So maybe the % does not work in combo with []? What am I missing? Thanks ... View more

Using Similar To or LIKE? I tested the heck out of it and never got it going.  On 10.5.1 using a File Geodatabase (.GDB) Watch But strangely this works And this does not So maybe the % does not work in combo with []? What am I missing? Thanks ... View more

I am testing this and SIMILAR TO does not work when using wildcards but does work otherwise. So AG3 similar to 'AG3' works but AG3 similar to 'AG%' does not work. (AG_ does not work either) What I really want to do is [1-9]! ... View more

I am testing this and SIMILAR TO does not work when using wildcards but does work otherwise. So AG3 similar to 'AG3' works but AG3 similar to 'AG%' does not work. (AG_ does not work either) What I really want to do is [1-9]! ... View more

Yep most of my day is doing this type of data ballet.  Keeps us working though! I agree that live time data stuff is something Esri really lacks.  It is all based on processing data vis scripts etc, not reacting live time.  Arcade is a start at this and when collector gets Arcade you may finally be able to write something once that works in web map and collector.  In the end what normally I have to do is pull down the data, run some script on it, then republish.  I could see you running a nightly to do some of this like days. Have you looked at the Workforce app?  It allows you to get a list of To Do items and such that may help with the spatial clutter.  I think it may have severity and such also to prioritize.  Seems built to do some of what you want - like closing out a job. ... View more

You could use Arcade expressions to calculate some of it probably.  Symbols or definition query could handle some other parts. But it sounds like you have the common issue of a company wanting to use modern technology but still use there old workflows.  If they are not at all open to changing how they see items (they are probably used to static reports) then it will be a tough go.  A Ops Dashboard could quickly tell them many of the things you mentioned. For me we had a manager that refused to not get a print out from Survey123.  So I built this whole system to generate a pdf and mail it.  So the field worked filled out on the tablet, got an email, printed it, then walked it over to the mangers desk.  They then complained it was not any easier - well duh!  Then in the end I found that all the manager did was put the paper in a file cabinet - never to be looked at again!  Lot of money to spend just cause someone will not change. Just my personal view.  Good luck. ... View more