Personalized Community is here!
Quickly customize your community to find the content you seek.
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
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
We installed CRM 2011 in 2013 and had been using it since then. Now, as the number of records got increased tremendously, as part of cleanup, we want to delete the old records. The tables have parent-child relationship, restrict delete relationship and dependency on same tables as well (i.e., sort of parent-child relationship within the table).
With these complications, for most of the tables, on an average, the CRM API based deletion is taking about 20 seconds to delete a record.
Even with CRM tool, manually, it is taking almost the same time.
For bulk deletion of records from CRM tables, is there any other safe way of quick deletion ?
Also, can we delete the records using SQL Delete operation ? What are the problems that we might face if we delete this way ?
We first use View or Advanced Find to list the records we want to delete, then export the records to Excel and delete the records in bulk in the Excel file, finally import it into CRM.
Please refer to these two articles:
If your problem is solved, please click "Yes" to mark the verified answer. This will help other users with the same theme, if they have the same problem, they can refer to this post directly.
Hope this helps.
Any supported deletion mechanism (UI, bulk delete, CRM API) will need to check the relationships, so will take a similar amount of time.
I can think of 3 possible ways to improve this:
Or, is it viable to consider upgrading to CRM 2013, then deleting the records. In CRM 2013 the ExtensionBase and Base tables are merged into one table, which may well improve delete performance (by reducing locks, and simplifying the query optimisation). However, it's difficult to predict how long the upgrade would take to run
Business Applications communities