Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
When I try to publish a Post whit a mention to users or records in the Timeline, it gives this error:
Error Details: TypeError: Cannot read property 'entityTypeName' of undefined
Does anyone have the same error? How can I fix it? I am using Sales enterprise license and Sales app
Please share a screenshot, thanks.
I noticed that we have the same problem in all our MS environments. Here the screenshot of the error:
And the screenshot of the fact that we are not able to mention teams/records:
And this is the error log:
at Array.forEach (<anonymous>)
at MentionsControl._getMissingFetchXmlList (devdealflower.crm4.dynamics.com/.../MentionsControl.js:2:12353)
at MentionsControl._isRequiredMetadataLoaded (devdealflower.crm4.dynamics.com/.../MentionsControl.js:2:12609)
at MentionsControl._downloadIfRequiredMetadataIsMissing (devdealflower.crm4.dynamics.com/.../MentionsControl.js:2:13297)
at MentionsControl.init (devdealflower.crm4.dynamics.com/.../MentionsControl.js:2:8920)
at t._measureLifecycleMethod (devdealflower.crm4.dynamics.com/.../7.js
at t._initializeControl (devdealflower.crm4.dynamics.com/.../7.js
at Object.bs [as unstable_batchedUpdates] (devdealflower.crm4.dynamics.com/.../app.js
at P (devdealflower.crm4.dynamics.com/.../app.js
ID impegno: 245a7614-b5a6-46db-ab47-d7c16d88d4bc
Can yo try to use @user rather than #user. You can refer below article.
Hello FrancescaV ,
Checking all the replies here, I would suggest you to open a ticket with Microsoft Support team since the error seems to coming from OOB solution and you have more environments reproducing the same.
I would also try in a vanilla trial org, if you have a chance, if reproduces there is chance the error was introduced by updates.
Business Applications communities