When running a simple 'Get-PWDocumentsBySearch' command$Docs = Get-PWDocumentsBySearch -SearchName "$ProjectFolderPath\$pdfSearchName" -filename '%.pdf' -GetAttributes
I now get an error, which I never used to get beforeGet-PWDocumentsBySearch : Not logged in as a ProjectWise Administrator.
I am using the Open-PWConnection method because I don't want to use an administrator login -Admin parameter, the New-PWLogin method requires an administrator login and I don't want to use the GUI because this is on an automatic scheduled task.
ModuleType Version Name---------- ------- ----Binary 184.108.40.206 PWPS_DAB
Any assistance will be greatly appreciatedKind regards Gavin Chapman
See version 220.127.116.11 just posted. You can now login with New-PWLogin and use the cmdlets with a non-admin user who is a member of a group called PowerShell Users.
$encryptedPassword = Read-Host -Prompt "Enter Password:" -AsSecureStringNew-PWLogin Naou22468a:PW_GAS_PRD -UserName PowerShellUser -Password $encryptedPassword -NonAdminLogin
Think I finally understood what you guys were asking for: the ability to do bulk processing against a datasource that may not be your own. Did not even occur to me...
Anyway. Hope that helps. Added Sqlite support for 64-bit, too.
Answer Verified By: Gavin Chapman
This is timely. I tried logging in with a 'test' account only to receive the error noted by the O.P. I had the thought of doing Infrastructure Change Testing with Pester, so hopefully this will allow me to say, use a 'standard' user account to bounce a drawing through the workflow and test that it actually did, etc. etc.
So next time there is a change in the workflow, security or whatever, I can just run the tests again.
Do the users have to be in a PowerShell Users group or will a user list also work?
They must be in a ProjectWise Group.