In this blog post, we’ll explore the four common bulk operation errors frequently encountered in Dataverse within the Power Platform environment. Before we begin, ensure you subscribe to CRM Crate to remain informed about the latest developments in the Power Platform field.
Power Platform is a suite of Microsoft tools designed to empower users—both technical and non-technical—to build apps, automate workflows, analyze data, and create virtual agents with minimal coding. It includes four main components: Power BI for data visualization and analytics, Power Apps for building custom applications, Power Automate for automating business processes, and Power Virtual Agents (Copilot) for creating intelligent chatbots. At the heart of Power Platform is Dataverse, a secure and scalable data platform that allows users to store and manage data used by business applications. Dataverse provides a unified data schema and integrates seamlessly with Microsoft 365, Dynamics 365, and other services, enabling consistent data management and governance across the organization.
What are the different types of bulk operation errors in Microsoft Dataverse?
Bulk operation errors in Microsoft Dataverse typically occur due to issues related to system performance, data integrity, and concurrency. One common cause is processing large volumes of data simultaneously, which can overwhelm system resources or exceed timeouts. Errors may also arise when multiple operations try to access or modify the same records at the same time, leading to conflicts or deadlocks. Additionally, custom plug-ins or workflows that are not optimized for bulk operations can introduce delays or failures. Poorly structured data, such as missing required fields or invalid references, can also trigger errors during bulk imports or updates. Overall, these errors stem from the complexity and scale of operations exceeding the platform’s processing capabilities or violating data rules.
Sql error: Generic SQL error
Error Code: -2147204784
Sql ErrorCode: -2146232060
Sql Number: 1205
Error Message: Generic SQL error. CRM ErrorCode: -2147204784 Sql ErrorCode: -2146232060 Sql Number: 1205
In Power Apps / Dynamics 365 CE the “Generic SQL error” can occur when multiple concurrent operations attempt to update the same record simultaneously. This typically happens in high-traffic environments or during automated processes like workflows, plugins, or integrations that don’t properly handle concurrency. SQL Server enforces data integrity by locking records during updates, and if another process tries to modify the same record before the lock is released, it results in this error.
Sql error: SQL timeout expired
Error Code: -2147204783
Sql ErrorCode: -2146232060
Sql Number: -2
Error Message: SQL timeout expired. CRM ErrorCode: -2147204783 Sql ErrorCode: -2146232060 Sql Number: -2
The error “SQL timeout expired” typically occurs when a database operation takes longer than the allowed time limit to complete. This is often due to large batch requests that overload the SQL server, causing it to exceed the timeout threshold. Such operations might include bulk data imports, complex queries, or inefficient custom code that doesn’t scale well with data volume.
Sql error: The transaction of the SQL command has already been rolled back or committed
Error Code: -2147220907
Error Message: The transaction of the SQL command has already been rolled back or committed; this is usually caused by a swallowed SQL deadlock exception.
The error “The transaction of the SQL command has already been rolled back or committed” typically occurs due to a deadlock situation, often when multiple concurrent operations attempt to update the same record. In SQL Server, a deadlock happens when two or more processes block each other by holding locks on resources the other processes need. Once SQL Server detects a deadlock, it automatically rolls back one of the transactions to break the cycle, resulting in this error.
Error “There is no active transaction”
Error Code: -2147220911
Error Message: There is no active transaction. This error is usually caused by custom plug-ins that ignore errors from service calls and continue processing.
The error “There is no active transaction” typically indicates that a piece of custom code, most often a plugin, is attempting to perform a database operation outside the scope of a valid transaction. This issue is not exclusive to bulk operations; it can occur in any scenario where a plugin or custom workflow tries to access or modify data without being properly enclosed within a transaction context & by custom plug-ins that ignore errors from service calls and continue processing.
