Latest Contributions by TregChristopher

Thanks Ismael, I tested your workaround (replace today() in default with once(today()) in calculation) and can confirm it does seem to be working in a webform when published from the latest Connect. Looking forward to having the constraint message issue solved as it will help with problems with 1) dates (it is surprising how many people are accidentally creating an obs date year of 1919 instead of 2019!..and this is in turn is causing a Python 3.6 datetime.datetime.fromtimestamp() method to fail) and 2) being able to constrain the location selected: https://community.esri.com/thread/228352-use-constraint-on-location-to-prevent-default-loc-from-being-accepted and https://community.esri.com/groups/survey123/blog/2017/10/26/limiting-extent-in-which-input-point-can-exist. ... View more

This is very discouraging to hear. The number one request that my agency would have of the Survey123 team is to maintain a stable product over adding new functionality. Please, please stop breaking stuff that previously worked when new versions are released! Don't get me wrong, I love having new features like the GNSS receivers compatibility with Survey123 but it's embarrassing to have to explain to my customers, why their existing form is no longer working or that we have to wait another 3 months for a  fix that was promised 3 months ago. And if these bugs, that rollback previous functionality, do inadvertently slip thru the testing before a new release (understandable on occasion), then the answer should always be 'hotfix in x days/weeks" not "we'll get this fixed the next major release 3 months from now"...and then after patiently waiting for the release to happen (because there is no status report on what's changing with the next version until it's actually released and provided like above), it turns out that no, the thing that was broken with a new release back in October actually won't be fixed until May.  To recap the 2 issues: -default dates (created from connect and applied to webforms) broke with this release -constraint messages (created from connect and applied to webforms) broke with a release in early October ... View more

The issue Constraint message in Web Form persists during correct answer was not fixed with this release! Also, it looks like a default value for a date field ( e.g.(today()) is now not being added on load to the webform. This was working in an early Feb release. ... View more

I just tested and this was NOT fixed with the 3.3.51 release! In addition, it seems like the default condition for my observation date field (today()) is now not being added on load to the webform. ... View more

Thanks James, I'm glad to know that pulldata('@geopoint', ...) function now works in webforms. However, I think I need to wait to implement for two reasons: For the 'constraint message' issue to get resolved at the end of this month. And more importantly, the constraint doesn't seem to work on a hidden field (in the webform version). I just posted about this in Michael's post , (so sorry for the cross-posting!) ... View more

Good news! The pulldata() function is actually now supported in webforms for the geopoint! Not sure when this enhancement was implemented but I tested this out successfully after S123 team responded to my related question about constraints on the default location:https://community.esri.com/thread/228352-use-constraint-on-location-to-prevent-default-loc-from-being-accepted However, there are two things that are not quite working yet to implement exactly the way Michael describes above: 1. Constraint message improperly shows OnLoad of the webform (this is supposed to be fixed by end of Feb according to post:https://community.esri.com/thread/223993-constraint-message-in-web-form-persists-during-correct-answer 2.If I apply a constraint to a hidden field (e.g. Michaels "Within Specified Extent?" or my "Latitude" field). The constraint does not seem to be used by the webform and I can submit a record while violating the constraint. Once I turn this field back on (either as a note, integer or decimal), the constraint functions properly again. MY current workaround is to put the constraint into the note field that warns about the constraint (e.g. Michaels "Specified Location Outside of Ireland" note or my pic below). This is a little clunky because this shows up by default and just turns red after the user tries to submit. ... View more

Excellent post by Michael Kelly but for the web version of Survey123 I don't think this will work...unless you're planning on extending the limited pulldata functionality in the web version to geopoint questions soon? Might there be another workaround that requires the observer to do something with the map control (pan, zoom,etc) in order to show "success" on this required field? Because I'm centering the map in Connect, the default center location is being used to fulfill the "required" condition and the user isn't forced to make changes to this location before submitting. ... View more

I'm seeing the same thing as Nick and (pretty sure) I didn't see it when I first published forms from Connect around 10/23 (using v 3_0_149) but then upgraded in November (to v 3_1_126) and now see the constraint messages, on load, in the webforms. Confirming also that field app version still works as normal and that for webforms, the constraint shows regardless of custom vs default message and that it is on two different types of constraints ( a date field and an email field) (see pic below). ... View more

Excellent! This is really helpful and I just tested it out and it worked fine...I never realized there are other 'type' values that we can include in our spreadsheet beyond the list of available options. As a suggested future enhancement, it would be nice if videos were also somehow bundled with the image type, so that it would show the camera icon and provide the capability to capture either a video or a photo with their device while completing the form (like what they can do already with just photos). ... View more

Hi John, What do you think the turn around time is for fixing a bug like this? i.e. When is next S123 release and is it possible that it would be fixed by that next version? ... View more

This still wasn't working about a month ago but there must have been a recent update because I can confirm that this is working now (Py API 1.4.1): ##delete all features via truncate tblTaxo.manager.truncate() Pre-overwriteFeature count: 0 from arcgis.features import FeatureLayerCollection tblTaxo_flayer_collection = FeatureLayerCollection.fromitem(items) #call the overwrite() method which can be accessed using the manager property tblTaxo_flayer_collection.manager.overwrite(tblTaxoGeolib) Post-Overwrite Feature count: 2431 ... View more