Will the "Import-PWDocuments" switch "-ExcludeSourceDirectoryFromTargetPath" be enabled so we can use the higher than 1.6.x versions?
Been waiting to update machines from 1.4.x due to the "Powershell Users" group requirement, and now that I do, I cannot use the same command line or the new command line...
The suggested fix of putting the file into one folder and moving them to another does not help if the goal is to sync externally generated files into a static folders set, only updating the needed files.
That fix would generate 100% upload every time, defeating the purpose of only updating changes...
Need some help or ideas here please.
Thanks,
John
I'm building an Excel spreadsheet in PowerShell and running my imports with Import-PWDocumentsBySpreadsheet because of issues with the Import-PWDocuments cmdlet. I can check the age/existence of documents at the source/destination when populating the spreadsheet if I need to sync data into ProjectWise.
See this link for issues with Import-PWDocuments
https://communities.bentley.com/products/projectwise/content_management/f/projectwise-powershell-extensions-forum/172282/import-pwdocuments-not-working-as-expected
Robert,
Thanks for your quick reply and idea about using Excel... a bit more than I want to get into today to make a broken function work...
Dave,
Thanks for the link, I did read all of that prior to putting in this cry for help...
So again the cry for help... Brian/Dave B., can the switch function for "-ExcludeSourceDirectoryFromTargetPath" be repaired to work?
To me, the function should either work as it is documented, or be revised to indicate it will not... after all, these are basic (simple?) functions, right?:
We had a routine called "ch2mhillfileimportexport.exe" that read a XLS listing from and to folders, and it did what we needed (Bentley had written for us a while back, last update was Feb 2016), that started to mysteriously fail ~18+ months ago when running on some PW Project Folders, it just would not get the folder contents anymore...
Since then, the bar has moved (I get it..., it must evolve..., new and interesting stuff...), but now it is partially inoperable (not so good)...
If I must write considerable "wrapper" routines around the functions to make them sort of work, or use other functions to fake what the implied function is, or it increases the WAN traffic significantly, no one wins...
I have removed the newer PWPS_DAB version, put the older back on, and will just continue with that for a while...
Just my opinion, all please feel free to disagree and respond back... I want to learn if and where I am right or wrong...
According to the change log for the PWPS_DAB module, this has already been accomplished. Is it not working for you?
2019-02-09 Version 1.9.4.0Added cmdlets Get-PWConnectedProjectAssetTypes - returns list of valid Asset Types Get-PWConnectedProjectIndustryTypes - returns list of valid Industry TypesChanged cmdlets CheckOut-PWDocuments - Now supports the -NoReferences switch in all modes (ChekcOut, Export, CopyOut) Import-PWDocuments - resolved bug with handling of -ExcludeSourceDirectoryFromTargetPath Convert-PWAccessControlMaskToString - enhanced return values Add-PWConnectedProject - Now supports -Token argument Get-PWConnectedProjectDataLocations - now supports -Token argument