Hi everyone,
I’d like to check whether the following behavior is an expected limitation or if there is a recommended approach to handle this use case. Our client has built a disaster monitoring dashboard for Sumatra. Field teams update the data directly in the dashboard, and the situation must be officially reported to PUPR twice a day. Many C-level stakeholders review this information through PDF reports, so PDF output is a hard requirement.
To avoid double work and maintaining separate reporting assets, we proposed using ArcGIS StoryMaps as the reporting layer, embedding the existing dashboard so that:
the dashboard remains the single source of truth, and
the PDF report reflects the same content without creating a separate report design.
Issue:
When the dashboard is embedded directly into a StoryMap and exported to PDF:
the content is automatically scaled down in Print Preview,
the embedded dashboard no longer respects its original layout,
widgets shrink and overlap,
and the resulting PDF becomes difficult to read for executive stakeholders.
We have already tried:
simplifying and restructuring the dashboard layout,
testing different StoryMaps width presets (Wide / Full),
splitting dashboards into smaller sections,
but the PDF export behavior remains the same.
Question:
Is there any way to:
control how an embedded dashboard is rendered during StoryMaps PDF export, or
preserve the same size and structure as the original dashboard view in the PDF?
Or is this behavior an inherent limitation of StoryMaps PDF export by design when embedding dashboards?
Any clarification, best practices, or official guidance would be greatly appreciated, as this impacts operational reporting workflows.
Thanks in advance.
