Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
For guidance about general things to avoid when composing Dataverse queries, see Query anti-patterns.
You can use FetchXml with the Dataverse Web API. In that case, see Optimize performance using FetchXml
Automatic query optimization
Don't be surprised when the performance of a slow query improves without any change on your part. Dataverse actively monitors data retrieval operations to improve performance. When a specific query using standard tables performs poorly, Dataverse might automatically make changes that improve the performance of the query. This behavior might make certain performance issues appear transient because they can't be reproduced later.
Automatic query optimization doesn't require any configuration. It's enabled by default for everyone.
See also
Query data using OData
Select columns using OData
Join tables using OData
Order rows using OData
Filter rows using OData
Page results using OData
Aggregate data using OData
Count rows using OData
Query anti-patterns