Latest Contributions by Shwu-jingJeng

Hi Chiara, This issue usually occurs when the using an older Connect version to publish the survey and use new version of web app(survey123.arcgis.com>Settings>Versions) to render the survey form. The problem would solve if you use Connect 3.12 version to republish and use 3.12 version of web app to render the survey. Could you please try to sync the version of Connect(3.12) to republish the survey and make sure the Settings is also set to the same version (3.12)? ... View more

Hi Chiara, Did you use the production version of 3.12 Connect to republish the form and still see the UI issue? Have you also tried our latest beta build (3.13.127 Connect) to republish the survey? Could you share your XLSForm here to see if you have other settings for this table-list group? ... View more

Hi Swathilyengar, I was able to reproduce your issue and this issue seems to start with 3.12 version and when you switch from english to a right to left language. I had entered an internal issue for this and also encourage you to submit this issue as a bug via Esri Support. Our Support team will assign an official bug number for your records. This number can be used to search for and subscribe to the bug on the Esri Support site. If the issue is reported by other customers it will be attached to the same bug report, which helps us assess the impact of the issue and prioritize it accordingly. ... View more

Hi Swathilyengar,   Could you provide more information regarding the multiline text input for Farsi language? 1. Did the issue occur only on Android phone with the Farsi input? What model of the Android phone is used? 2. What version of Connect did you use to piublish this survey? Did you have problem to type Farsi in Connecy and field app on Windows or on the web form? 3. Did the same multiline text input work on iOS device?   ... View more

Hi Chiara, What version of Connect did you use top publish this form? Could you check the Settings tab from survey123 website for this survey and check if 3.12 is used for web app?   ... View more

Hi Michael, In Michelle's case, we had helpped her with some report template syntax error to close this issue. What issue did you encounter?   ... View more

Hi Ahmad, Your web form issue is related to “using relevant on a repeat” (If I remove all relevant for all repeats, it works fine). We do have an internal issue for this logged and planned to be fixed in 3.14. If you would like to track the fix status, I would recommend to log an Esri support salesforce issue for this and we will link to the current internal issue so that you can track the fix status. ... View more

Hi Antonio, I was not able to rerpoduce the issue even with pdf file and I also used 3.12 Connect to publish the survey. Is it possible you can share yout XLSForm with me to test it in house? If you prefer not to share publicly, you can email it to me ([email protected]). ... View more

Hi Ahmad, You are missing the file name type for the village.csv in your XLSForm and also missed the language code in the choice tab. Please try this XLSForm and it should work with current 3.12 production build.   ... View more

Hi Antonio, What version of the survey is published with? Is it published from Connect or create from web designer? When you change your AGOL account language, did you see all UIs on the survey123 website display Italian correctly? Did you export the feature report to pdf or word doc? If you could provide me more details of the information I asked above, that could help me to narrow down your issue. ... View more

Hi Antonio, Could you explain more about your isssue? The report content will print the langauge based on the ArcGIS acccount profile language. For example, my AGOL account language is set to Japanese and my survey does have a Japanese version. When I log on to survey website and print the report, the report will be printed as Japanese. Is this what you are asking?   ... View more

Hi William, The earliest time frame would be before the UC but it still depends on the actual implemetation. Currently you could check the status of this issue by referencing this enhancement request: ENH-000135167 Enable javascript function on public surveys. Use the Survey123 pulldata from an existing feature service option for public surveys. We will announce the fix on our EAC when it becomes available for beta testing. Please keep eyes on our updates posted on EAC. Thanks, ... View more

Hi Mayra, Thanks for the xlsForm. By looking at the form, you are using the javascripts with the reversed geocoding service. I was able to see the problem when the survey is made to public. If it's private, the reversed goecoding service would work on an android phone web browser. Could you confirm that you see this problem on an android device and with a public survey? We do have issue with javascript in public survey and currently is scheduled to be implemented in the next release. Before the release, you could access to the beta version from our EAC site to test the fix. Please confirm if you had met the following scenarios: 1. Using the web browser on android. 2. Survey is public.  ... View more