I am having problems when setting Project resources to 'Inherit' or 'None'
The help file and examples seem to be incorrect as '-ResourceMemberName' is a required value
#Example usage for setting a project's application resource to inherit.
Set-PWRichProjectResource -FolderPath 'Projects' -ResourceType 'application' -Inherit
#Example usage for setting a project's workspace profiles resource to none.
Set-PWRichProjectResource -FolderPath 'Projects' -ResourceType 'workspaceprofile' -None
Also I have found that the cmdlet will add multiple entries for the same value into the resources
For example if I run the following command twice, there will be 2 entries in the resource list for 'ENVIRONMENT 1' -
Set-PWRichProjectResource -folderpath $project -resourcetype environment -resourcemembername 'ENVIRONMENT 1'
I have a workaround for setting to 'Inherit': "-ResourceType environment -ResourceMemberName 'NULL' -Inherit" but this does not work when setting to 'None'
FYI - this is using a SS4 Datasource
I have updated the cmdlet to resolve this issue. Should be available in a future release of the PWPS_DAB module.
Answer Verified By: Peter Willmen
One other thing I have found is that assigning the 'workflow' resources has no effect
Hey Peter, I have tested setting the workflow and it appears to be working correctly. However, I have overlooked a step in the validation process for the resource (erroring when it doesn't exist), so even if you enter an invalid workflow name, the process will still complete. Obviously, with no change. I will update the cmdlet to resolve this.
Once again, I have updated the cmdlet to resolve this issue. Should be available in a future release of the PWPS_DAB module.