You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When adding the top tag to the fetchxml string I always get the error
"Error: The top attribute can't be specified with paging attribute page"
I just added to line 875
if (pageNumber < 0) replacementString = '$1 ';
When I call executeFetchXml(entityname, sFetchXML, null, -1, null) it seems to work.
The text was updated successfully, but these errors were encountered:
hi @pyro-mm , I remember I had to include a paging number in every fetch request because I wanted to retrieve a paging cookie and for some reason it was not doing it back in 8.2 without adding a "paging" attribute to fetch xml, I don't know if it's fixed right now, did not test it.
To be honest, I did not take into account the fact that devs can use "top" inside a fetch xml as well. So, I am going to make some changes and publish a patch asap.
When adding the top tag to the fetchxml string I always get the error
"Error: The top attribute can't be specified with paging attribute page"
I just added to line 875
if (pageNumber < 0) replacementString = '$1 ';
When I call executeFetchXml(entityname, sFetchXML, null, -1, null) it seems to work.
The text was updated successfully, but these errors were encountered: