<?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>topic Re: Using Append_management for all versions in Python Questions</title>
    <link>https://community.esri.com/t5/python-questions/using-append-management-for-all-versions/m-p/307263#M23915</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Finally, I figured out the correct workflow for this. I had to change to the child version (ChangeVersion_management) before appending. Then I can propagate the changes from children to parents and grandparent. This is the only way reconciliation works.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 24 Jul 2018 21:12:19 GMT</pubDate>
    <dc:creator>NaciDilekli</dc:creator>
    <dc:date>2018-07-24T21:12:19Z</dc:date>
    <item>
      <title>Using Append_management for all versions</title>
      <link>https://community.esri.com/t5/python-questions/using-append-management-for-all-versions/m-p/307260#M23912</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a rather complicated enterprise geodatabase version scheme that looks like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="Multiple projects with subprojects" src="http://desktop.arcgis.com/en/arcmap/10.3/manage-data/geodatabases/GUID-9A9F943D-57A3-4D1D-AF24-AAC2470F2A40-web.gif" /&gt;&lt;/P&gt;&lt;P&gt;Periodically I get updates to our data inventory, and I would like to update all the versions together. I tried the append_management command as follows:&lt;/P&gt;&lt;PRE class="lia-code-sample line-numbers language-none"&gt;&lt;CODE&gt;&lt;SPAN class="comment token"&gt;# some code&lt;/SPAN&gt;

&lt;SPAN class="keyword token"&gt;for&lt;/SPAN&gt; fds &lt;SPAN class="keyword token"&gt;in&lt;/SPAN&gt; arcpy&lt;SPAN class="punctuation token"&gt;.&lt;/SPAN&gt;ListDatasets&lt;SPAN class="punctuation token"&gt;(&lt;/SPAN&gt;&lt;SPAN class="string token"&gt;''&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt;&lt;SPAN class="string token"&gt;'feature'&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;)&lt;/SPAN&gt; &lt;SPAN class="operator token"&gt;+&lt;/SPAN&gt; &lt;SPAN class="punctuation token"&gt;[&lt;/SPAN&gt;&lt;SPAN class="string token"&gt;''&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;]&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;:&lt;/SPAN&gt;

&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;SPAN class="keyword token"&gt;for&lt;/SPAN&gt; fc &lt;SPAN class="keyword token"&gt;in&lt;/SPAN&gt; arcpy&lt;SPAN class="punctuation token"&gt;.&lt;/SPAN&gt;ListFeatureClasses&lt;SPAN class="punctuation token"&gt;(&lt;/SPAN&gt;&lt;SPAN class="string token"&gt;''&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt;&lt;SPAN class="string token"&gt;''&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt;fds&lt;SPAN class="punctuation token"&gt;)&lt;/SPAN&gt;&lt;SPAN class="punctuation token"&gt;:&lt;/SPAN&gt;

&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; inputPath &lt;SPAN class="operator token"&gt;=&lt;/SPAN&gt; os&lt;SPAN class="punctuation token"&gt;.&lt;/SPAN&gt;path&lt;SPAN class="punctuation token"&gt;.&lt;/SPAN&gt;join&lt;SPAN class="punctuation token"&gt;(&lt;/SPAN&gt;arcpy&lt;SPAN class="punctuation token"&gt;.&lt;/SPAN&gt;env&lt;SPAN class="punctuation token"&gt;.&lt;/SPAN&gt;workspace&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; fds&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; fc&lt;SPAN class="punctuation token"&gt;)&lt;/SPAN&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; outputPath &lt;SPAN class="operator token"&gt;=&lt;/SPAN&gt; os&lt;SPAN class="punctuation token"&gt;.&lt;/SPAN&gt;path&lt;SPAN class="punctuation token"&gt;.&lt;/SPAN&gt;join&lt;SPAN class="punctuation token"&gt;(&lt;/SPAN&gt;outLocation&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; sdeString &lt;SPAN class="operator token"&gt;+&lt;/SPAN&gt; fc&lt;SPAN class="punctuation token"&gt;)&lt;/SPAN&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; arcpy&lt;SPAN class="punctuation token"&gt;.&lt;/SPAN&gt;Append_management&lt;SPAN class="punctuation token"&gt;(&lt;/SPAN&gt;inputPath&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; outputPath&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; schemaType&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; fieldMappings&lt;SPAN class="punctuation token"&gt;,&lt;/SPAN&gt; subtype&lt;SPAN class="punctuation token"&gt;)&lt;/SPAN&gt;
‍‍‍‍‍‍‍&lt;SPAN class="line-numbers-rows"&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, this only updated the DEFAULT SDE version. What's the best strategy to push those changes to the child versions as well? I would like to be able to do this programatically.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks, Naci&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 11 Dec 2021 14:42:55 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/using-append-management-for-all-versions/m-p/307260#M23912</guid>
      <dc:creator>NaciDilekli</dc:creator>
      <dc:date>2021-12-11T14:42:55Z</dc:date>
    </item>
    <item>
      <title>Re: Using Append_management for all versions</title>
      <link>https://community.esri.com/t5/python-questions/using-append-management-for-all-versions/m-p/307261#M23913</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If the changes are destined for the Default version, and you want all of those changes to propagate out to the child versions, then &lt;A class="link-titled" href="http://desktop.arcgis.com/en/arcmap/latest/manage-data/geodatabases/reconciling-a-version.htm" title="http://desktop.arcgis.com/en/arcmap/latest/manage-data/geodatabases/reconciling-a-version.htm"&gt;Reconciling a version—ArcGIS Help | ArcGIS Desktop&lt;/A&gt; using &lt;A class="link-titled" href="http://desktop.arcgis.com/en/arcmap/latest/tools/data-management-toolbox/reconcile-versions.htm" title="http://desktop.arcgis.com/en/arcmap/latest/tools/data-management-toolbox/reconcile-versions.htm"&gt;Reconcile Versions—Help | ArcGIS Desktop&lt;/A&gt;&amp;nbsp; .&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Mar 2018 23:23:03 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/using-append-management-for-all-versions/m-p/307261#M23913</guid>
      <dc:creator>JoshuaBixby</dc:creator>
      <dc:date>2018-03-08T23:23:03Z</dc:date>
    </item>
    <item>
      <title>Re: Using Append_management for all versions</title>
      <link>https://community.esri.com/t5/python-questions/using-append-management-for-all-versions/m-p/307262#M23914</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you for your reply. I have been trying to post the changes to the child versions, but the Post Changes button is always disabled while the parent SDE version is active.&amp;nbsp;I did this by posting changes from the child version to the parent. That seemed to work and got the additions from the parent version. Is that the correct workflow?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Mar 2018 15:04:22 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/using-append-management-for-all-versions/m-p/307262#M23914</guid>
      <dc:creator>NaciDilekli</dc:creator>
      <dc:date>2018-03-12T15:04:22Z</dc:date>
    </item>
    <item>
      <title>Re: Using Append_management for all versions</title>
      <link>https://community.esri.com/t5/python-questions/using-append-management-for-all-versions/m-p/307263#M23915</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Finally, I figured out the correct workflow for this. I had to change to the child version (ChangeVersion_management) before appending. Then I can propagate the changes from children to parents and grandparent. This is the only way reconciliation works.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Jul 2018 21:12:19 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/using-append-management-for-all-versions/m-p/307263#M23915</guid>
      <dc:creator>NaciDilekli</dc:creator>
      <dc:date>2018-07-24T21:12:19Z</dc:date>
    </item>
  </channel>
</rss>

