Personalized Community is here!
Quickly customize your community to find the content you seek.
Check out the latest Customer Service updates!Learn about the key capabilities and features of Dynamics 365 Customer Service and experience some of the new features.
Download overview guide | Watch Customer Service video
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I noticed that with this version, a contact specified within entitlment setup is now required to create an incident related to an entitlement.
The feature decribed by Microsoft is that we can describe contact within entitlements in order to restrict access to them, it no contact is described, access to support should be allowed to any contact of the customer.
FYI, we had an automatic process for incident creation that fall down because of that reason these last 3 days.
Does anyone met the same issue ?
Is it planned to consider this as a bug ?
Thanks you for your feedback.
CRM Consultant (Titanium)
we are facing the same problem. We have 2 instances/applications- currently one is in v18.104.22.1688 and one in v22.214.171.1241.
Application in 126.96.36.1998 works the same as you described, which is, in my view, bug.
Application in 188.8.131.521 works as before.
So I hope that in few days upgrade on v184.108.40.2061 will solve the issue. And also that some next minor update wont bring it back.
D365 Consultant (AutoCont)
Thank you for the feedback.
It would be nice if Microsoft people also feel concerned about the subject.
Have a nice day,
Business Applications communities