Applies to Product – Microsoft Dataverse
What’s happening?
Customers are experiencing querying issues where the query on an attribute has exceeded the maximum supported depth of filters.
Reason:
This is caused by a configuration change that affected where the value for the maximum depth of filters is stored. The value was not migrated successfully, leading to the default value being used instead of the intended increased value.
Resolution:
- Simplify the query by reducing the number of nested filters or breaking it into smaller parts.
- Ensure that the configuration value for the maximum depth of filters is set correctly. The value should be increased from 25 to 78 to support the way data is loaded.