Hi @skoofy5 ,
I can confirm that following your repro steps, I get the same error.
So it's not because of loadNextPage or loadExactPage. Actually has nothing to do with our code.
It happens only when you use the "Advanced Filtering panel", like in your screenshot above, but doesn't happend when you just type something in the search box.
Actually is not happening only with 3rd party PCFs, but also with the out of the box grids. You can use the ribbon "Show As" -> "Read only grid", and test the standard. It's exactly the same behavior.
I've checked what fetchXML is send in the background by the platform.
If I use the search box (which works), I see the following fetchXML in the network protocol:
<fetch version="1.0" mapping="logical" returntotalrecordcount="true" page="1" count="25" no-lock="false">
<entity name="orb_pcftester">
<attribute name="orb_ampel"/><attribute name="orb_prio"/><attribute name="orb_optionsetcode"/><attribute name="statecode"/><attribute name="orb_pcftesterid"/>
<attribute name="orb_name"/><attribute name="createdon"/>
<order attribute="orb_name" descending="false"/>
<filter type="and">
<condition attribute="statecode" operator="eq" value="0"/>
</filter>
<filter type="or" isquickfindfields="1">
<condition attribute="orb_name" operator="like" value="impo%"/>
</filter>
</entity>
</fetch>
If I use the "Advanced Filtering Panel", I see the similar fetch, but page "2", and that's the reason for not finding records:
<fetch version="1.0" mapping="logical" returntotalrecordcount="true" page="2" count="25" no-lock="false">
<entity name="orb_pcftester">
<attribute name="statecode"/><attribute name="orb_name"/>
<order attribute="orb_name" descending="false"/>
<attribute name="modifiedon"/><attribute name="orb_optionsetcode"/><attribute name="orb_prio"/><attribute name="orb_ampel"/><attribute name="orb_pcftesterid"/>
<filter type="and">
<condition attribute="statecode" operator="eq" value="0"/>
<condition attribute="orb_name" operator="like" value="Impo%"/>
</filter>
</entity></fetch>
I hope the product team can help us.
Maybe you can open a support ticket, since the bug can be reproduced with out of the box grids.
Kind regards,
Diana
