-
Notifications
You must be signed in to change notification settings - Fork 341
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
Person-Card component no longer works within layouts > People > Manage people fields #3939
Labels
bug
Something isn't working
Needs: Author Feedback
Awaiting response from the original poster of the issue.
Comments
kasperbolarsen
added
the
Needs: Author Feedback
Awaiting response from the original poster of the issue.
label
Nov 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
Needs: Author Feedback
Awaiting response from the original poster of the issue.
Version used
4.12.2
Describe the bug
In older versions of PnP Modern Search we were able to use Microsoft Graph Person-Card component to render a manager display name based on the managers email address returned in search after configuring a managed property Manager.
This was working well allowing users to see both the user information on the person they where looking for and that persons manager without having to click through pop ups.
The issue now is that the Microsoft Graph Person-Card component no longer works within the "Manage people fields" section. The last known working version was 4.9. We haven't tested ever version between 4.9 and 4.12.2 but I know the issue exists in:
To Reproduce
Detailed steps to reproduce the behavior:
{{slot item @root.slots.UserDisplayName}}
with<mgt-person user-id="{{getUserEmail (slot item @root.slots.UserEmail)}}" view="oneline"></mgt-person>
Expected behavior
We expect to see the Users Name in the first field. As demonstrated in the screenshots.
Screenshots
Expected outcome:
Actual outcome:
Desktop (please complete the following information):
Additional context
The above steps are a simplified version of what we do with a Manager field. For our environment using a users email or UPN is not a valid option as they do not include the users name in full or in any consistent order.
The text was updated successfully, but these errors were encountered: