Community
Select to view content in your preferred language

Conditional Report-Templates for Custom Print Service

299
0
3 weeks ago
Status: Open
Labels (1)
DJColeman
by
Emerging Contributor

Idea: Currently, Report Templates for use in custom print services are "hardcoded", meaning when the Report is exported as a .rptx file, when printing with said template the pages that appear in your output are inflexible. I would like to be able to use .rptx files (or a variant) that can add or remove subreports depending on the data present at time of print.

An example mockup of this:

  1. We are working with datasets that contain an unpredictable number of features. When printing in Experience Builder using a custom print widget, certain subreports/Details pages will always be dedicated to a single type of feature. And if there is more than one of those features then our need is for the report to conditionally repeat the presence of those subreports/Details pages for reuse until every single feature of that type (query) has been returned. And these need to repeat sequentially. The issue currently is, in part, that Report Template formats are hardcoded, and therefore are not functional in the dynamic way we need (i.e., a ten-subreport template is no use if the features in a query would add up to need 20 subreports).

    I have included sample images to better explain:
    1. Page one of the sample-report shows the Layout Template.

       

    2. Page two of the example report shows the Population Impacts, Buildings, Households, Open Shelters, National Status, Region, State EOC Status, and Geographic Area which come from the polygon containing the fires. However, it then goes on to include values from the first fire (“Indios”), which contain everything after the fire’s name all the way until the end of page 4.

       

       

       

    3. At the end of Page 4, we can see the contents seen for the “Indios” fire repeat for the “Hackberry Canyon” fire. And since this is the final fire in the polygon, the report ends on page 5, below.

       



      And as there can be untold number of fires within a polygon, you can see the current .rptx creation functionality in ArcGIS Pro for use in the Print Widget of Experience Builder will not work for us without the ability to conditionally add and repeat subreports—as seen above with the Indios and Hackberry Canyon fires—because the .rptx creation structure requires hardcoded subreports which are anticipatable at the time of print.

0 Kudos