-
Notifications
You must be signed in to change notification settings - Fork 93
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
When you create a message by profile card, cannot retrieve recipients' DisplayName. #2201
Comments
Hi @mayanagi, Thank you for pointing out this behavior discrepancy. @ElizabethSamuel-MSFT, could you please investigate? |
@ElizabethSamuel-MSFT - following up on this to see if we've addressed the discrepancy outlined above. thank you! |
@exextoc Can you advise if this behavior is by design? Thx. |
@ElizabethSamuel-MSFT This is not by design. This seems to be a problem with Outlook Web behavior. @mayanagi Thanks for reporting this issue regarding get recipients. It has been put on our backlog. We unfortunately have no timelines to share at this point |
The docs have been updated with this info (see PR OfficeDev/office-js-docs-pr#2998). Transferring to the product repo to track the fix. |
Thanks for your patience. We have updated the document. Kindly reopen the bug if you have any other queries. |
When you create a message by clicking an email address in the profile card like the picture below, add-ins cannot get recipient's DisplayName.
I assume that this behavior is by design.
That's because I understand add-in can get recipient's DisplayName from the name-resolved value in a message being composed. However, the recipient is NOT name-resolved when creating a message by clicking an email address in the profile card as below.
ASK: Could you please add the notice like "You cannot retrieve DisplayName when creating a message by clicking an email address in the profile card" if this behavior is by design.
You can reproduce this behavior by following steps.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: