to get a personalized navigation.
to get a personalized navigation.
Hi
After yesterday, we get duplicate rows when paging in GraphQL. We have seen this both in Freeinf1 and freeinf2.
When running this query in GraphQL and retrieving all the pages:
query VBNxtQuery($id: Int!, $cursor :String){
useCompany(no: $id) {
freeInformation1(first: 1000, after: $cursor , filter: { _and: [ {freeInformationCategory: { _eq: 1}} {freeGroup2: { _eq: 9}} ]}) {
totalCount
pageInfo {
hasNextPage
endCursor
}
items {
primaryKey
}
}
}
}
We get the correct amount of rows as in VB NXT, but about 1/4 of those are duplicates (two of the same primaryKey).
We have seen this problem in several of our queries and this is a critical issue.
We deployed a fix for this half an hour ago, so the behavior should be correct now.
I can confirm that our queries now seems to return the expected result with and without paging, so it looks good from our end. Thanks!
Any updates on this, other than the work around to add sorting to the query? Have you been able to narrow down the scope for this bug? Breaking the paging/cursor is quite critical for getting data.
Copyright © 2022 Visma.com. All rights reserved.