Import-PWDocuments Issue with 1.6.2.0

Here is my statement:  Import-PWDocuments -InputFolder $InputFolder -ExtensionsOfInterest ".xtx" -ProjectWiseFolder $CurrentFolder.FullPath

$InputFolder = "C:\Stats"

There is a file in stats named d.xtx

In PWPS_DAB 1.5.4.0:

The above statement will take the file from the PC and place it in PW at $CurrentFolder.FullPath (expected)

In PWPS_DAB 1.6.2.0

The above statement will take the file from the PC and place it in PW at ($CurrentFolder.FullPath)\Stats and then place the file there

I ran the same query and got these results - the only difference was the version. 

In 1.6.1.0 this cmdlet was updated (which may be the culprit).

Parents
  • We'll have to look into this. As you can see below from the module change log, there was a change to the cmdlet in version 1.6.1.0  to handle long paths.

    Import-PWDocuments - Now supports importing from long paths on disk (Export-PWDocuments already supports writing to long paths on disk.)

    For the time being, I would suggest importing to a temporary folder which will mimic the folder structure on the local drive, You can then move the documents to the correct location.

Reply
  • We'll have to look into this. As you can see below from the module change log, there was a change to the cmdlet in version 1.6.1.0  to handle long paths.

    Import-PWDocuments - Now supports importing from long paths on disk (Export-PWDocuments already supports writing to long paths on disk.)

    For the time being, I would suggest importing to a temporary folder which will mimic the folder structure on the local drive, You can then move the documents to the correct location.

Children