Share via

When using Comments on Microsft lists ... mentioning @ , coming up with - @mention{0}

Anonymous
2024-02-15T13:02:53+00:00

Just spent the week migrating a MS database over to MS lists, use alot already, on this list the comment feature is not working, the @ symbol allows me to click names and looks fine but soon as hit send it comes up with @mention{0} and person doesn't get the email.

works fine in my other lists made in the same way

Microsoft 365 and Office | Install, redeem, activate | For business | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

3 answers

Sort by: Most helpful
  1. Anonymous
    2024-06-28T14:34:19+00:00

    Hello,

    I have the exact same problem - has this issue been resolved/ any idea regarding cause?

    @mention works in some lists, in other I get the @mention {0} instead of proper selection of addressee from database.

    Thank you & KR

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-02-28T15:16:35+00:00

    Hello Thankyou, yes issue happens with multiple team members, how do I get hars logs please?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-02-15T14:01:07+00:00

    Dear Lewis Whelan,

    Good day!!

    Apologies for the inconvenience caused and please don’t worry, let’s work together on your concern and move towards a resolution path.

    I understand your concern and I would like to convey that I have tested the behavior in the Lists of Microsoft Lists, where @mention feature works without any issue.

    Since you mentioned the problem doesn’t happens with the other lists and as there is no settings in the List for @mention feature, I would like to suggest you check the behavior by accessing the List in the InPrivate or Incognito window.

    If still the same problem persists, I believe the problem should be further investigated by related development team via collecting HAR logs because there is not any related service incident reported at the Microsoft Service Health dashboard.

    I do feel regret for not resolving the problem and redirecting you to the related development team but the fix to your concern can be find out through the HAR logs and suggest you raise a support ticket from the Office 365 admin center, where the related team will investigate the problem further by collecting the HAR logs.

    Reference: Get support - Microsoft 365 admin | Microsoft Learn

    Note: To create a support ticket, you need to have admin privileges and if you aren’t admin of your Office 365 organization, please contact the admin of creating a new ticket.

    Appreciate your patience and understanding. Have a great day!!

    Best Regards,

    Sophia

    Was this answer helpful?

    0 comments No comments