Maximum records in a query

[titobcn]

Hello,
I have a query with more than 2000 records, when I want to save the view it doesn't let me and I get the error "Number of conditions in query exceeded maximum limit."
What can I do to be able to save the view with all the records that I have made through the fetch?
Thank you

[rappen]

I'm curious - can you actually execute the query in FXB? And it works?
Error message, will it stop you from the server? Screenshot?

[rappen]

Ok, so the error message is not from our tool, it's from the Dataverse.
Is it not possible to create the query with joins of the filtering?
Generating a query with a bunch of guids is not so secure, since you don't really know when it will hit the limit of number of conditions.

[titobcn]

Wow...so what can I do?

[rappen]

Can you share your queries? If too sensitive to share publicly, can you email me?
Just to get an idea of what we need.

[titobcn]

You can provide an email
Thanks!

[rappen]

jonas at jonasr dot app

[titobcn]

Have you been able to see the file?

[rappen]

Yes.
This filtering is not possible with that many filters. Can't do.
I'm thinking about how to find all these emailaddresses?
I understand through Office, you should probably set a flag in these contacts with Power Automate, and make the filtering a lot easier in the query:

<fetch>
  <entity name="contact">
    <!-- attributes -->
    <order attribute="ab_aplicacionorigen" descending="false" />
    <filter type="and">
      <condition attribute="statecode" operator="eq" value="0" />
      <condition attribute="ab_aplicacionorigen" operator="eq" value="{8437AA9C-D384-E811-80D9-005056BD6621}" />
      <condition attribute="ab_officesegment" operator="eq" value="true" />
    </filter>
  </entity>
</fetch>

(see the last condition above)

[titobcn]

Hello,
At the end I am going to export the contacts, update and import again.
It is the only feasible solution to unravel the project.
We are limited with the dataverse.
Thanks for the help!

[rappen]

Thanks and good luck! 🤓