topic Re: Survey123 Report: Page Break for Repeat Feature in ArcGIS Survey123 Questions

Survey123 Report: Page Break for Repeat Feature

Anonymous User — Thu, 01 Jul 2021 19:22:30 GMT

I am trying to create a report that displays each new repeat feature to a new page. I read some older posts that this is possible by adding index (=repeat count) to the survey. (Link: https://community.esri.com/t5/arcgis-survey123-questions/survey123-feature-reporting-insert-page-break/m-p/872656)

I did not add the repeat count to the survey and the data collection has been completed already. Is there any way to achieve this (page break for each new repeat feature) without the repeat count? That post is only a few months old but wanted to check if someone figured out new ways to handle it.

Re: Survey123 Report: Page Break for Repeat Feature

Ruth_JiatengXu — Mon, 05 Jul 2021 08:09:37 GMT

Hi @Anonymous User

You can use the ${$feature | getValue: "position"} as the repeat count. Here is the explanation of getValue:"position" in the doc:

To display the index of a repeat record, use the getValue expression with the reserved keyword $feature. This example will produce 1 for the first record in a repeat, 2 for the second, and so on:
${#defects}
${$feature | getValue: "position"}
${/}

So you can use this expression in your template to insert page break before each repeat except for the first repeat.

If you need, you can also use ${repeat1 | getValue:"count"} to return the number of instance of repeat1.

Thanks,

Ruth

Re: Survey123 Report: Page Break for Repeat Feature

Anonymous User — Tue, 06 Jul 2021 14:38:33 GMT

Ruth,

This worked beautifully - I appreciate your help! Somehow the if statement persisted on printing "true" but I wasn't sure how to hide it so I ended up styling the statement in white font.

Re: Survey123 Report: Page Break for Repeat Feature

Ruth_JiatengXu — Wed, 07 Jul 2021 06:03:47 GMT

Hi @Anonymous User ,

If you need help to remove the "true" from your report, you can share your report template here.

Thanks,

Ruth

Re: Survey123 Report: Page Break for Repeat Feature

Anonymous User — Wed, 07 Jul 2021 15:54:24 GMT

Hi @Ruth_JiatengXu - I'm attaching the report template here. I've stripped off the content from the parent feature, but the page #2 is where the repeat questions display. Then the page #3 shows some more questions from the parent feature. From your screenshot, it seemed I needed an additional closing tag. But once I added it, it skipped showing the first repeat question altogether so I resorted back to using white font. Attached template outputs something like this:

Re: Survey123 Report: Page Break for Repeat Feature

Ruth_JiatengXu — Thu, 08 Jul 2021 06:09:41 GMT

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

Re: Survey123 Report: Page Break for Repeat Feature

Anonymous User — Thu, 08 Jul 2021 14:15:59 GMT

Thank you for the detailed guidance, @Ruth_JiatengXu !

Re: Survey123 Report: Page Break for Repeat Feature

ZachBodenner — Fri, 10 May 2024 15:57:44 GMT

I'm also having some trouble with this and I'm wondering if anyone here could help out:

I have a report that I want to print out only repeat data with a new page for each entry.

It starts with:${#repeat name}${if ($feature | getValue: “position”)!=1}, then has some MS Word tables with fields from the repeat, and ends with ${/}${/}

I feel like that should be working but I keep getting errors like Error: An error occurred when checking the report template. The tag beginning with "}$repeatEn" is unopened. The start tag ${# UASPreFlightChecklist} is unclosed.

Re: Survey123 Report: Page Break for Repeat Feature

JJ_Reyes — Tue, 17 Dec 2024 14:57:15 GMT

@Ruth_JiatengXu - would there be a way to get the LAST position, without having a repeat count in the form?

Re: Survey123 Report: Page Break for Repeat Feature

Ruth_JiatengXu — Wed, 18 Dec 2024 08:40:10 GMT

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

Re: Survey123 Report: Page Break for Repeat Feature

Ruth_JiatengXu — Wed, 18 Dec 2024 08:45:42 GMT

Hi @ZachBodenner ,

I am sorry for the late response. The close tag in your template might be the cause of this issue.

Thanks,

Ruth

Re: Survey123 Report: Page Break for Repeat Feature

JJ_Reyes — Wed, 18 Dec 2024 13:41:13 GMT

Ah sorry @Ruth_JiatengXu - I wasn't clear. It's more like trying to find the last repeat so a final separator doesn't display. If the code was something like this:

${#repeat1}

${field1InRepeat1} <page break>

${/}

I'm looking to identify the last repeat so it does not have an extra page break at the end of the document.

Re: Survey123 Report: Page Break for Repeat Feature

Ruth_JiatengXu — Thu, 19 Dec 2024 12:20:02 GMT

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

Re: Survey123 Report: Page Break for Repeat Feature

JJ_Reyes — Thu, 19 Dec 2024 14:57:35 GMT

This works great - thanks! I was able to add my own parameters instead of $inputParams as well.