Summary: Get data from Windows Powershell in Orchestrator for debugging.
Is there an easy way to troubleshoot a Windows PowerShell script in Orchestrator so I can see if the data is $Null or is the right type?
Leverage the Export-Clixml cmdlet within the script against the object in question:
$SomethingNotWorking | EXPORT-CLIXML C:\debug\something.txt
Then in Windows PowerShell, rebuild the variable to examine it outside of the script:
$SomethingNotWorking | GET-MEMBER