Latest Contributions by erica_poisson

Hi Ismael, Thanks for the call earlier and explanation about the proper syntax to use to fix this issue. Using the ${layerName.fieldName} instead of just ${fieldName} solved my problem. I'm now able to print reports and successfully have information from different related tables print to one table row. Thanks so much! Erica ... View more

Hi Xander, Sorry for the very late reply. Yes - it is the case where I want to replace the entire text (label) in each instance. So, the replacements would be: 1. Original text = '51 east entrance', replacement text = 'East Entrance' 2. Original text = '54 middle entrance', replacement text = 'Middle Entrance' 3. Original text = '1', replacement text = 'West Entrance' ... View more

Hi Xander, I am trying to do this as a label expression, therefore each replace statement needs to apply to a label for one of three features. I don't see how the above statements could apply to this. Thanks, Erica ... View more

I do have a question about BUG-000114116.I was actually the person who submitted this case to get this logged as a bug. I have a report template that I just tried testing, but was unable to get this to work. Does this bug fix also apply when attempting to write attributes from a nested repeat to the same row of a table? I can attach a sample Word template if that would better help explain this question. ... View more

Hi Phil, Thank you! I do have an additional question - if it is more important to me that end users can see the repeat information in the field, could I remove the repeat counts on the repeats towards the beginning of my survey and leave the "query" parameter within the bind::esri:parameters for those 4 repeats? That way end users can see the information they entered during their "pre-field" work, but not make any changes? I made the change above, and received the following error message when trying to view the feature layer item details in AGOL - "Unable to load https://services1.arcgis.com...=json status: 500". I saved a copy of my XLS, deleted the survey and recreated it. I tested my workflow - complete the "pre-field" portions of the survey on my desktop, submit it, and then open the survey on my iPhone, retrieve the partially completed survey from the Inbox, complete and submit. Now, there are no errors when submitting the survey, however I still get the "Unable to load https://services1.arcgis.com...=json status: 500" when trying to view the feature layer item details in ArcGIS Online. I also can't load the data in the Survey123 website. I checked the ArcGIS Online Health Dashboard, and there are no issues shown. I went back into the Survey123 app on my PC, refreshed the Inbox and can see the completed survey there - including all of the information within the "multiple waypoints" and "related table photo information" sections. This seems good, but I'm perplexed by this new issue. Again, thank you for the continued help with this! Erica  UPDATE: It looks like there were intermittent issues with Hosted Feature Services this morning, which were the root cause of issues on my end. I just tested viewing my data via the Survey123 website, and via the Item Details page of the feature service, and it seemed to be working without issue. I was also able to export to both of my report templates from the Survey123 website. I really appreciate your continued help with this, I don't think I would have figured out that repeat counts/the bind::esri:parameters were causing issues without your assistance. ... View more

Hi Phil, We are editing via the Inbox. It's good to know the error is re-produceable, however I am curious why I was able to successfully edit a survey via the Inbox, and submit (with attachments to the nested repeat) when initially testing this survey around February 1; I also had a test user who was able to successfully do this around the same time. I was thinking that maybe it was my bind parameter for the "multiple geopoint" and the "related table photo information" repeats that was causing the issue. I had it set so these could be editing via the Inbox. I removed the parameters, republished the survey and did another test, but saw the same result. Erica ... View more

Hi Phil, Yes - the error (or lack thereof) only occurs when editing a record and re-submitting. Just for some additional clarification, when users are completing the 'pre-field' portion of the survey, they are not completing at information in the "multiple geopoints" feature layer, or the "related table photo information" table. It isn't until the 'in-field' portion that the tables I just mentioned are completed. During this time, the main feature layer and some of the other related tables will also be added to. I've attached a copy of the XLS form here. Thank you so much for your help with this!  Erica ... View more

All of the testers, myself included, have re-downloaded the survey to see if that helps with the issue, but it made no difference. I just tried again this morning, and see the same hang-up on the nested repeat table (Related_Table_Photo_Information) via the "sending" dialog. When I originally tested this survey after building it, it was not shared, and it worked fine. After initially sharing with my testing group, one person was able to successfully complete the workflow and submit the survey - this was around February 1-4. Since then, no sharing to either the form/feature layer has been changed.  I am curious if it is the workflow causing the issue, although it did work initially. It goes as follows - begin the survey on a PC and complete 'pre-field' portions; submit. When in the field, go into the Inbox, fetch the proper survey and complete. Portions completed in the field include questions in the 'main' table, a few repeat tables, and the nested repeat portion which consists of the following: a repeat that can have multiple geopoints, and within this, a nested repeat table where with attachments, that can be submitted multiple times per geopoint. Here is my schema: All users are able to submit the 'pre-field' portion of the survey. When attempting to submit after accessing the survey from the Inbox, the survey hangs when submitting. All devices see the same error - I've personally tested on Windows PC, iPhone, and MacBook. My users have tested with iPads. I've attached a log file from this morning. ... View more

Phil, Will nested repeats in a survey, when using the most updated versions of Connect and the field app prevent the survey from submitting? None of the questions in the nested repeat have relevant or calculations outside the repeat, but there are photo attachments. Thanks, Erica ... View more

Hi Phil, Thank you for the clarification on this! I appreciate it. It took me awhile to realize that I was attempting to use the results of a select_multiple within my conditional statement, and now I do see why that is a problem. Although I understand that select_multiple questions come into an attribute field as comma separated values, will it ever be possible to use them in if statements as I had been trying to do? I know my user who wanted this capability will ask me, so I'll give them the official answer. Thanks for all the help. Erica ... View more

Hi Phil, Could you take a look at the conversation between Stephen and I on this thread Conditionals in Survey 123 Reports  and let me know why his statement works and mine doesn't? It seems to me our syntax is identical, so I'm just a little confused. Also, the documentation on Ismael Chivite's https://community.esri.com/groups/survey123/blog/2018/07/06/bull-release-30 posting made me think this sort of thing was possible. Thanks again, Erica ... View more

Hi Stephen, The LD_Other_Sign_Details field is a text field; this only shows up when the answer to Corner Landmarks (a select multiple question type) is equal to "other_sign". Is your city field a select one question type? Part of me wonders if the fact that my Corner Landmarks question is select multiple is causing this to fail. But yes - I have received responses say this isn't possible/wont be possible, which is disappointing. I see no difference in our syntax that would cause your statement to work, and mine to fail. I've also read the https://community.esri.com/groups/survey123/blog/2018/07/06/bull-release-30, which is what led me to believe this was possible in the first place. ... View more

Hi Phil, Are there any plans to include the capability for if statements to control what displays in a report template? If yes, is there an anticipated date when this will be available? I also think it could be advantageous to update some of the documentation surrounding this, as I didn't find it very clear there. Thanks, Erica ... View more

Just curious if you ever figured out a solution to this, as I am having a similar issue. I use the syntax - ${Standing_Location} (${if Corner_Landmarks==“other_sign”}${LD_Other_Sign_Details}${/} With the example that I'm testing the record has Corner_Landmarks equal to other_sign, and details filled out in LD_Other_Sign_Details, however nothing prints. All I get is the result of the Standing_Location field. ... View more