Project transactions out of order after import

[gdenning]

I just finished importing my SourceSafe repository into Vault, and it ran without errors over the weekend (took 2 full days, but that's okay). However, I've noticed a problem. When I try to merge two folders, the "Select Changes to be Merged" list (5th page of the merge branches wizard) shows transactions completely out of order. The list of changes are completely random, making it impossible for me to find the latest changes to the project. When I list "Project History", everything looks fine because the dialog sorts in date order, but the "Select Changes to be Merged" sorts in version order, which is completely wrong. Any suggestions? The merge branches functionality is our main reason for wanting to use Vault and this problem makes it unusable for us. I've attached a screen shot to illustrate.

[gdenning]

After looking into this again, it appears that what is going on is that the import functionality checks files in in this order:

<file A>
<file A version 1>
<file A version 2>
<file A version 3>
<etc>
<file B>
<file B version 1>
<file B version 2>
<file B version 3>
<etc>

As a result, the project transaction numbers are not in the order that the files were originally checked in, they are in the order that the import routine checked them in. So, I need either a SQL script to re-order the transaction versions based on check-in date, or a change to the "Merge Branches" wizard to sort transactions by date instead of by transaction version.

[lbauer]

As you have seen, the way we do the import doesn't lend itself to dates and versions being in an intuitive order. I can log a feature request to take a look at the way dates appear in the Merge Branches Wizard for imported items.

Going forward, the dates for new items and versions will be in the proper order. In the meantime, trying to merge branches on imported items will get unexpected results. We don't recommend it.

[jsynoski]

Linda,

Would a solution to this be to check all folder files files out and then check them in (Check In unchanged files option set to Check In)?

Would this get the version numbers to be "right"?


Jim

[lbauer]

Haven't tried this; it should increment the version and get the date right for this latest checkin.