<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>idea Save Layout As… with Dependent Maps (Preserve Historical Fidelity) in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/save-layout-as-with-dependent-maps-preserve/idi-p/1694631</link>
    <description>&lt;DIV&gt;&lt;P&gt;ArcGIS Pro needs a layout‑level &lt;STRONG&gt;“Save As… (Include Dependent Maps)”&lt;/STRONG&gt; capability that duplicates a layout &lt;STRONG&gt;and automatically creates renamed copies of all maps referenced by that layout&lt;/STRONG&gt;, updating the &lt;EM&gt;new&lt;/EM&gt; layout’s map frames to point to the duplicated maps while leaving the original layout and maps untouched.&lt;/P&gt;&lt;P&gt;In consulting, engineering, and regulatory workflows, layouts are &lt;STRONG&gt;historical records&lt;/STRONG&gt;, not just dynamic views. When a layout has been issued (PDF/JPG), future users must be able to reopen it and see &lt;STRONG&gt;exactly what was delivered&lt;/STRONG&gt;, without reinterpretation or regeneration.&lt;/P&gt;&lt;P&gt;Currently in ArcGIS Pro:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Layouts reference maps by identity.&lt;/LI&gt;&lt;LI&gt;Changing a map frame’s source map triggers a &lt;STRONG&gt;full legend rebuild&lt;/STRONG&gt;, disregarding user‑authored legend state such as:&lt;UL&gt;&lt;LI&gt;Heading visibility&lt;/LI&gt;&lt;LI&gt;Removed legend items&lt;/LI&gt;&lt;LI&gt;Custom ordering&lt;/LI&gt;&lt;LI&gt;Item‑level visibility choices&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;Legend locking and “Match New Layer” settings do not prevent this behavior.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;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.&lt;/P&gt;&lt;H3&gt;Requested behavior&lt;/H3&gt;&lt;P&gt;Add a layout‑level operation similar to &lt;STRONG&gt;Save As&lt;/STRONG&gt;, with an option such as:&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;&lt;STRONG&gt;“Save Layout As… (Include Dependent Maps)”&lt;/STRONG&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;When selected, ArcGIS Pro would:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Duplicate the selected layout&lt;/LI&gt;&lt;LI&gt;Identify all maps referenced by its map frames&lt;/LI&gt;&lt;LI&gt;Create duplicated copies of those maps&lt;/LI&gt;&lt;LI&gt;Optionally auto‑rename the duplicated maps (date/version suffix)&lt;/LI&gt;&lt;LI&gt;Repoint the &lt;EM&gt;new&lt;/EM&gt; layout’s map frames to the duplicated maps&lt;/LI&gt;&lt;LI&gt;Leave the original layout and maps completely unchanged&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;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.&lt;/P&gt;&lt;H3&gt;Benefits&lt;/H3&gt;&lt;UL&gt;&lt;LI&gt;Preserves historical fidelity without flattening layouts to graphics&lt;/LI&gt;&lt;LI&gt;Prevents accidental legend and map series rebuilds&lt;/LI&gt;&lt;LI&gt;Provides a safe, intentional workflow for issued deliverables&lt;/LI&gt;&lt;LI&gt;Aligns ArcGIS Pro with standard document‑control expectations&lt;/LI&gt;&lt;LI&gt;Reduces risk for long‑running consulting and regulatory projects&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;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.&lt;/P&gt;&lt;/DIV&gt;</description>
    <pubDate>Mon, 06 Apr 2026 19:02:19 GMT</pubDate>
    <dc:creator>SteveIrving</dc:creator>
    <dc:date>2026-04-06T19:02:19Z</dc:date>
    <item>
      <title>Save Layout As… with Dependent Maps (Preserve Historical Fidelity)</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/save-layout-as-with-dependent-maps-preserve/idi-p/1694631</link>
      <description>&lt;DIV&gt;&lt;P&gt;ArcGIS Pro needs a layout‑level &lt;STRONG&gt;“Save As… (Include Dependent Maps)”&lt;/STRONG&gt; capability that duplicates a layout &lt;STRONG&gt;and automatically creates renamed copies of all maps referenced by that layout&lt;/STRONG&gt;, updating the &lt;EM&gt;new&lt;/EM&gt; layout’s map frames to point to the duplicated maps while leaving the original layout and maps untouched.&lt;/P&gt;&lt;P&gt;In consulting, engineering, and regulatory workflows, layouts are &lt;STRONG&gt;historical records&lt;/STRONG&gt;, not just dynamic views. When a layout has been issued (PDF/JPG), future users must be able to reopen it and see &lt;STRONG&gt;exactly what was delivered&lt;/STRONG&gt;, without reinterpretation or regeneration.&lt;/P&gt;&lt;P&gt;Currently in ArcGIS Pro:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Layouts reference maps by identity.&lt;/LI&gt;&lt;LI&gt;Changing a map frame’s source map triggers a &lt;STRONG&gt;full legend rebuild&lt;/STRONG&gt;, disregarding user‑authored legend state such as:&lt;UL&gt;&lt;LI&gt;Heading visibility&lt;/LI&gt;&lt;LI&gt;Removed legend items&lt;/LI&gt;&lt;LI&gt;Custom ordering&lt;/LI&gt;&lt;LI&gt;Item‑level visibility choices&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;Legend locking and “Match New Layer” settings do not prevent this behavior.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;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.&lt;/P&gt;&lt;H3&gt;Requested behavior&lt;/H3&gt;&lt;P&gt;Add a layout‑level operation similar to &lt;STRONG&gt;Save As&lt;/STRONG&gt;, with an option such as:&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;&lt;STRONG&gt;“Save Layout As… (Include Dependent Maps)”&lt;/STRONG&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;When selected, ArcGIS Pro would:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Duplicate the selected layout&lt;/LI&gt;&lt;LI&gt;Identify all maps referenced by its map frames&lt;/LI&gt;&lt;LI&gt;Create duplicated copies of those maps&lt;/LI&gt;&lt;LI&gt;Optionally auto‑rename the duplicated maps (date/version suffix)&lt;/LI&gt;&lt;LI&gt;Repoint the &lt;EM&gt;new&lt;/EM&gt; layout’s map frames to the duplicated maps&lt;/LI&gt;&lt;LI&gt;Leave the original layout and maps completely unchanged&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;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.&lt;/P&gt;&lt;H3&gt;Benefits&lt;/H3&gt;&lt;UL&gt;&lt;LI&gt;Preserves historical fidelity without flattening layouts to graphics&lt;/LI&gt;&lt;LI&gt;Prevents accidental legend and map series rebuilds&lt;/LI&gt;&lt;LI&gt;Provides a safe, intentional workflow for issued deliverables&lt;/LI&gt;&lt;LI&gt;Aligns ArcGIS Pro with standard document‑control expectations&lt;/LI&gt;&lt;LI&gt;Reduces risk for long‑running consulting and regulatory projects&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;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.&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 06 Apr 2026 19:02:19 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/save-layout-as-with-dependent-maps-preserve/idi-p/1694631</guid>
      <dc:creator>SteveIrving</dc:creator>
      <dc:date>2026-04-06T19:02:19Z</dc:date>
    </item>
  </channel>
</rss>

