Latest Contributions by Ruth_JiatengXu

Hi @NurbekGabdullin @Alex_at_Exprodat , The fix is bow available on the production environment. Thanks, Ruth ... View more

Hi @NurbekGabdullin @Alex_at_Exprodat , Thanks for sharing here! The issue has been fixed on BETA (https://survey123beta.arcgis.com/). If possible please help verify the fix. Fell free to let me know if you have any questions. Thanks, Ruth ... View more

Hi @JulietK , Sorry Juliet, I missed your post. N is the character for letters and digits, however, I found there is an issue with the case controller > and N, I have logged an internal issue to fix it. You can use >XXXX as a workaround. I will reply to this post once we fix the issue with > and N. Thanks, Ruth ... View more

Hi @ahargreaves_FW , It is not possible to apply conditions to the input mask. However, you can create two text questions Q2 Q3 with different input mask and let them relevant to your Q1. Add another text question Q4 to gather result from Q2 and Q3. Set Q2 and Q3 to "do not submit answer", then the redundant value will not be submitted. Thanks, Ruth ... View more

Hi @PeterMadirazza , I am wondering have you republish the survey using the latest 3.16 Connect? You can check the form version in the developer tools (press F12 to open) -> console -> survey published. I guess this survey was published in connect, then republished in website, then republished again in the latest Connect. If yes, then the cause of the issue is that we improved the mechanism of encoding/decoding in 3.16 to ensure some encoded content will not be decoded accidentally. If this is the case, republish your survey in the website will fix the issue. You can save your current form as a new form to test the solution I mentioned. Then, republished your current form if the solution I mentioned can work without issue. If you haven't republished your survey using the latest 3.16 Connect, could you please let me know the publishing version and the rendering version of your survey? The .info file inside your survey folder would be really helpful. I can then help you investigate further. Thanks, Ruth ... View more

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