Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
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 | Talent TechTalks | Upcoming 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