Anyone experiencing similar problems?
After updating to latest PWPS_DAB version 220.127.116.11 I am getting an error running any existing scripts using Select-PWSQL with an output to an Excel spreadsheet.
The SQL results are displayed but the error occurs when attempting to write to Excel
e.g. Select-PWSQL -SQLSelectStatement $SQLstr1 -OutputFile 'c:\temp\file.xlsx'
WARNING: Error: Could not load file or assembly 'DocumentFormat.OpenXml, Version=18.104.22.168, Culture=neutral, PublicKeyToken=8fb06cb64d019a17' or one of its dependencies. The system cannot find the file specified. at PWPS_DAB.XLSXDataSetTools.DataSetToXLSXFast(DataSet ds, String sWBName) at PWPS_DAB.SelectPWSQL.ProcessRecord()
In the meantime I will will try rolling back the PWPS_DAB version to see if I can get it working again
Try version 22.214.171.124 which I just released. I fixed that missing dependency, but, in the meantime, I actually changed the way we generate XLSX files. I think it's an improvement, but happy to hear your feedback.
Answer Verified By: Peter Willmen
Thanks Dave version 126.96.36.199 fixed the dependency issue in Export-PWProjectAccessControl as well.
Possibly unrelated but I've noticed Export-PWAccessControlToExcel is crashing PowerShell in the current versions. I need to rollback a few builds and see when it was last working as we use it a lot.
I've seen this crashing too but think it's related to ProjectWise Office 365 Integration, specifically the latest additional module
AECOM Roads UK&I Digital Engineering, Design & Solutions Lead | Sector Information Management Lead
Principal Engineer – Digital
OpenRoads Designer 10.10 | MicroStation CE 10.16 | ProjectWise CE 3.4 | ContextCapture | ProjectWise PowerShell 2.0 | Generative Components | OpenBridge Designer 10.10
Revit 2022 | Civil 3D 2022 | Recap 2022 | Infraworks 2022 | Dynamo | Navisworks Manage
PowerShell | Visual Studio | Office 365 | Power Automate | Teams | SharePoint | Visio
Speckle | BIMVision | Revizto | Solibri
Thanks Chris that was on my list to try as well but the day got away from me. I only recently installed the ProjectWise Integration for Microsoft Office 365 v10.00.3907 update so it's a likely candidate for the issue. Will test that tomorrow.
Export-PWProjectAccessControl was developed (by Brian F.) as a replacement for Export-PWAccessControlToExcel to deal with performance and stability issues. I think we also had that Office integration conflict a few years ago. The intent was that Export-PWProjectAccessControl would completely replicate the Export-PWAccessControlToExcel functionality. Please let us know if that's not the case. The names are similar, but the guts are quite different.
I can confirm that the ProjectWise Integration for Microsoft Office 365 v10.00.3907 update breaks the Export-PWAccessControlToExcel cmdlet.
I can see the performance benefit to Export-PWProjectAccessControl and from a purely automated PowerShell activity wouldn't have a problem switching to it. The benefits to Export-PWAccessControlToExcel however are it's backwards compatibility with the Access Control Import/Export from within ProjectWise Explorer which is helpful when not all admins are equal with their PowerShell scripting experience plus it's visual representation of the permissions can be easier to read.
PS there might be a bug with Export-PWProjectAccessControl missing workflow access control from the export but I'll need to run a couple more tests to confirm exactly what's happening there.