Latest Contributions by TregChristopher

Yes, thanks!  It's been awhile since I looked through those formulas and had never used those particular, pulldata options before. Below are screenshots of getting the form mode and using the form mode to change behavior on "PhotoCount" and "IsAttachment" field...probably could be simplified more but works for now. Spoke to soon...there is a mistake in the final calculation above (where the IsAttachment field should equal yes (10 as domain code) when at least one attachment created. If Photocount is null instead of 0, the calculation will result in "No" for IsAttachment. To trap for null, use coalesce in calculation to force it to zero from null: if((coalesce(${PhotoCount},0)>0),10,20)       ... View more

@IsmaelChivite your guide  for creating a count of attached photos works great when submitting a new record (snippet below) but when the user edits the survey (from the inbox) the attachments aren't editable (which I know is a known issue, that you all are working on) but the problem is that the record count also gets reset to null (or zero). integer photo_count Photos submitted   count-selected(${photo}) This is a similar problem to other "in form only" workarounds we use (e.g. calculating on non-relevant field) that work on first submission but then do unexpected things when editing a previously submitted record. I'm wondering if there is some check in Survey123 that we can use to auto-detect whether the record is new vs in "edit mode"? We can then check for the mode to modify you phot count example to something like "if([new mode],true),count-selected(${photo})". This mode check would also help with other calculations and relevant conditions that give different results when editing. screenshot of new record before submission   screenshot of editing record from inbox ... View more

I get a message: {'success': True}  but when I look at the layer interface (the list of values) or review the json of the service (.../rest/admin/services/..), nothing has changed. When I do this manually (on the rest/admin/services update definition I have to change the line lasteditdate = " " (removing the date and replacing with quotes with a space following the known issues described in:https://support.esri.com/en/technical-article/000014622) and then the changes are successfully applied. Wouldn't you also need to include this lasteditdate line in your dictionary? If so, I've tried something like this (see below) with the same 'success' message but without changes successfully applied.   #define the update dictionary ##test using the entire copy of the json of the service ##(as if you were doing it manual update with the .../rest/admin/services/... url for that service) update_dict = { "editingInfo" : { "lastEditDate" : " " }, "fields": [ { "name": "OccurTaxoID", "domain": { "type": "codedValue", "name": "cvd_OccurTaxoID", "codedValues": [ { "name": "Amphibian!!: Unknown/Other", "code": "-1113" }, { "name": "Frog/Toad!!: Unknown/Other", "code": "-1114" }, { "name": "Frog/Toad!!: Bullfrog", "code": "-1115" } ] } } ] } ... View more

Just found today that Ismael has already provided an answer to this in one of his many excellent blog posts:https://community.esri.com/groups/survey123/blog/2017/11/14/understanding-notes-in-survey123 ...Just provide an html tag in the label and that will satisfy the requirement for needing a label for a note and then you can use the hint (or a calculation in Ismael's example) to provide the actual note information with the proper html formatting. ... View more

As of June 23, 2020 the Edge browser's (Microsoft Edge 44.18362.449.0, Microsoft EdgeHTML 18.18363) the auto-complete is still only looking for values that begin with what your typing, not anywhere else in the text. ... View more

Hi Ismael, The default bold makes total sense for field labels except when it is a note field, where you might not want anything bold or just a key phrase in a larger sentence to be bold. I can sort of work around by putting the note's message in the hints field (and just bold-ening what I want) but since some kind of label is required, it's not a full solution. And this is only a problem for the web form. It looks like the field app (at least Connect's preview) recognized bold tags within a note's label. Treg ... View more

That all looks right to me...Sorry I can't think of anything else as to why yours isn't working. And yeah, hidden constraints don't seem to work on the web form (but do in the field app). This would be a nice feature that I would love to see working in the web form. ... View more

My location constraint on web from is working fine. It is a read-only note field, has a calculation to sum 2 integer fields (int(${ValidX}) + int(${ValidY})), and a constraint of .=2 so it won't show the constraint message unless the calc doesn't sum to 2. Just tested the web form (https://survey123.arcgis.com/share/a384e90f69744f2e846135a9ce80027f ) and it does in fact show the constraint message and prevent the user from submitting until they correct their location. So I think in general, constraints in web forms seems to be working as expected, since the 3.4 or 3.5 release. In my situation with a spatial constraint, ideally the constraint would be on a hidden field (instead of a note field) because the constraint message shows on form load...so a a little messy looking but it is good enough for now.  One thought is that since you are using a note field, I think the calc needs to be cast to integer ( e.g. my calc is:int(${ValidX}) + int(${ValidY}) ), otherwise it might read the result as a string and then the constraint wouldn't fire if it is expecting your integer value of .>0 ... View more

Thanks James, I'm glad the email field will work when we get exchange online enabled. For the domain code-to-description issue: It certainly seems far easier to do this in Survey123 and I have done this once before (using pulldata rather than your jr:choice-name() function, which I'd like to try out soon) but then you are just creating new fields to store the string of a coded value domain, which seems like you are defeating the purpose of using coded value domains in the first place. I've tried to follow your suggestion of creating a variable in Flow but I'm still stumpedeven after going through several Microsoft-Flow posts on this subject. Below is what I have tried to come up with (which isn''t working) but I just can't seem to make the jump to creating a array variable (there is no dictionary variable) in Flow and then use that in an expression to tell the message post to show either "Yes" or "No" (instead of code 10 or 20) from a field in Survey123 called "IsSGCN"...Do you, Ismael or anyone else have a clear example of mimicking these coded values in Flow so that the domain descriptions show in the posted message? I know this is more of a MS Flow issue than Survey123 but any help would be appreciated! ... View more

Apparently I  haven't been using this much because I just tried again and it seemed unsuccessful...the record count remained the same between the original 2431 and the overwrite, which should now have 2434 records. I didn't check whether any changed attribute values were overwritten or remained the same but the lack of change to the record count would seem to indicate that nothing else was overwritten either. This is a table in an SDE,so I don't think your source as a feature class in a file geodb is the problem. I did get a warning (not an error) that the dataframe (df) is being deprecated in favor of the spatial dataframe but since it was a warning, I don't think that is the error either. I am now working off of Py API version 1.6.1 Now removing all records from taxo table... Pre-Truncate Feature count: 2431 Post-Truncate Feature count: 0 Now overwriting taxo table... Post-Overwrite Feature count: 2431 C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\lib\site-packages\arcgis\features\feature.py:612: UserWarning: The SpatialDataFrame has been deprecated. `df` property will be removed as a future release. Use `sdf` instead. warnings.warn(("The SpatialDataFrame has been deprecated. " ... View more

Hi Orlo, My Survey123 web forms have been working for over a year now and allows for anonymous reporting with attachments. I have a "collect with attachments only" Layer View that is shared to everyone and is derived from a master hosted feature layer that only I can access.  example form: https://survey123.arcgis.com/share/a384e90f69744f2e846135a9ce80027f  Settings on view that the form is using: ... View more

Ahh, yes! Thank you James and Jeff for identifying the problem. Most of the agency computers are still on Edge 41.16299.1004.0/EdgeHTML 16.16299 while some test computers (my laptop included) have a major Win10 upgrade that has Edge version 44.17763/18.17763. My laptop loads those forms without issue, while my desktop (on the older version) generates the "append" error. I believe that the agency will be upgrading soon, so the problem should go away for all staff, once this happens. ... View more

Thanks Shwu-Jing, I will send in a ticket and after a solution found, I will provide a response here. ... View more