Latest Contributions by JAVIERVARA_SANZ

Thanks for the prompt response Zhifang. I understand the workflow you are suggesting, but my word document is simply referencing ${Grants}. Please confirm it will be OK replacing it with ${_2020_Prescribed_Fire_Grant_Application_MASTER.Grants}. If that is the case, I'll give it a try. Also FYI, I'm not using repeats in this survey, and producing the reports directly off Survey123.com, although my step is to generate them through the API. Thanks again. Javier ... View more

Thanks Zhifang. To answer your question, 2020_Prescribed_Fire_Grant_Application_MASTER is a layer name while only Grants is a field name. However, I believe the issue is related with the name of the layer itself starting with a number, since, although the actual name in the survey is 2020_Prescribed_Fire_Grant_Application_MASTER, it has been saved in AGOL as _2020_Prescribed_Fire_Grant_Application_MASTER. As a workaround I've done the following: Export the layer to my computer Rename the feature class to (Prescribed_Fire_GRANT_2020_Application_MASTER) , the relationship class (Prescribed_Fire_Grant_2020_Application_MASTER__ATTACHREL), and the attachments table (Prescribed_Fire_Grant_2020_Application_MASTER__ATTACH) ZIP the resulting geodatabase and upload it back to AGOL to create an independent hosted feature layer (Prescribed_Fire_Grant_2020_Application_REPORT) Create a copy of the Survey and name it Prescribed_Fire_Grant_2020_Application_REPORT Update the XLXS form to add a submission URL that points to the new hosted feature layer At this point I'm able to generate the report without any issues. I can't really wait for this to be resolved, so I'm glad the steps mentioned above have worked so far. I'm not sure about the attachments though, so we'll see. The bad news is that the layer will no longer be connected to the original data source. This is not important in my case, but definitely a minus. Taking all my feedback above, could you confirm it the fact the the service was created where the name starts with a number might be the origin of the issue. If affirmative, it would be good to either allow it in the future, or make sure Survey123 Connect prevents users from creating reports under this circumstances. Thanks a lot for getting back with me. Javier ... View more

Thanks for the suggestion James. However, I am relaying on three forms per group, thus, will have to republish a total of 30 surveys (10 groups total) every time there is an update. FYI these updates would be frequent due to the fact that some dropdowns need to be updated periodically due to the addition of locations. Just for reference, we are dealing with Points of Distribution that are set up as needed. Also keep in mind each form is very specific and I wasn't able to develop them in a way that every scenario fit in a single form. Thanks. Javier ... View more

Correct James. By the way. I figured out the issue. My survey had three fields that were named with reserved words (Organization, Group, and State). These fields were flag, so I looked at the validation error from Excel and eureka. However, given the ripple effects, it was a bit disappointing that Connect allowed me to publish. What are your thoughts on this? Let me know if you'd like me to post this same message in the Early Adopter Community. Thanks for following up. ... View more