Applies to Product - Microsoft Dataverse
What’s happening?
Customers are experiencing slow performance when updating rows in a Dataverse table via a Logic App, with operations taking approximately 9 seconds, which is impacting overall efficiency.
Reason:
The slow performance during the update operation is attributed to the design limitations of the system, particularly when synchronizing large volumes of data, such as 17 million annotation records. The process has been observed to be slow due to the significant amount of data being processed and returned from SQL, which includes large fields like DocumentBody and FileBody.
Resolution:
It is recommended to use the Standard Logic App instead of the Consumption Logic App to improve performance.
For further optimization, consider denormalizing fields that are causing slow queries, such as:
- Creating new fields on the primary table to store frequently accessed data directly, rather than relying on lookups that require additional queries.
- Limiting the number of columns retrieved in queries to only those necessary, as retrieving too many columns can lead to performance degradation.