Change Version

[TedCronin]

Love the new dialog.  Lots of great info now to preview.  One thing off the top of my head, would be to give me the capability to add a version when inside the Change Version dialog.  Maybe I forgot to add a version, so when I go and want to change, oops, forgot to add, but lone and behold, I can add one from inside the Change dialog.  That would be handy addition to the tool.  Also, first time opening the dialog, the display got really funky for the dialog, probably won't be able to repro on your end.

[TedCronin]

Problem  -

If I want to change the version, I have to select the transactional tab.  This works as expected.  If I select the Tree View Tab, and select a version there, I cannot change to a version that way.  The dialog just closes and no change occurs.  Is this expected?

I would expect that if there are three tabs on a dialog for Changing Versions, I would be able to use all three tabs interactively, and not just visually.  So, Transactional works.  Tree View is great in that I see the tree view, but I want to connect (change) using this view.  Unfortunately, I don't have a historic view for this database so I cannot test that right now.


Why no filter with Tree View?

[BrentPierce]

Ted,

We can't reproduce the issues you are running into with the tree view. Could you be a little more specific about the workflow you are following to change the version in Map?

As for the filtering of the tree view. The tree view displays the hierarchy of all the versions in the geodatabase. If some versions are filtered out of the tree view this parent/child view of the versions does not really make sense. For this reason we did not provide the ability to filter when viewing the tree view of the versions in the geodatabase.

Hope this helps,
-Brent

[BillFox]

The change version tool should allow the ArcSDE/geodatabase admin to create a new version on be-half of another user.
This would ease the process of going to state zero while in an off hour maintenance window.
The editors should not need to know anything about creating and deleting versions - only the save, reconcile and post loop.
As long as the editors know to save, reconcile and post before the maintenance window we could even have a short python script
do the delete versions and create versions on the editors behalf.
Also, applications such as ArcGIS Server services that reference named versions could be managed in the same way.