we are getting the path too long error when exporting documents outside of projectwise. We have a lot of information to download from our datasource. We would need to be able to correct this problem in a way that is not manual
This is USUALLY a Windows limitation issue. ProjectWise supports longer pathnames than does Windows, which can be a good thing...unless you need to Export documents. Having said this, there aren't many options to "press on", each of them which will require some form of manipulation of your ProjectWise content. You will need to (in some way) resolve (address) the Document/File Paths that exceed the limit for your Destination Path before exporting them.
You could first try:
You could craft a PowerShell Script that will examine the Full Paths of your Documents (by a Folder or for the entire Datasource) and identify those Documents that exceed the acceptable character length (of your parent Destination Path). You could then take the desired action (i.e. change one or more Folder Names in the Path of the Document or change the File Name of the Document).
ProjectWise Explorer CONNECT Edition, Version 10.00.03.453
ProjectWise Drive, Version 2022.1.328
OpenRoads Designer CONNECT Edition, Version 10.09.00.91
OpenRoads Designer CE 202 Release 2, Version 10.10.21.4
Power GEOPAK V8i (SELECTseries 10), Version 08.11.09.918
Which export cmdlet are you using and what version of PWPS_DAB? Also, what version of Windows are you on?
According to Export-PWDocuments it should support Windows long paths
Folder structure is preserved (even long paths so make sure you have a Windows File Explorer replacement that can navigate long paths).
I believe it uses the \\?\ UNC construction for exporting those long paths so if you're getting an error your Windows may not have it enabled. Enabling this requires a somewhat recent version of Windows 10, and it won't enable long paths for mapped network drives.
How to Enable or Disable Win32 Long Paths on Windows 11/10 (thewindowsclub.com)
I always export to my local hard drive and if need be will create a 1 letter folder directly off C: and use that to keep path lengths down. If even that doesn't work I've used the subst command to map a local path to a single drive letter.
subst | Microsoft Docs
If all of that doesn't help, or you can't enable long paths both Export-PWDocumentFilesToZip and Export-PWDocumentsToArchive will maintain the long paths but if the intent is to get the files out of ZIP/Archive on to a windows file system the problem will return.
Lately I've been using Export-PWDocumentsToArchive when copying files to other datasources and don't want to worry about path lengths since they'll never appear on a windows file system.
Oh, as for something that can actually navigate long paths if you get it working, the pwps_dab change long mentions FreeCommander. I haven't tried it myself but it's here:
I use XYPlorer as a windows explorer replacement, i suspect it supports long paths too but haven't noticed. I've never gotten an error about a path to long from it.
The LongPathTool application is the go-to solution for resolving any issues caused by long file paths on Windows and Mac.