Latest Contributions by ANRGIS

I would love to know when this will be implemented. It should have been something that was added in the Field Forms configuration. I see a "default date" configuration option, but it's not enabled:  If we could set this to Today() like you can in Survey123, it would be ideal. ... View more

We are also experiencing this.  I'm subscribing for updates.  Thanks! ... View more

This is still an issue. Any timelines for the upcoming update? ... View more

I'll make the change see if it works! Thanks @ZacharySutherby  ... View more

Did you ever get a response to this issue? I'm receiving the same error after upgrading to 10.8. The issue seems to exist within modelbuilder. The irony is that it will run when accessed from the toolbox. When the model is published to a service, it fails. ... View more

Lesson learned...just put allowUpdates=true query in the bind::esri:parameters column for the beginning of the repeat and ALL your repeat data is retrieved from the Inbox.  Thanks Luba Hristova‌ ... View more

Thanks for the clarification. I'm testing on iOS v3.5.164 (8 plus) and publishing the feature service to AGO using Connect v 3.5.157. I created a new survey just now and I'm still not able to retrieve the repeat records. I JUST have allowUpdates=true in the bind::esri:parameters column. What gives? Luba Hristova‌, I did try and populating all the repeat fields with allowUpdates=true and still didn't work  Survey attached. Thanks! ... View more

Hey Doug, I was merely giving expanding on my experience with it. Typically when these cases arise, Esri-staff will take note and add stakeholders to a particular issue.  I agree however, that having a place of known issues would be nice to go to with perhaps a link of a workaround to get you by until the issue is resolved. It's also nice to validate that an issue you are experiencing is known and not something I'm missing. Take care. ... View more

Since the addition of validation through equations for required fields, it seems like the functionality should be reverted so that required fields within repeats cannot be skipped. For instance, we can have a validation question... To keep this in the realm of trees, say a question whether a measurement is required.  This question is default to 'NO' so the repeat is hidden. I can set the required measurement fields to NOT be required since the repeat is hidden using an equation based off the validation question. If 'YES', then the measurement repeat is visible and the required measurement fields are now required because the validation question is now true. What it fails to do now, if there are multiple measurements, I can submit repeats without entering values within the measurement repeat section... If I'm not submitting the survey until later (say, I'm surveying many trees), I don't realize that I've left those required measurements blank.  ... View more

They actually went away again and removing the group and re-adding the group fixed it... However there definitely seems to be some instability.  ... View more

Thank you Patrick, I do see our items showing up in our site now.  We will wait for some guidance on what to do about the search using inclusive queries.  ... View more

This was an incredibly intrusive release that has essentially broken our current Open Data site as well as the State of Vermont's site without warning. We have set up cards in our Open Data site that searches based on keywords. For instance: search?tags=isothemeboundary,isothemecadastral datasets?t=keyword1,keyword2 datasets?t=any(keywords) etc. With this update, I cannot even browse any of our datasets... http://anropendata-vtanr.opendata.arcgis.com/  There should have been an option to upgrade and doing so, would clone the site to test the functionality before releasing this. It has rendered our site useless and we now will likely have to spend a considerable amount of time with support fixing it. Steve Sharp ... View more