nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Report Template Duplicating Report Based on Number of Selected Records

TeresaMarquez

Hello,

I am experiencing a duplication issue in my report template. For instance, using the merge (continuous) file option, the generated file will contain the report duplicated 5 times if I select 5 records to be displayed. I believe it has to do with the #SWPPP_Collection call at the top of the table. (SWPPP_Collection is the parent table & Ongoing_Repeat is the related table)

The goal is for the template to produce a seamless table containing all records indicated by the contingencies listed after #SWPPP_Collection, as seen in the screenshot below.

Any advice would be greatly appreciated.

Finde mehr Beiträge mit dem Tag

Accepted answers

TeresaMarquez

Although we were unable to find a solution via Word, we realized we could create a survey report template right in Arc Pro. This method is much more efficient & less dreadful to work with compared to Microsoft Word.

All comments

TylerGraham2

Is there a reason you're calling the parent table SWPPP_Collection as a repeat table? If your survey and report template are pointing to the SWPPP_Collection table as the parent and then you call it as a repeat, I think that would explain why your report is duplicating itself.

Drop the entire ${#SWPPP_Collection} line and the last ${/} and see what happens.

TeresaMarquez

Unfortunately I have tried that. When I keep the same file option (merge (continuous)), the following happens.

When I choose merge (next page), the report is not duplicated or stacked but I get one box per page & there is no way that I can figure out to filter for the necessary records. The goal is to have a seamless chart containing all specified records which is why I called on the parent table like I did, so I can dictate which records would show up in the report.

Please let me know if you have an alternative action to achieve this goal. I tried keeping the same line but removing the # & got the same results as when I removed the line completely.

TylerGraham2

I tried to get it to replicate with a dataset of mine calling the Parent layer and Child layer in a table and I couldn't get it to happen. However, I didn't have any if statements in my table or queries and other filters on the layers.

The only other idea I have is, if you haven't tried it already, to create a new template, so you don't lose your existing work. Then start simple with just calling the tables and their fields with no if statements, queries, or filters. Test to see the output, and if it does work gradually start adding to it, test each addition until you find (hopefully) the cause.

TeresaMarquez

I have unfortunately already tried that idea as well 😢 The only time the report duplicates is when I call the parent table as I did. The report generates exactly as I need it to minus the duplication.

The hurdles I'm facing are between figuring out a way to implement my current method of calling the parent table but without the duplicating, or finding another way to get the template to filter the parent table data before calling on the related table.

Thank you very much for responding to my post, I greatly appreciate it. You helped me nail down that my calling of the parent table as a repeat is the probable cause of the issue I'm facing.

TeresaMarquez

Nimm an der Diskussion teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.