Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
If you can ask customer to delete way to old history of appointment then it would be good idea to delete respective entry from POA table for deleted appointment.
I believe this is On-Premise and you are directly dealing in SQL, so a backup of atleast those table where you are deleting entry should be taken.
If you have DEV instance then you can do following to test
Try deleting one record from POA of any appointment and open up to see what error you get.
If an appointment itself is deleted, then deleting an entry from POA should not be a problem.
I hope this help.
Read : https://vjcity.blogspot.com/
Thank you for your reply.
We don't intend to delete an appointment itself, because that's obviously unacceptable to the customer.
We are just thinking about deleting POA records for organizer/attendees.
Business Applications communities