Latest Contributions by Ruth_JiatengXu

Hi @AirX , Sorry for the late reply. It is possible to dynamically add pages. Before the open tag ${#individual_entry} and close tag ${/} is the content that will be repeated for each entry. So you can use: ${#individual_entry} Use field within repeat: ${dot1} Use field outside repeat: ${$layers[0].pavethick} page break ${/}   The generated report will look like this: ---On the page 1--- Value of dot1 in the 1st repeat instance Value of pavethick ---On the page 2--- Value of dot1 in the 2nd repeat instance Value of pavethick ---On the page n--- Value of dot1 in the nth repeat instance Value of pavethick   Currently, you placed ${individual_entry} and ${/} in the same table cell, so the content between these tags will be repeated within this table cell only. The best practice is to use the open and close tag to wrap the entire section that you want to repeat for each entry. In my pervious reply, although I didn't produce the result your expected, you can still reference it to update your template. This is the template:   This is the generated report with 2 individual entries:   Thanks, Ruth ... View more

Hi @ZhujingXia , We are working on this feature right now. I encourage you to raise an Enhancement case to 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 @AirX , I have checked with our developer if multiple ${imageQ} are written continuously, we may not be able to extract the template tags correctly. To fix the image exporting issue, please split multiple ${imageQ} with spaces or line breaks. Or you can use different font styles for them like the screenshot below: I am not quite sure about "all the individual entries are being exported together on the same page entry". I guess you may want to repeat the highlighted section for each individual entry and I have included a modified template and an exported report for your reference. If this is not the case, please let me know what is your expected output. Thanks, Ruth   ... View more

Hi @AirX , When no image exists, the syntax ${qname|getValue:""|size:420:0} raises an error. You can use ${if qname}${qname|getValue:""|size:420:0}${/} to pass an empty image question. Please check the updated template "images.docx". The repeat syntax can also be used to repeat an entire section, in case you want to repeat the middle part of your template for each individual entry. I include another template "repeat.docx" for your reference. Thanks, Ruth ... View more

Hi @AirX  You need to remove the ${/} mentioned in point 2. Please check the template I modified. Thanks, Ruth ... View more

Hi @AirX , I have checked your template, please try making the following changes to your template: In the "Utility Owner" cell, the ${#individual_entry} tag is not closed. Therefore, the report service considered the content afterward still within the repeat.  There is an extra close tag here   With the updated template, you will generate a report like this: Thanks, Ruth cc @Jim-Moore  ... View more

Hi @Teresa_Blader , When you open a survey with mode=view, the web app will be looking for a feature service with both of these 2 typekeywords: StakeholderView {Survey item id} When your survey points to a submission URL, the Collaborate page cannot create the feature service mentioned above. However, you can create this feature service manually: Create a view layer for your submission layer   Add these 2 typekeywords to your newly created view: StakeholderView {Survey item id} Note: this is the survey you are using with the mode=view This tool can be used to update typekeywords: https://ago-assistant.esri.com/ Let me know if you have further questions. Thanks, Ruth ... View more

Hi @JJ_Reyes , Thanks for the information, you could use the following syntax. ${#repeat1} ${field1InRepeat1} ${if ($feature| getValue:"position")!=( r1 | where:"$inputParams !important" | stats:"count,objectid")}  <page break>${/} ${/} Add the page break when the position is not equal to repeat instance count. Use ( r1 | where:"$inputParams !important" | stats:"count,objectid") to get repeat count inside ${#repeat1}${/}.  Thanks, Ruth ... View more

Hi @JulietK @AndrewPadilla @HaroldHerrera1  The issue has been fixed. Please let us know if you have further questions. Thanks, Ruth ... View more

Hi @ZachBodenner , I am sorry for the late response. The close tag in your template might be the cause of this issue. Thanks, Ruth ... View more

Hi @JJ_Reyes , I am not sure if I understand your question correctly or not. If you want to show the last repeat instance in the repeat, you don't need to have a repeat count in the form. You can use the following in the repeat template:   ${#repeat1 | resultRecordCount:1 | orderByFields:"objectid DESC"} ${field1InRepeat1} ${/}   Thanks, Ruth ... View more

Hi @SayenaMarandi , To record the geometry in your survey feature layer, you need to set the connection from `StarMap_Street` polyline to Survey's polyline geometry. To achieve this, you may need to create a new survey and add a map question with the line type, then add the polyline geometry connection in the Experience Builder. As you mentioned, your survey feature layer has the point geometry type, and I think maybe you don't set the geometry connection between the web app and the survey widget. Therefore, the default value geopoint 0.0 is added for all the records you submitted to the survey feature layer. Please let me know if you have further questions. Thanks, Ruth   ... View more

Hi @SCB, The issue mentioned in https://community.esri.com/t5/arcgis-experience-builder-questions/feature-report-widget-won-t-allow-mobile-worker-to/m-p/1513225/highlight/true#M13995 has already been fixed and it should work just like Survey123 website.  Please let me know if you have further questions. Thanks, Ruth ... View more

Hi @CFECAK , Thanks for sharing your question here. Have you tired the method=camera in the body::esri:style column? Here is what an XLSForm looks like if you want to force users to submit a new photo from the camera: type name label body::esri:style geopoint location Location   image image Photo method=camera Thanks, Ruth ... View more

Hi @Daniel_Perkins , Thanks for the information, we are currently working on the related support issue: https://support.esri.com/en-us/bug/polygons-with-holes-do-not-have-the-correct-shape-sent-bug-000155234. You could follow the development status using the link. We will also reply to this post when the fix is available for testing.  Thanks, Ruth ... View more