Latest Contributions by Katie_Clark

@ZacharySutherby   Thanks so much for your response and additional information about how the XLS Form works. In my case, it was the indexed-repeat as you mentioned. I'm using position(..) in a repeat question to create ID's for each entry based on it's position in the repeat. This works as intended in the survey and isn't causing issues as far as I can tell. ... View more

I'd say there are a few things to consider here to determine your best course of action. Here are my personal recommendations: Are the responses from the pre-test group valid, or is it just test data? If test data: it makes sense to delete If valid data: will publishing the updates to the survey cause the feature layer to be overwritten so you'll lose existing data? (it should give you a warning before publishing if this is the case. Only certain types of changes cause this to happen, i.e. changing a field type for a question). If no loss of data after publishing updates: keep as is. Perhaps add a hidden "Dev Notes" field to the feature layer or something, where you can write a note to indicate that the responses were submitted with a previous version of the survey, if that's info that you need to keep track of.  If loss of data after publishing updates: export the feature layer as a file geodatabase first. You can then either save these records in that format for archive/reference purposes, or append into the updated feature layer after publishing the updates. Hope that helps! ... View more

@IsmaelChivite Thank you so much for your response and confirming that - I'll open a support ticket as you suggested.  ... View more

Do you have any repeats in your survey? Aside from just a simple typo in the field name, this is the most common cause for this error. Make sure you have the opening and closing tags for the survey in the correct places.    If you need further assistance with troubleshooting, sharing the survey and/or report template would be helpful.  ... View more

What you'll need to do for this is have a hidden question for each repair type that asks for the associated number, and then they would become visible if the user selects that type. I definitely recommend reviewing this post that explains the difference between the relevant and the body::esri:visible columns in the XLS form, so you can choose which one is more appropriate for your survey workflow.  https://community.esri.com/t5/arcgis-survey123-blog/survey123-tricks-of-the-trade-hidden-relevant-and/ba-p/1165842 ... View more

Yup, that would do it! I guess I would say best practice is to just click refresh, I don't think it could hurt anything. An example I can think of for wanting them to be in sync is viewing permissions - i.e. if you have the inbox enabled in Survey123 Connect, but then in AGOL you disable access for users to view other people's submissions. There are many other examples I'm sure but that's the first one that comes to mind.  ... View more

When you published the data, did you just set a definition query to filter out the records, or did you actually create a new layer from the selected features?   ... View more

Hello @ZhifangWang , I finally had time to test this edit to the report template, and unfortunately it did not solve the problem. The first photo of the repeat question in the survey is still omitted from the report word document. However, as you can see from the screenshot below, the photo description is still pulling in as expected. When I click inside the table cell, it is empty. No placeholder white textbox/image or anything like that.    I have confirmed that the photo DOES pull in when generating a PDF directly, rather than a word document. (see screenshot below, it worked in both my original and modified templates). However, this is not a possible solution for us as these reports need to be reviewed and possibly edited, along with the fact that generating directly as PDF messes with the table formatting of the report.   Here is a snapshot from my XLS form, the photo section is set up almost identical as you have it in your screenshot. The only difference being that my image question is listed before the description question. I also have some notes fields that are used to help with UI and enforce image orientation in the survey (landscape).   Another piece of information; when I manually copy/paste the photo into the report and then save, I get this message in Word. Clicking "Details" produces this dialogue box. Clicking "Go To" then jumps to/highlights the newly pasted image.       With this information, do you have any further thoughts for troubleshooting? What could be causing the issue in Word doc but not PDF? Thanks!             ... View more

Could you provide the report template? That would help in troubleshooting. Also, do any of the questions in your report have conditional statements for visibility? ... View more

Great insight, thanks for the response! ... View more