Latest Contributions by Ruth_JiatengXu

Hi @Anonymous User  I modified your template, and it should work now. Few things to notice: 1. The following expression inserts a page break before each repeat, except for the first repeat instance. If you put the table between ${if ...} ${/}, then the table will not be printed for the first repeat instance. ${if ($feature|getValue:”position”)!=1} page break ${/}Observation 2. The ${if ...} ${/} needs the closing tab ${/} to work, and a space is needed between if and the expression. 3. If you only want to output the instance number without the if statement, you can simply use ${$feature | getValue: "position"}. Thanks, Ruth ... View more

Hi @DarraghOSullivan , The issue you encountered is the performance issue of the report service, and generating report for the record with many repeat, maps, photos is the bottleneck of the current report service. We are working on refactoring the service to improve the performance of the report service, so other than BUG-000129586, we also handle BUG-000140099, BUG-000136451 (10 min limit issue), BUG-000138738. Thanks, Ruth ... View more

Hi @DarraghOSullivan , You are encountering the existing salesforce issue: BUG-000129586 generating the feature report fails when the records have a large number of photo-enabled related records. We are working on this issue right now, and the fix will be available in the next release. We will reply to this post once the fix is available for testing. Thanks, Ruth ... View more

Hi @Anonymous User , If you need help to remove the "true" from your report, you can share your report template here. Thanks, Ruth ... View more

Hi @dnykodym  Thanks for sharing here. The repeat instances within one record cannot be split into multiple reports, however, you can create another survey from the existing repeat layer, then each repeat instance can be handled as a record.  Here is the steps: 1. Open connect -> + New survey -> Feature service, select the feature service 2. Go to settings tab -> fill the name of your repeat table in the form_id field 3. Go to survey tab -> delete all fields outside the repeat  4. Publish the survey, and you will have the survey with every repeat instance as a record. Thanks, Ruth ... View more

Hi @Polesig  Thanks for sharing here! The report service does not support adding analyze graphics/charts. If you have a feature idea for Survey123 that needs fleshing out or you think will gain support from others please add it to https://community.esri.com/community/arcgis-ideas/content?filterID=contentstatus%5Bpublished%5D%7Ecategory%5Barcgis-survey123%5D Thanks, Ruth   ... View more

Hi @FrancisCorbett , Thanks for sharing here! The web builder does not support changing submission URL, but the web builder already creates views of the original published feature service to protect your data. When you publish a survey from web builder, the web builder automatically creates 2 views, surveyName_fieldworker view is used to collect the result, and the surveyName_stakeholder view is used to shared to result. You can see this blog post for more information: Securing data in public surveys (Survey123 web designer) . If the current fieldworker and stakeholder views cannot satisfy the needs, please share more details relates to your use case. Thanks, Ruth ... View more

Hi @Anonymous User  Thanks for sharing here. The ${geopoint | getValue: “x|y”} currently can only return the lat/long with 5 decimal places, and you cannot get more significant digits. However, there is one expression can pad zeros to the output number, if you use ${geopoint | getValue: “x|y” | toFixed:8} you will get the lat/long with 8 decimal places (5 significant decimal digits + 3 zeros). We have discussed your use case with the team, and in the future release we will make the ${geopoint | getValue: “x|y”} to return original lat/long, and then you can use round or toFixed expression to format the output lat/long. I will reply to this post once the change is available for testing. Thanks, Ruth ... View more

Hi @RobertAnderson3 , Sorry for the late response, and thank you for sharing here! Since the last Survey123 3.12 release, the Survey123 form content will be displayed in the language which has higher priority (URL lang parameter > user profile language > organization profile language > browser language > default language). Then, the survey taker will have the form displayed in their preferred language automatically. For your survey, even the default language is set to French, if your profile or org, or browser language is set to English, the form content will still be displayed in English. As you mentioned, the URL param lang can be used to force the form displayed in specified language, you can use the embed widget to include the URL param. I am working on the BUG-000138161 you raised, could you please double check your profile, org, browser language settings and let me know if the web app work as expected or not? Thanks, Ruth ... View more

Hi @ElizabethHovsepian  Sorry for the late response, and thanks for sharing the issue here. The appearance of the checkbox is actually determined by the operation system and the output format.  Therefore, if you generate report in pdf format, the checkboxes will have the same size. I will log the issue you encounter and I will reply to this post if the issue is fixed. I also encourage you to contact 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. Thanks, Ruth ... View more

Hi @PatrickHassett  The error is returned by the encodeUrlParams REST API, and the request is sent to portal to verify the token. Could you please provide more info relates to the portal?  For example, what is the authentication method used by the portal (IWA/SAML/Built-in)? Can it be accessed from external network? Thanks, Ruth  ... View more

Hi @MarissaReed  Thanks for the sample survey, the issue you mentioned is an known issue, we will reply to this post once the issue is fixed. Here is a workaround for this issue, change the relevant of the hotline_calls to:     ${field_coordinatorlead_jobs}='Hot_Line_Calls' and ${field_coordinatorlead_}='Yes'     Then, this Hotline Calls question will only appear when Field Coordinator/Lead: Yes and Jobs: Hotline Calls. Thanks, Ruth ... View more

Hi @JerryEnoe  Apologies for the delay. If it is possible could you please share your report template here so that we can reproduce the issue? Thanks, Ruth ... View more

Hi @Tim-Woodfield  Apologies for the delay. If it is possible could you please share your report template here so that we can reproduce the issue? Thanks, Ruth ... View more