I have a rather complicated enterprise geodatabase version scheme that looks like this: 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: # some code for fds in arcpy . ListDatasets ( '' , 'feature' ) + [ '' ] : for fc in arcpy . ListFeatureClasses ( '' , '' , fds ) : inputPath = os . path . join ( arcpy . env . workspace , fds , fc ) outputPath = os . path . join ( outLocation , sdeString + fc ) arcpy . Append_management ( inputPath , outputPath , schemaType , fieldMappings , subtype ) 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. Thanks, Naci

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Using Append_management for all versions

NaciDilekli

I have a rather complicated enterprise geodatabase version scheme that looks like this:

Multiple projects with subprojects

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:

<SPAN class="comment token"># some code</SPAN>

<SPAN class="keyword token">for</SPAN> fds <SPAN class="keyword token">in</SPAN> arcpy<SPAN class="punctuation token">.</SPAN>ListDatasets<SPAN class="punctuation token">(</SPAN><SPAN class="string token">''</SPAN><SPAN class="punctuation token">,</SPAN><SPAN class="string token">'feature'</SPAN><SPAN class="punctuation token">)</SPAN> <SPAN class="operator token">+</SPAN> <SPAN class="punctuation token">[</SPAN><SPAN class="string token">''</SPAN><SPAN class="punctuation token">]</SPAN><SPAN class="punctuation token">:</SPAN>

&nbsp;&nbsp;&nbsp; <SPAN class="keyword token">for</SPAN> fc <SPAN class="keyword token">in</SPAN> arcpy<SPAN class="punctuation token">.</SPAN>ListFeatureClasses<SPAN class="punctuation token">(</SPAN><SPAN class="string token">''</SPAN><SPAN class="punctuation token">,</SPAN><SPAN class="string token">''</SPAN><SPAN class="punctuation token">,</SPAN>fds<SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">:</SPAN>

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; inputPath <SPAN class="operator token">=</SPAN> os<SPAN class="punctuation token">.</SPAN>path<SPAN class="punctuation token">.</SPAN>join<SPAN class="punctuation token">(</SPAN>arcpy<SPAN class="punctuation token">.</SPAN>env<SPAN class="punctuation token">.</SPAN>workspace<SPAN class="punctuation token">,</SPAN> fds<SPAN class="punctuation token">,</SPAN> fc<SPAN class="punctuation token">)</SPAN>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; outputPath <SPAN class="operator token">=</SPAN> os<SPAN class="punctuation token">.</SPAN>path<SPAN class="punctuation token">.</SPAN>join<SPAN class="punctuation token">(</SPAN>outLocation<SPAN class="punctuation token">,</SPAN> sdeString <SPAN class="operator token">+</SPAN> fc<SPAN class="punctuation token">)</SPAN>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; arcpy<SPAN class="punctuation token">.</SPAN>Append_management<SPAN class="punctuation token">(</SPAN>inputPath<SPAN class="punctuation token">,</SPAN> outputPath<SPAN class="punctuation token">,</SPAN> schemaType<SPAN class="punctuation token">,</SPAN> fieldMappings<SPAN class="punctuation token">,</SPAN> subtype<SPAN class="punctuation token">)</SPAN>
‍‍‍‍‍‍‍<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

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.

Thanks, Naci

Trouver plus de publications taguées avec

Accepted answers

NaciDilekli

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.

All comments

NaciDilekli

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. 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?

Thanks

bixb0012

If the changes are destined for the Default version, and you want all of those changes to propagate out to the child versions, then Reconciling a version—ArcGIS Help | ArcGIS Desktop using Reconcile Versions—Help | ArcGIS Desktop .

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.