ArcGIS Pro needs a layout‑level “Save As… (Include Dependent Maps)” capability that duplicates a layout and automatically creates renamed copies of all maps referenced by that layout, updating the new layout’s map frames to point to the duplicated maps while leaving the original layout and maps untouched.
In consulting, engineering, and regulatory workflows, layouts are historical records, not just dynamic views. When a layout has been issued (PDF/JPG), future users must be able to reopen it and see exactly what was delivered, without reinterpretation or regeneration.
Currently in ArcGIS Pro:
As a result, users are forced to rely on fragile workflows (map renaming conventions, strict user discipline, or converting legends to graphics) to preserve historical fidelity. One accidental map reassignment can permanently alter a previously issued layout.
Add a layout‑level operation similar to Save As, with an option such as:
“Save Layout As… (Include Dependent Maps)”
When selected, ArcGIS Pro would:
This produces a clean, self‑contained snapshot of the layout and its data sources, eliminating the need for repointing later and preventing destructive legend regeneration.
ArcGIS Pro already has the required architecture (stable map identities, layout‑map relationships, object duplication). This enhancement would simply orchestrate those capabilities into a safe, first‑class workflow.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.