Hey,   Seems like distinct values are missing from the new aggregates method. ... View more

Hey,   I'm fetching all available companies for all customers in a single query, but for users with access to heaps of customers this is taking a lot of time.   It looks like that this query executes in sequence instead of parallel. Any suggestion on how I can fix this? It does seem like that executing it using batchRequest has the same issues.   In this sample I'm fetching the same over and over, but in my actual use case I'm fetching companies for all available customers. For each additional availableCompanies I add to the query, it adds around 100ms to the response time.   query availableCompanies { availableCompanies { items { vismaNetCompanyId name vismaNetCustomerId organizationNo } } a_2: availableCompanies { items { vismaNetCompanyId name vismaNetCustomerId organizationNo } } a_3: availableCompanies { items { vismaNetCompanyId name vismaNetCustomerId organizationNo } } a_4: availableCompanies { items { vismaNetCompanyId name vismaNetCustomerId organizationNo } } }   ... View more

Would be helpful if the textTypeNo could be included on hover in the docs.     ... View more

Hey,   I'm fetching some aggregated data, but according to the docs the _aggretate-nodes are deprecated and will be removed. The data I'm fetching does not use groupBy, and thus the new method throws an error.   Would simplify things if the new approach worked without grouping.   Works like a charm   query AggregatedOrderSummary($cid: Int!, $dateStart: Int!, $dateEnd: Int!) { useCompany(no: $cid) { order_aggregate( filter: {_and: [{orderDate: {_gte: $dateStart}}, {orderDate: {_lte: $dateEnd}}, {customerNo: {_gt: 0}}]} ) { count { orders: orderNo } } } } { "data": { "useCompany": { "order_aggregate": { "count": { "orders": 232 } } } }, "extensions": { "vbnxt-trace-id": "0000000000000000ac82fe3b47675fee" } }     Not working   query AggregatedOrderSummary($cid: Int!, $dateStart: Int!, $dateEnd: Int!) { useCompany(no: $cid) { order( filter: {_and: [{orderDate: {_gte: $dateStart}}, {orderDate: {_lte: $dateEnd}}, {customerNo: {_gt: 0}}]} ) { items { aggregates { count { orders: orderNo } } } } } } { "errors": [ { "message": "Error: SQL command no. 3010 failed.Database error.", "extensions": { "data": { "status": 2, "status_name": "DatabaseError" } } } ], "data": { "useCompany": { "order": { "items": null } } }, "extensions": { "vbnxt-trace-id": "000000000000000075873a15a5b0ddac" } }     ... View more

Hey,   There's a logical issue when using _in. When the array is empty i expect it to be false, but instead it returns all rows.   So just for the sake of a demo I'm setting the sellerOrBuyer to 999 here, so that we know that it won't return any, but this might be due to some other filter in the real world.   When order in this example returns 0 rows I would expect sellerDetails to do the same, but instead it returns all rows.     query IssuesWith_InSample($cid: Int!, $sellers: [Int!] = []) { useCompany(no: $cid) { order(filter: {sellerOrBuyer: {_gt: 999}}, first: 3) { items { sellerOrBuyer @export(as: "sellers") } } sellerDetails: associate(filter: {employeeNo: {_in: $sellers}}) { items { employeeNo name } } } }     I understand that this will be a breaking change to fix, but I'd like to argue that we're not past the point of breaking changes with bnxt yet. ... View more