Latest Contributions by Ruth_JiatengXu

Hi @Karl_Reinhardt, The issue has been fixed on production. You can verify the fix by adding ?version=latest to your survey URL. Please feel free to let me know if you have any question. Thanks, Ruth   ... View more

Hi @ChrisRoberts2 ,  The fix is available on production environment. Please let me know if you have more question. Thanks, Ruth ... View more

Hi @JhoanUrquia , The mode=copy was introduced in 3.11, so it works on the survey published with 3.11 or the newer version. The survey version can be checked in the browser using the console tab of the developer tool (F12). If the survey was published with the older version, you could use ?version=latest&mode=copy&globalId={} to view the behavior before you republish the survey. Please let me know if adding verion=latest cannot solve the issue. Thanks, Ruth ... View more

Hi @DeniseTolness1  Thank you for sharing your question here! Could you please answer a few questions, so that I can help you locate the cause of the issue? When you save your old form to a new form, does the new form has any data attached to it? If there is no submission to the form, the overview, analyze, and data page will not be able to show. In this case, you will see the "The survey has no records yet. Please check again later" msg. If this is not the case, could you please let me know: 1. Which method did you use to connect the new survey to the existing dataset? e.g. submission url 2. what is the behavior of the data, overview, and analyze pages? If there is any msg appearing on the page or the page cannot be loaded completely? Thanks, Ruth   ... View more

Hi @TRamos , Thanks for sharing here! I have examed your form and template, and I think there are 3 issues: The "begin repeat" type was written as "begin_repeat" in the XLSForm. Although this may not lead to a report issue, it is better to write the question type using the correct syntax. The repeat's open tag is written outside the table and the close tag is inside a table. This is problematic to the report service since the report service does not know how to deal with repeat instances. If the open/close tags are written outside the table, the repeat service will duplicate the entire section between the open/close tags for each repeat instance. If the open/close tags are written inside the table, the report service will duplicate the table rows for each repeat instance. I move the close tag outside of the table to fix the issue, see screenshot below. With this fixed, you will not see the error raised for OtherM which is the question before entering repeat. There are many fields in the report template that are not actually in the XLSForm, such as Inlet_641. All of them are removed in the updated template. Original template Updated template With these 3 issues fixed, your report should be generated correctly. Other than that, you may also need to place the open and close tags if outside the table. Please feel free to reply to this post if you encounter other errors. Thanks, Ruth ... View more

Hi @CynthiaD  Thanks for raising the issue here! Could you please help us check the choice name of the incomplete question? There is an known issue which may cause the same problem. When the choice name contains trailing and leading spaces, like "    choice_1" will not able to show correctly in the analyze page. 1. Open the browser's developer tool (press F12) -> go to Network tab 2. With the developer tool opened, load the Analyze page of your survey 3. Search for form.json, and see the details of it. 4. Under the questions node, find the question with issue -> expand choices node -> expand items node 5. Check if leading and trailing spaces are in your choice value Thanks, Ruth ... View more

Hi @KevinMWright13  Thanks for sharing here, and we will include more on string concatenation in the doc. Here is an example to create a formatted address with the line break, comma, and space. The comma and space can be added directly into the calculation field with join. Adding a line break is not directly supported in the website calculation, and this is a valid enhancement we considered to support in the further release. The example below shows a workaround method, the line break field is a multiline text question with only line break (enter key) as the default answer. Thanks, Ruth ... View more

Hi @KarimNaguib  Thanks for your reply! If you don't want to see the description on a separate page, please change the name of your survey description to something that is not "generated_note_surveyDescription", and move the note question into your first page group. Then the survey description will be rendered as a normal note question instead of the survey description. I have attached another modified form here, please ignore the warning "question has no label", and it is ok for the page to have no label. (We can skip warnings but not errors). To make it more clear, it is the by-design behavior of the web app to display the survey description (generated_note_surveyDescription note question) as a separate page. If you still need to have a survey description and you want to see it together with your first page content, please let me know. Thanks, Ruth ... View more

Hi @KarimNaguib , I modified your XLSForm a little bit, and this should make your form works as expected in the web app. I wrapped the generated_note_surveyDescription question in a group with field-list appearance (I highlighted the places I edited). The web app always rendered the generated_note_surveyDescription question as a separate cover page for the multiple-page survey, so it should be wrapped in a field-list group for the multiple-page survey. I guess your survey is published from the website as a single-page survey, so the generated_note_surveyDescription question does not work as expected. Please let me know if you have any other questions! Thanks, Ruth ... View more

Hi @Travis_GIS  This might be an known limitation, by default, the report will show the filtered records in the parent table, and all the related records of them in the related tables.  You could use a where filter in your report template to filter the record in the related table, here is the syntax: ${#layername | where: } ... ${/} Please let me know if this is not the case. Thanks, Ruth ... View more

Hi @RafaelCelaya @Anonymous User @FredMitchell  The fix for this issue is now available on the production website, if it is possible please help us verify the fix, and let us know if you have any question. Thanks, Ruth ... View more