-
Notifications
You must be signed in to change notification settings - Fork 348
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Get-PnPTerm fails with -Includes #1304
Comments
@KoenZomers - I installed using Install-Module PnP.PowerShell -AllowPrerelease -SkipPublisherCheck -Force and it now shows as using 1.8.48. Still getting the same error in both PS v5 and v7 :( |
@KoenZomers looks like I might have been a bit too quick off the mark - in Australia so timing is likely out a bit :) Will try again Monday morning. |
@paylord Sorry didn't realize you were on the other end of the globe :) The new version is 1.8.49 and is out now for you to try this: https://www.powershellgallery.com/packages/PnP.PowerShell/1.8.49-nightly |
@KoenZomers Now on 1.8.53 and can confirm it is correctly pulling back the parent if it is a Term and pulls back an empty object if the parent is a TermSet. Thanks for the support :) |
Thanks for checking and confirming @paylord ! |
Reporting an Issue or Missing Feature
Get-PnPTerm is throwing an error when trying to use the -Includes parameter
Expected behavior
I would expect to be able to use -Includes to populate additional properties as part of Get-PnPTerm.
Actual behavior
Get-PnPTerm is working fine:
PS C:\WINDOWS\system32> $term = Get-PnPTerm -Identity '37982bc4-efea-4b32-af8e-56135a773b70'
PS C:\WINDOWS\system32> $term
Name Id Child Terms
Train 03 37982bc4-efea-4b32-af8e-56135a773b70 0 (Not loaded)
With -Includes throws an error:
PS C:\WINDOWS\system32> $term = Get-PnPTerm -Identity '37982bc4-efea-4b32-af8e-56135a773b70' -Includes Parent
Get-PnPTerm : Cannot bind positional parameters because no names were given.
At line:1 char:9
PS C:\WINDOWS\system32>
Steps to reproduce behavior
See above example
What is the version of the Cmdlet module you are running?
1.8
Which operating system/environment are you running PnP PowerShell on?
The text was updated successfully, but these errors were encountered: