Replies: 1 comment 1 reply
-
I see this was converted from an issue to a discussion. Does that mean this is by design? Does anyone from the team have some light to shed on this? This was not the behavior of this command not so long ago. A little help would be greatly appreciated! |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Reporting an Issue or Missing Feature
The command Get-PnPUserProfileProperty now outputs as a hashtable. This prevents running a " | Select " against any of the properties that matter.
Moreover - When you run Get-PnPUserProfileProperty -Account $UPN -properties Many of the properties come back blank.
Expected behavior
The ability to run a " | Select " against the output like you could in the past. or at minimum not return blank output when you run Get-PnPUserProfileProperty -Account $UPN -properties
Actual behavior
N/A see above
Steps to reproduce behavior
Get-PnPUserProfileProperty -Account $UPN | Select PersonalUrl
Get-PnPUserProfileProperty -Account $UPN -properties PersonalUrl
What is the version of the Cmdlet module you are running?
on Powershell 7.3 and PNP version 2.2
Which operating system/environment are you running PnP PowerShell on?
Beta Was this translation helpful? Give feedback.
All reactions