Latest Contributions by AnthonyJonesRSK

Hi, I was hoping someone could assist as I think I have stumbled across a bug with the search appearance when using url parameters in the web form. When attempting to edit an existing record in my survey, if I simply want to edit the record everything works fine. So https://survey123.arcgis.com/share/32d28c25ee9e4a0b9599bf1430162843?mode=edit&globalId=aceb084d-e547-4600-8a5e-9fc7ecedcb47  allows me to edit the record and the select_one with the search appearance (the Project Number question) works as expected, see below. If however, I want to update a field in my survey using the &field: url parameter I find that the select one with the search appearance will not pull through the existing data. So the url https://survey123.arcgis.com/share/32d28c25ee9e4a0b9599bf1430162843?mode=edit&globalId=aceb084d-e547-4600-8a5e-9fc7ecedcb47&field:example2=no where I want to update the Example select_one question to "no" causes the Project Number question to fail to pull through the existing record, see image below. To be clear this happens whenever I use the field parameter to try and update any other field. I've tried this with two surveys now and get the same result. I also searched online for this but couldn't see that anyone else had highlighted this problem. If someone could assist with this it would be much appreciated. Thanks Anthony ... View more

I've recently come across the situation where I would like to have multiple repeats all use the same nested repeat in my survey. So we have parent layer with many child layers which would all make use of one child layer. The use case for this is that we would like each repeat to have a nested repeat to record actions but we would like those actions to be recorded in one table, not multiple separate tables, for the purpose of reporting. I built a layer in ArcGIS Pro with the relationships as above but find that if I try and then build a S123 form on top of this in Connect it won't work as Connect doesn't like that they all have nested repeats with the same name. My thinking was that a bind::esri:fieldName option could be used which would mean you could give each repeat a different name in the name column (Actions1, Actions 2 etc.) so that any S123 calculations could reference the repeat but the underlying feature service would have just one table simply called Actions, added in this extra column. This may also be a solution for the issue described here where Doug outlines the need to have fields with the same name across different repeats. Connect flags these as problematic even though the same field names in a feature service across different layers is perfectly fine. This additional bind field could possibly be a solution for that whilst still allowing users to reference the correct fields in their calculations. I am sure there are reasons I'm unfamiliar with that may prevent this working but it would be great to know if it could be possible. Thanks Anthony ... View more

Hi, I'm trying to run a report for a particular record in a Survey123 survey and am receiving the error below: "An error occurred when rendering by the report engine. An error occurred when assembling data. Error message: Cannot read properties of undefined (reading 'name') The expression leads to this error: ${# IssueVisits|resultRecordCount:1|orderByFields:" OBJECTID DESC"}" This report works fine for other records but appears to have an issue with one in particular. I'm not quite sure what "undefined (reading 'name')" is referring to so any help with that would be much appreciated. It appears to have a problem with some nested repeat sections in the report , that start with ${# IssueVisits...}. I have removed these and the report runs so could do with some help understanding what the issue is with this section for this particular record. I have also done some further testing and built a test survey on top of the repeat above the nested repeat and then ran a report where each record in the repeat is a survey entry. Here the same syntax for ${# IssueVisits...} is used and it appears to work fine so not quite sure what the problem is. Any help on this would be much appreciated. Thanks Anthony ... View more