Latest Contributions by JeffPuuri1

Hi James, I am actually working on this same issue as well.  What happens on your end if you add a query to your bind::esri:parameters so that it now looks like this: query allowAdds=true allowUpdates=true, and then follow your testing procedure?   Without query in the parameter list, in your testing procedure after step 3, you do not see the previously submitted repeat record, correct?  In our workflow, we would like to see the previously submitted repeats records, fully understanding that we would not see the previously submitted image, but would be able to see the other input fields which is important context for our workflow.   What we are finding is that when prepending query to the parameter list, and following your testing procedure, after step 5 we can see the additional related records in ArcGIS Online with the attribute fields filled in, but the Photos and Files column has 'Add' instead of 'Show' like we see for the attachment submitted during original survey submission at step 2. ... View more

Thanks for the clarification, James.  In fact I was just coming back here to update this thread with a report of success by simply entering the bare words query allowUpdates into the bind cell for the case where I don't need to filter anything coming back out during a refresh.  Thanks for pointing out the formatting nuances when further filtering might be necessary. ... View more

I have attached the XLSX for a super simple form that I use for Inbox Refresh testing with Repeats blocks.  When I send the survey, I can see the attribute values in the main and related classes for the feature service.  In fact I can edit attributes from the main survey and the related records in an Arcgis Online web map.  However, when I refresh the Inbox in Survey123, I see the edit changes to attribute values in the main survey, but the repeats block is essentially empty as it is ready for data entry into the 1st record, even though the underlying feature service has more than one related record.  In the bind::esri:parameters column on the begin repeat row I have tried it with allowUpdates=true and another time with allowUpdates=true 1=1, but neither time could I refresh previously submitted values back into the fields within the Repeats block. JTedrick-esristaff‌ you mentioned that you had been able to have this work on an Esri test service.  Do you see anything configured for the Repeats block in the XLSX that I have attached that is different from what you are doing?  Also, is there anything else I can check configuration-wise on the feature service itself? Thank you, Jeff Puuri ... View more

I am also trying Refresh previously submitted values in attribute fields contained in Repeats blocks on my survey form.  In the bind::esri:parameters column on each begin repeat row, I have the value set to allowUpdates=true.  But when I refresh, none of my Repeats blocks contain the previously submitted values.  I did try the syntax shown in the initial post that also has query='1=1' but was receiving an error during the refresh so I went back to just allowUpdates=true.  I do not have an Inbox filter set. I did try enabling this setting on the Repeats blocks on a service that was already published.  It was able to republish without overwriting the data.  But I was wondering if I might to delete this service and publish from scratch.  Bottom line, has anyone been able to get this capability working per the Survey123 documentation?  Thanks for anyone who might be able to provide some additional configuration that I might be able to try. ... View more