I believe I reproduced what you're describing (although maybe a bit differently).   I created and order with a single line, quantity 10. The order looked like this: { "data": { "useCompany": { "order": { "items": [ { "orderNo": 1489, "orderDate": 20240319, "joindown_OrderLine_via_Order": { "items": [ { "orderNo": 1489, "lineNo": 1, "productNo": "101", "quantity": 10, "finished": 0, "finishDateAsDate": "0001-01-01", "finishAtAsTime": "00:00" } ] } } ] } } } } Next, I ran the mutation you shown, trying to finish 10. The result I got was: { "data": { "useCompany": { "mutationResult": { "affectedRows": 1, "items": [ { "finished": 0, "finishDateAsDate": "0001-01-01", "finishAtAsTime": "00:00" } ] } } } } This means nothing was finished. If I read the order again, I get the same values as previously: "items": [ { "orderNo": 1489, "lineNo": 1, "productNo": "101", "quantity": 10, "finished": 0, "finishDate": 0, "finishDateAsDate": "0001-01-01", "finishAtAsTime": "00:00" } If I run the finish processing mutation finish_order($cid : Int!, $ono : Int!, $pno : String) { useCompany(no : $cid) { order_processings { finish( filter: {orderNo:{_eq : $ono}}, args : { finishType : 2, group : { key : $pno, quantity : 10.0 } } ) { succeeded items { handledOrderLine { lineNo finishedNow } } } } } } it is reported that 10 items were finished: { "data": { "useCompany": { "order_processings": { "finish": { "succeeded": true, "items": [ { "handledOrderLine": [ { "lineNo": 1, "finishedNow": 10 } ] } ] } } } } } But when I read the order, it looks like the quantity is unchanged, and nothing is finished: "items": [ { "orderNo": 1489, "lineNo": 1, "productNo": "101", "quantity": 10, "finished": 0, "finishDate": 0, "finishDateAsDate": "0001-01-01", "finishAtAsTime": "00:00" } This is not a GraphQL issue. But we need some input from someone that knows better (than me) the business logic here. ... View more

Distinct is available for now only in the old table_aggregate fields. ... View more

I understood this problem was resolved with the support team. ... View more

This problem is now fixed. https://docs.business.visma.net/docs/releasenotes ... View more

This problem is now fixed. https://docs.business.visma.net/docs/releasenotes ... View more

OK. We can make it without returning an error. ... View more

I get your point: in the context of @export, it's not an error, because the array was evaluated. But if you pass an empty array directly, would you consider it an error? Would you expect a message that your argument was incorrect? Or would you expect an empty result, and nothing about the cause?   Yes, we can do it so that an error is not returned, but I see pros and cons for it. ... View more

We can't just return no data, we should also indicate the problem. So you get an error message back. It would look like this:   { "errors": [ { "message": "The array argument for the _in operator is empty.", "path": [ "useCompany", "associate" ], "extensions": { "details": "GraphQL.ExecutionError: The array argument for the _in operator is empty." } } ], "data": { "useCompany": { "order": { "totalCount": 0, "items": null }, "sellerDetails": null } } }   Seems good? ... View more

Thanks for reporting it. I will investigate the problem. ... View more

You are correct. There should be nothing to return. Will look into it. ... View more

