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.
2022 Release Wave 2Check out the latest updates and new features of Dynamics 365 released from October 2022 through March 2023
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
Hello. I have been trying to assign an Appointment (Activity entity) in CRM 4.0. The user I tried assigning to has the System Administrator role so they should be able to receive it. However, I am greeted with the below error message:
I have been using a CRM user account called 'User Two' for testing purposes. I have given this user the 'Assign' right for the Activity entity:
The Appointment entity has the following three tabs:
As can be seen, the only lookup field on the Appointment form is for the Owner (User). I have also given the 'Appended To' right to the User entity to allow the Owner lookup value to be added to the Appointment entity, but I am still getting the same error message mentioned earlier on.
Are there any other permissions which I am missing which are needed to allow the assigning of an Appointment to another user?
Can you check the permissions on the Note entity ? Depending on the cascading rules for the relationship (between appointments and notes), the notes may also be assigned during this process, so the user would need rights for this.
If that's not it, enable tracing , and the trace log should give you the privilegeid that you're missing, and you can look this up in the Privilege view in SQL
After following the tracing and SQL step, it turned out that the user needed Read Access for the Report Entity and Read Access for the Queue. After adding those permissions to the security role it worked! Strange that those permissions were needed for sharing an Appointment. Thanks!
Business Applications communities