We are are looking at implementing a reporting service in ArcGIS Server (11.5) that can be used through the Experience Builder Print Widget.
We've configured this as a report, as per the customer's requirements, with 4 sections in Pro as follows:
1) A details section to include a few basic attributes (approx 6) of a selected site polygon.
2) A details section to include summary attributes (approx 7) from each selected tree survey (point) feature in a tabular format.
3) A details section to include detailed attributes (approx 10) from each selected tree survey (point) feature in a paged format (i.e. 1 feature per page)
4) A details section to include attachments from each selected tree survey (point) feature in a paged format (1 feature per page.
This report has been published as a print/report service using pro that also includes a basic A4 landscape map template. We've then configured the print widget in Experience Builder to use this service and set it to use the selected features for the relevant layer in each section of the report.
This is all working as expected (except when there are no features selected - but that is a different issue!) and producing a report. However, it is taking approximately 60 seconds to print the full report, including the map. This seems pretty poor performance considering that in our tests we have been using 1 selected site polygon and 3 selected tree survey features.
Doing a few more detailed tests by removing the map and sections in turn, we have found that:
- The map is taking approx 22 seconds.
- The attachments section is taking approx 5 seconds.
- The detailed (paged) tree survey attributes section is taking 14 seconds.
- The summary (tabular) tree survey attributes section is taking approx 6 seconds
- The single details section for the site polygon is taking approx 14 seconds.
Again, the above is for 1 site polygon (with approx 6 attributes) and 3 tree survey features (with approx 7 attributes), so the data quantity feeding into the report is minimal. The data for the report is also sent in the print request (in the web_map_as_json parameter) so the reporting service is not having to query any data, just present it by injecting it into the report template.
So why is it taking so long to generate a pretty basic report?
