Latest Contributions by DougBrowning

Some of it was setup before me so there may be another way but I didnt find one.  On my big form with choice list of 5,000 they are all external_choices.  So I use multiple columns to break up the list different ways. So my external choices looks like  Then my choice filter does things like this if I want all of them I do fulllist=${fulllist} If I want just Woody I do Type=${woody} If I want some combo I do  Type=${woody} or Type=${herb} or Type =${unknown} Or even Foliar=${fulllist} or Type=${none} One trick is it will not take text for some reason So Type="Woody" will not work So I just made dummy fields like this But I am not basing any of this on a previous field so that gets harder. For you it depends how many combinations you have.  You could make more columns instead of rows So a column of M with a Y in it. Then a second column called E with Y in the right choices, etc. But looking at yours I am not sure you can use a field name as the column filter name?  James may know. So filter = ${wlsystem} turns into ${wlsystem} = "Y". I guess it is tough without knowing your workflow. Other times I just allow them to add bad values then check it with a constraint instead. I would also read this page Cascading and external selects—Survey123 for ArcGIS | ArcGIS  ... View more

contains() returns true and false.  Choice filter is doing a lookup query.   The last line looks right but the contains line would just calc to True.  That does not tell 123 what to go fetch. Use the method in line 5.  You can build more complicated queries or add more columns to use in filtering. I think that is what you are seeing. ... View more

Are you using an iPad by chance?  Just had a support call because iPad will shut off location access to the app every time you update.  Go in and make sure it has access to Location. ... View more

Bump again.  Selections are the heart of ArcMap.  So weird that AGOL does not use them at all. ... View more

Has anyone found this yet?  Seems simple enough and SOP in ArcMap. ... View more

I thought of this later also that I should have made the note about integer.  I was on a phone quick. I do like that way you write that James.  Thanks ... View more

Sorry I should have included that.  I figured it would come up. You want it to evaluate to true so I just use 1. So if(check, constraint, 1) ... View more

It works in a GDB but does not work when hitting a in_memory set in Python.  Says invalid SQL statement. thanks ... View more

Yep found my own old post about it. I was hoping it was the numeric issue.   https://community.esri.com/thread/218020-cast-does-not-work-in-searchcursor-queries  ... View more

Again today having lots of QA issues due to 123 not having a way to require validation by Page. Here is the workflow. On Page 1 there is a required field of Line Number. User skips this. On page 3 they add 50 repeats.  Each repeat inherits the Line Number. So if Line number is blank all my repeats are PlotKey_ (instead of PlotKey_1). User submits and Line Number is flagged.  User sets LineNumber to 1. Now I have the header being correct as PlotKey_1 BUT all my repeats are now orphans. I am sure you are sick of me asking for this but we are now spending thousands on labor to go back and clean these all up.  Then I take heat. Please consider it!  Thanks! ... View more

Ok finally got it.  You need to use NUMERIC and give it a size.  You also need the field name in "". So this worked CAST("RockFragments" AS NUMERIC(38,9)) <> (CAST("ESD_FragVolPct" AS NUMERIC(38,9)) + CAST("ESD_FragVolPct2" AS NUMERIC(38,9)) + CAST("ESD_FragVolPct3" AS NUMERIC(38,9))) This help says you can use double but it never works.  Crazy how bad this help page is. SQL reference for query expressions used in ArcGIS—Help | ArcGIS for Desktop  Edit:  This worked great in a ArcMap Def Query but bombed in a search cursor in python with invalid SQL statement. whereClause = 'CAST("RockFragments" AS NUMERIC(38,9)) <> (CAST("ESD_FragVolPct" AS NUMERIC(38,9)) + CAST("ESD_FragVolPct2" AS NUMERIC(38,9)) + CAST("ESD_FragVolPct3" AS NUMERIC(38,9)))' It is hitting a in_memory table so that may be it.  I have found that in_memory sets do not support all the SQL that geoDBs do.  Which is not documented or anything.  This may be what stopped me from cast in the past.  Bummer. Any ideas? thanks ... View more

What about for DOUBLE or INT?  I can never get cast to work for numbers and had given up till I saw this post. CAST(RockFragments AS DOUBLE)  is a no go ... View more

if I remember right I got around this by using an if in your constraint. So say if value1 is not blank then check constraint otherwise do nothing. ... View more

I heard back that a official bug has been created for 3.5.  It is for pulldata though so prob not yours but thought I would post. BUG-000123478: Previously functioning Survey123 Survey missing fields in most recent 3.5 release. Specifically (from the case notes):   "I believe the issue may be with the pulldata function. Even in the sections (i.e. groups) that do appear, the questions that have the pulldata function in their calculation (or that reference fields which use the pulldata function) are either not appearing or are failing to calculate. There are also a couple fields that use pulldata which are not in any group, and they are also failing to appear." ... View more

I think this is actually now correct in 3.5.  You should NOT be able to move to the next repeat until ALL constraints are satisfied.  The old way it was letting you skip and move on - which was bad for me.  In fact I had to create workarounds to make sure it did stop from adding a repeat. Does this sound like it? This sounds like another care of letting us control when validation happen through settings. ... View more