Latest Contributions by DataOfficer

Hi James, Has there been any improvement in allowing images to be attached to choices in the web form? ... View more

Thanks, all fixed. My mistake! ... View more

I am now having the same issue. When logged in as the administrator I am able to complete and submit my Survey123 Form using the Send button at the end of the survey form. However, other staff and hub community users are unable to submit data, with it getting stuck on Getting service information after clicking Send. The survey was built in Connect.  I have attached the log file from Survey123. ... View more

I've followed the instructions, and this walkthrough but I am still having issues. The SVG displays in my form but the regions aren't clickable. There are no groups and no empty paths, with each path having an ID (A, B and C). What could be causing these problems? ... View more

Hi, It was published through Connect. The reason I am using dateTime fields rather than separate date and time is that we need to calculate the difference between two periods: TimeOnSite and TimeOffSite (see below). These can be across multiple days, which is why a simple calculation between two times gives an incorrect output.  Is there a way of forcing manual input in to the time part of the dateTime field? type name label calculation dateTime TimeOnSite Survey start date and time dateTime TimeOffSite Survey end date and time integer Duration Total survey time int((decimal-date-time(${TimeOffSite}) - decimal-date-time(${TimeOnSite})) * 24*60) ... View more

Johnathan Hasthorpe‌ have there been any developments on this or any idea when it will be fixed? ... View more

This would be extremely useful for our purposes also. We have a large number of point features which we need to display to different users based on the boundaries of other feature layers (e.g. land ownership). This would need to update 'live' as new point features are added, rather than simply extracting the data within that area to a new file. ... View more

Posted as an idea: https://community.esri.com/ideas/18149  ... View more

Same problem here ... View more

Hi James, Thanks for the clarification. By creating a geopoint in the nested repeat (with coordinates pulled from the layer above), would it then store the nested repeat data as a feature layer or as a related table, as is currently the case? Many thanks, Rob ... View more

Hi James Tedrick‌, I have a similar question/problem. Background: We have a situation where volunteers are carrying out wildlife surveys. The form is setup with repeats and nested repeats. The nested repeat captures species records, within repeats that are occurring at different times/and or locations, within a survey at a particular site. A hidden field assigns a default verification status of unverified. Certain members of the project then have access via a webapp to view the records that are unverified, and edit the status to verified if they are happy that the record is correct (eg. the species has been correctly identified).  Inbox query: We want to have an Inbox query expression that returns records specific to the user, and with a verification status of unverified. This would be via a query expression of:  Creator=${username} AND Verification=0 (where 0 means unverified) However, this does not work and returns the same error when refreshing the inbox that Jordan has described for their use case. Has there been any progress on making it possible to include queries from nested repeats? The workaround I am considering is to create another field in the parent layer that summarises the verification status across the nested repeats and use that within the query (e.g. assign the survey unverified status if any record from the nested repeats is equal to 0 (unverified)). However this is not great as it applies the verification to the whole survey rather than the individual records within it and brings up a few other challenges, including how to auto-update the survey-level verification status (and subsequently the surveys appearing in the Inbox) when the record-level verification status is amended. Any suggestions? Thanks, Rob  ... View more

I have the same issue as illustrated by Colin Campbell‌. We are also running wildlife surveys in Great Britain and require the date format to be dd/mm/yyyy. Any updates as to when this bug will be resolved? Zhifang Wang ... View more