This is due to a change we did for performance improvement in GraphQL. Previously, we would be selecting entire rows, no matter now many fields you wanted from a table. Now, we are only selecting exactly what you ask for. However, if you ask for nothing, you get nothing. Therefore, you cannot have join-only fields in the schema, such as here: taxAndAccountingGroup { items { joindown_TaxAndAccountingInformation_via_TaxAndAccGroup { items { joinup_TaxCode_via_TaxCodeSales { joinup_Vat { rate } } } } As you figured it out, it works, if you add at least one field. But you did that do that with joinup_TaxCode_via_TaxCodeSales. Here is a query that works: query GetTaxAndAccountGroups($cid: Int!) { useCompany(no : $cid) { taxAndAccountingGroup { totalCount items { taxAndAccountingGroupNo description joindown_TaxAndAccountingInformation_via_TaxAndAccGroup { totalCount items { taxAndAccountingGroup description joinup_TaxCode_via_TaxCodeSales { taxCode joinup_Vat { rate } } } } } } } } Result: { "data": { "useCompany": { "taxAndAccountingInformation": { "totalCount": 8, "items": [ { "taxAndAccountingGroup": 1, "description": "Avgiftspliktig høy sats", "joinup_TaxCode_via_TaxCodeSales": { "taxCode": 3, "description": "Utgående MVA - høy sats", "joinup_Vat": { "rate": 25 } } }, { "taxAndAccountingGroup": 2, "description": "Avgiftsfritt", "joinup_TaxCode_via_TaxCodeSales": { "taxCode": 4, "description": "Avgiftsfritt salg innland", "joinup_Vat": null } }, ... View more

Thank you for reporting. I am looking into it. ... View more

What exactly do you mean? Do you want to find whether it's possible to do insert, update, or delete for a particular table? ... View more

Do you mean like this? query gl_balance_multiple_dimensions { useCompany(no: 1234567) { generalLedgerBalanceForOrgUnit1(filter: { year: { _eq: 2023 } }) { items { accountNo year period cbDomestic orgUnit1 } } generalLedgerBalanceForOrgUnit2(filter: { year: { _eq: 2023 } }) { items { accountNo year period cbDomestic orgUnit2 } } } } ... View more

This is a bug. We will investigate and fix it. ... View more

This is a bug. Thank you for reporting it. We will investigate and fix it. ... View more

Thanks for reporting this. I have added it to our backlog. ... View more

Unfortunately, this is not working as you expect. The reason for that is the framework we are using (graphql-dotnet) parses the input into a dictionary, where there property is the key. However, the dictionary is sorting the keys lexicographically, so they appear in alphabetical order.   To change this, we need to make significant changes in the framework, which was not something we were willing to do.   The same problem we had when evaluating a request like this: orderLine_create(values:[{ orderNo : 855 productNo : "405" unit: 1 orgUnit1: 1 orgUnit2: 1 taxCode: 3 quantity : 2.0 currencyNo: 47 priceInCurrency: 14.0 discountPercent1: 0.0 description: "Kvikklunsj, 22.04.2023 16:58 - 23.04.2023 12:00, Refnr.:" }] The framework read all these object properties and put them in a dictionary. We fixed this by ditching the graphql-dotnet parsing and do it all explicit (which led to some bugs over time).    Bottom line is, we will add this to the backlog and see what we can do to make it work.   There is a workaround in the meantime. Don't pass an object as variables, but individual properties: query: mutation create_order($cid : Int!, $custno : Int, $ordType : Int, $ordPref : Int, $info5 : String, $info6 : String, $ttype : Int, $ourref : String, $yourref : String) { useCompany(no : $cid) { order_create(values: [{ customerNo : $custno orderType : $ordType orderPreferences : $ordPref information5 : $info5 information6 : $info6, transactionType : $ttype, ourReference : $ourref, yourReference : $yourref }]) { affectedRows items { orderNo } } } } variables: { "cid":xxxxxxxxxx, "custno":10290, "ordType":2, "ordPref":0, "info5":"1", "info6":null, "ttype":1, "ourref":"test@griegconnect.com", "yourref":"Ref tjeneste" }  This should work as expected. ... View more

What have you tried? What didn't work? What did you get? ... View more

This is not a feature we can provide at the time being. However, it's something that has been discussed and might be made available in the future. But I cannot tell you estimates on that. ... View more

Yes, I understand that not everything is plain forward and need to read the documentation for different things. But I don't think there are many APIs that you can use without going through the docs.   That doesn't mean we don't want to improve. We've been opened to ideas. So if you can explain with examples what you suggest I'll look into it. But honestly, the title and phrases like "using the suggest:-functionality" are confusing to me and I don't understand what you really want. ... View more

Both System.Text.Json and NewtonSoft allow you to ignore properties that are null. Here is an example of how to do that: https://stackoverflow.com/questions/6507889/how-to-ignore-a-property-in-class-if-null-using-json-net.   Actually suggest works exactly on null, because that's the only value that can be assigned to any field, regardless the type. ... View more

I don't really understand your question, how exactly this is supposed to work. Perhaps you can elaborate on what you are asking for. ... View more