When attempting to export documents from ProjectWise using the Powershell command Export-PWDocuments, the references are using DMS paths still instead of relative paths based on the export location. When performing the same action using the Export Folders tool inside of ProjectWise Explorer, there's an option called "Update documents to use local paths for references and links" that works and changes the reference paths. How can this be done using the Powershell commands?
Examples of script we've used:
$LocalFolder = 'D:\_idcWork\pwArchiveStructure\BAM Training 2'
$PWFolderPath = '\Training\BAM Training'
Export-PWDocuments -InputDocuments (Get-PWDocumentsBySearch -FolderPath "$PWFolderPath") -OutputFolder "$LocalFolder" -Verbose
Export-PWDocuments -OutputFolder "$LocalFolder" -ProjectWiseFolder "$PWFolderPath" -Verbose
The script above pulls references, but the references are still using DMS folder paths instead of the relative local paths.
The -useDMSFolders switch sounds broken. What happens if you use
Hi Bill. I tried your suggestion and it still didn't change the reference paths. Here's a screenshot comparing the results between the tool and the Powershell script.
Actually from the first message you posted, it doesn't look like you were using the -UseDMSFolders switch in the first place. You could try that and see if the references resolve any better after opening a master file from the exported DMS folder. You can add the -UseDMSFolders switch to the last two lines of your script as follows:
<#Export Docs#>Export-PWDocuments -InputDocuments (Get-PWDocumentsBySearch -FolderPath "$PWFolderPath") -OutputFolder "$LocalFolder" -Verbose -UseDMSFolders
Export-PWDocuments -OutputFolder "$LocalFolder" -ProjectWiseFolder -UseDMSFolders "$PWFolderPath" -Verbose -UseDMSFolders
Let us know.
Mark Weisman | Bentley Systems
I've re-run the original script I posted and added -UseDMSFolders as suggested. It changed the way the folder structure was built in my export location, but it did not change the references in the drawings to use relative pathing like the Folder Export tool does inside of ProjectWise. That's what we're hoping to accomplish via powershell. Here's the option we've been playing with in ProjectWise.
When that option highlighted in the screenshot is not selected, the path for references starts with PW_WORKDIR which we do not want.
Until we add this enhancement to Export-PWDocuments, please try adding a PW_WORKDIR environment variable either at the system level or in MicroStation. Its value should be a full path to the root of the DMSFOLDER where the documents are exported. Let us know if that helps.
Check out the Export-PWDocumentsSimple cmdlet in the latest release of PWPS_DAB. It should fix the reference files attachments of exported design files so that path information is substituted for PW_WORKDIR.
Answer Verified By: Trevor Sedlock