Incomplete export: I used the Export-PWDocuments command but in some cases it doesn't export all documents Is there any way to activate an activity log?

  • Alfredo,

    Here's a simple script to capture the output from Export-PWDocuments to a log file:

    Get-PWDocumentsBySearch -FolderPath 'my test folders' -OutVariable MyDocuments
    $Splat_ExportParams=@{
        InputDocuments = $MyDocuments
        OutputFolder = 'c:\temp\exportTest' 
        ExportVersions = $true
        ExportMetadata = $true
        ExportMetadataFile = 'c:\temp\exportTest'
    }
    
    Export-PWDocuments @Splat_ExportParams -Verbose *> 'c:\temp\export.log'
    

    This will export document versions* as well as the active document.  There may be other ways to capture the output, but by using -Verbose and redirecting the output to a log file, that may work for your needs.

    Now looking at your image where you are comparing the documents found in ProjectWise Explorer's Folder Property dialog, and what you see in a Windows File Explorer's folder property dialog, please keep in mind that ProjectWise documents are not required to have a file, so if there are any "abstract" documents in the ProjectWise folder tree, then that will lower the file count.  Also, it isn't clear from your image if you have any versions.  If you don't export the versions, the file count can be different as well.

    FWIW, I did my testing with:

    • ProjectWise Explorer v10.00.03.280
    • ProjectWise Integration Server v10.00.02.265
    • PWPS_DAB v1.23.8.0
    • Windows 10 Enterprise 64-bit

    *Update:  It looks like there is a bug in that my export didn't include my test version file.  I'll look into this and verify the problem and fix it if it is a bug.

    Dan Williams
    Solution Consultant
    Bentley Systems, Incorporated
    Portland, OR, USA (Pacific Time UTC-08:00)

  • Well, thanks for the answer.
    I tried to run the script and the result contains some errors.
    Now I'm in confusion...
    I state that I do not know ProjectWise and I have a customer who needs to export all documents because the activity is over.
    From what I have seen the Projectwise platform was used as a files repository (like a fileserver)
    I thought of using powershell to overcome the problem of long paths of which the "folder export wizard" tool is affected but it doesn't export all documents and I don't understand why because if I access the document through projectwise explorer I can export it.

    Below is the error I encountered with the script you suggested:

    Error: Could not find a part of the path 'd:\test\Affidatari\ATI Italiana Costruzioni - Manutenzione Pal Italia / Cardo\02- Subappalti\CASELLA IMPIANTI S.r.l.\Documenti
    Amministrativi\art.38\Massive_2015-09-15,0954'.
    at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
    at System.IO.Directory.InternalCreateDirectory(String fullPath, String path, Object dirSecurityObj, Boolean checkHost)
    at System.IO.Directory.InternalCreateDirectoryHelper(String path, Boolean checkHost)
    at PWPS_DAB.ImportExport.ExportIndividualDocument(ProjectWiseDocument pwDoc, String sMonitoredFolder, Boolean bUseDMSFolders, Boolean bExportMetadata, Boolean
    bUseUTC, PSCmdlet cmdlet)
    Error on copy out of '\\?\d:\test\Affidatari\ATI Italiana Costruzioni - Manutenzione Pal Italia / Cardo\02- Subappalti\CASELLA IMPIANTI S.r.l.\Documenti
    Amministrativi\art.38\Massive_2015-09-15,0954\Modulo_Massive_2015-10-01,0925.fdf' which was being copied out because Did not exist on disk
    Error: Index was out of range. Must be non-negative and less than the size of the collection.
    Parameter name: index
    at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
    at System.Collections.Generic.List`1.get_Item(Int32 index)
    at PWPS_DAB.ImportExport.ExportIndividualDocument(ProjectWiseDocument pwDoc, String sMonitoredFolder, Boolean bUseDMSFolders, Boolean bExportMetadata, Boolean
    bUseUTC, PSCmdlet cmdlet)

    ProjecWise Explorer: 10.00.02.99

    PWPS_DAB 1.23.8.0

    Windows7 pro SP1

  • Long paths are a different problem because ProjectWise allows very long folder paths while Windows file systems are normally limited to a max length of 260 (see MAX_PATH).  ProjectWise will also allow some of the "special" characters to be used in the folder names that are not legal for paths or file names in Windows file systems. Brian Flaherty has at least one Blog posting about exporting with long folder paths, and you may want to search this site for more postings about long paths.  

    Dan Williams
    Solution Consultant
    Bentley Systems, Incorporated
    Portland, OR, USA (Pacific Time UTC-08:00)