Latest Contributions by DougBrowning

Check the actual data type in the AGOL service though.  I would also add time to the report just to see what time it has.  Probably midnight.  I do not do much reports so not sure. I do remember that starting a field name with a _ is an issue.  Esp layer in queries.  I do not think that is this issue though. ... View more

What is the data type in the service?  It may be regular date then you can change the form fine.  If not set the current field to hidden then add a second date/time field to your form.  Calc over the old dates to the new dates and then you should be good to go.  No need to start over. Again this was defaulting to noon.  Is it not now? ... View more

The problem is that the service backend always has time.  They just released a date only last year but its not fully rolled out yet I think.  This means it is probably defaulting to midnight UTC and then you can go a day back easy.  How old is your 123?  A few years ago they changed date only to noon to get around this.  I wonder if setting the esri type is getting you.  You can instead use date as the field type in column 1 in 123 and see if that is better.   For us in the end we just always have time.  Its good info anyway and it reduces all these issues. ... View more

If you mean will it pull items off the list as you pick them, then no.  No way to do that really that I have seen.  Best I got is it makes a list as you go (using join) and then checks the current selection against that list.  No more complicated than that. Note you probably do not any of the xyz codes or unknown codes part.  That is something we use to track plants that the crew does not know what it is.  Then its easier. ... View more

In New Map View you can now make Forms that have calculated values (plus you can control Editable, Required, and Visible).  In our workflow we have the user fill out some fields then have some auto calculations in the background fields that calculate important values for us like due dates, project size, etc.  We would want those calculated fields to fire off when editing in Excel.  I doubt you could get them to go when editing a cell?  Constraining to a widget on edits would be ok for us.  That may mess up your nice domain drops down also not sure.   For the actual editing you could look at the Experience Builder widget as an example.  You may even be able to just use their code.  They have a 123 widget as well. Thanks a lot for considering. ... View more

See my post here  https://community.esri.com/t5/arcgis-survey123-questions/repeat-duplicate-preventer/m-p/1155978  ... View more

Sorry but it has been like this for years so it is probably not going to change anytime soon.  Also 80 pulldata calls would probably make your form rather slow.  May want to consider a different workflow. ... View more

I think maybe with repeat count it will load X number at once.  Then as they scroll through them the pulldata should fire as they go.  That may be enough for you?  It will just not load them until they scroll to them.   Not sure how you would control which one loads in each repeat though. ... View more

No you cannot prepopulate more than 1 repeat at a time. ... View more

Ok @ShannonCardoza  for my next crazy idea.  Some type of widget in the side bar for AGOL forms similar to the ExB widget.  This could go in the window where the map is now.  The reason is we now have forms that have a bunch of arcade in they to generate field values, etc.  If the users go in via ArcGIS for Excel now they can skip all of our arcade causing incomplete records.  Or if editing in Excel would kick off the arcade just like a widget even better!  (Probably hard to do). I could also see adding a Survey123 widget in there. Then some way to restrict the edits to using a form.  Not even AGOL will limit you though I believe. thanks a lot.   ... View more

They recommend it but based on real world experience they are incorrect.  See all my reasons in the post linked above. ... View more

If the map is still sending requests when a layer is off that is probably a big part of the problem.  No reason to do that and seems strange.  Again old map viewer it was not an issue.  We keep seeing this again and again that the JS 4 versions are having issues that the JS 3 versions had already figured out.  It seems like so much code is being rewritten when it could have been ported.  Been a big step back for us in many ways. I know all of that is out of your realm.  It just has been hard to be a proponent of Esri when it just plain cannot keep up at the enterprise scale.  ... View more

10 is too few for just about every use case we have.  Esp with reference layers.  For sure needs to be updated and tested way larger than that.  Not handling enterprise class size data has been Esri's biggest downfall for years.  We broke WAB going over 250 fields once.  Every single thing should be tested at 300 fields, 100 layers, and 1 million records before it ever gets released. ... View more

Common issue is pulldata does not like being inside of an if or any other function.  Move the pulldata to its own field then use that field in the if.   ... View more

That is a bummer it would be way less work and it is already working great in the map viewer - it is only Field Maps where it does not work.  We seem to keep losing more and more functionality over time honestly.  Esp the new JS 4.0 tools. thanks ... View more