Select to view content in your preferred language

Save Layout As… with Dependent Maps (Preserve Historical Fidelity)

114
0
4 weeks ago
Status: Open
Labels (1)
SteveIrving
Occasional Contributor

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:

  • Layouts reference maps by identity.
  • Changing a map frame’s source map triggers a full legend rebuild, disregarding user‑authored legend state such as:
    • Heading visibility
    • Removed legend items
    • Custom ordering
    • Item‑level visibility choices
  • Legend locking and “Match New Layer” settings do not prevent this behavior.

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.

Requested behavior

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:

  1. Duplicate the selected layout
  2. Identify all maps referenced by its map frames
  3. Create duplicated copies of those maps
  4. Optionally auto‑rename the duplicated maps (date/version suffix)
  5. Repoint the new layout’s map frames to the duplicated maps
  6. Leave the original layout and maps completely unchanged

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.

Benefits

  • Preserves historical fidelity without flattening layouts to graphics
  • Prevents accidental legend and map series rebuilds
  • Provides a safe, intentional workflow for issued deliverables
  • Aligns ArcGIS Pro with standard document‑control expectations
  • Reduces risk for long‑running consulting and regulatory projects

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.