Import-Module error with PowerShell SDK when installed manually

[David_Norris (Terry Yau)]

In step 4 of the following procedure (with SDK v1.4.12), Import-Module returns:
Import-Module: The required module 'PSSailpoint.Beta' is not loaded.

This wasn’t an issue with v1.4.3 (manual and auto). Auto install of v1.4.12 doesn’t have this issue either.

Has anyone ran into this?

[tyler_mairose]

Hello Terry,

We need to update our docs, I will create a task for us to complete.

After version 1.4.3 we split the modules out into separate submodules for each version (beta, v3, v2024, etc…) from then on the main PSSailPoint module specify the others as required modules.

[David_Norris (Terry Yau)]

Thanks. For the time being, any pointers as to how I can move forward with the manual install of v1.4.12?

[tyler_mairose]

You can manually install if you clone the PowerShell SDK repo and run the following from the root of the project.

Import-Module -Name '.\PSSailpoint\beta\src\PSSailpoint.Beta' -Verbose
Import-Module -Name '.\PSSailpoint\v3\src\PSSailpoint.V3' -Verbose
Import-Module -Name '.\PSSailpoint\v2024\src\PSSailpoint.V2024' -Verbose

. .\PSSailpoint\Configuration.ps1
. .\PSSailpoint\Pagination.ps1

[David_Norris (Terry Yau)]

Thanks for the pointers.

I’m guessing the polished up version of the documentation will include ways to import the modules without relative paths and the need to source the Configuration and Pagination scripts, correct?