1 Reply Latest reply on Sep 18, 2014 3:54 PM by Jeremiah Davis

    Drag and drop moves DB version of file, not local version

    Richard Nord

      We experienced the following situation today:

       

      A VB .exe file package was checked in on 2/17/2014

      Same file package was checked out on 9/17/2014 and modified. 

      The .exe and related files were dragged and dropped to a location outside of the PDM (no check in occurred, the files were still checked out)

      The modified version of the .LNG files (and perhaps others) did not make it with the drag and drop.  Instead, the versions checked in on 2/17/2014 were dragged and dropped.

      In other words, the drag and drop resulted in a move of the database version of the files, not the local version.

       

      We're wondering, is there a reason that the modified versions of the files were not relocated?  Is it because of the type of file it is, or does this affect other types of files as well?  We have not noticed it happening with other file types.

       

      Thanks in advance for any help.

        • Re: Drag and drop moves DB version of file, not local version
          Jeremiah Davis

          Hello Richard,

           

          This sounds like you were trying to perform the drag and drop on a workstation that was not the same as the one where these files were checked out. Or possibly the files were checked out, but a "Get Version" was performed such that it reverted to the last checked-in version in the vault.

           

          Are either of these the case?

           

          EPDM is going to copy out the files that are in the local cache. If you have modified versions of these files in your local cache, then that is what will be copied. If the files are checked out on a different machine, then the files in the local cache will be the latest ones on the server, assuming a "Get Latest" has been performed.