SAPIEN Technologies

If you really need to use the msiexec.exe providing the GUID, then you can use the following PowerShell code to get the installed application GUID: ## - List all Installed Apps GUID: $appAll = Get-WmiObject -Class Win32_Product; $appAll | select name, IdentifyingNumber | Sort-Object Name; ## - Sampl...

Have you tried using breakpoints in the code to debug the form? Running the debug will identify which line is causing the issue in the form. At the same time, you mention you run the code (without the GUI) and runs in PowerShell. In most cases, the code will change a bit when running it on a Windows...

It will help if you can provide a sample script that's causing the issue.

It should look like this:

$buttonShowForm_Click={
#TODO: Place custom script here: TestUserDatagridForm01.psf
if ((Show-TestUserDatagridForm01_psf) -eq 'OK') {

}
}

Can you please provide the code block you are using in the button control to open the "Show-CoreForm_psf" form?

Seems to work fine in PowerShell Studio! Az_01_2019-11-25_10-14-25.png Az_02_2019-11-25_10-17-25.png Try using the Cache Editor! Look for the Az module(s), and make sure the correct version of the module in question is selected, Then, do the build cache and verify that the version has been updated.

Can you provide more detailed information on what you want to accomplish?

Thanks for reporting this issue. Our team will have it corrected for our next service release.

In the previous post, there's a note on Az module "minimum requirement", which is Windows PowerShell v5.1.
So, this means that Windows PowerShell v2.0 is not supported.

Only Windows PowerShell v5.1 and greater (PowerShell Core -> PowerShell v7) are supported.

The latest version of Az module is: Az 3.0.0 Microsoft Azure PowerShell - Cmdlets to manage resources in Azure. This module is compatible with WindowsPowerShell and PowerShell Core. Minimum PowerShell version: 5.1 (not Windows PowerShell v2). For more information check the Az module link on the Powe...