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

The fix is in production. Please try it again and let us know if your problem is solved. ... View more

I do get an error, but something else: { "errors": [ { "message": "Unable to cast object of type 'System.Object[]' to type 'System.IConvertible'.", "path": [ "useCompany", "associate_update" ], "extensions": { "details": "GraphQL.ExecutionError: Unable to cast object of type 'System.Object[]' to type 'System.IConvertible'." } } ], "data": { "useCompany": { "associate_update": null } }, "extensions": { "vbnxt-trace-id": "0000000000000000aed2f5535fa82f2f" } } Works if I put the value in the query.  The variable should work too. We will fix this. ... View more

Export to array is now available: https://docs.business.visma.net/docs/features/directives#the-export-directive   ... View more

Yes, VBus is the backend for BNXT and GraphQL is sending VBS requests to it. Therefore, it is possible that what you suspect is correct. But no, you cannot see what version is running.  ... View more

There is no append/remove operation, only set. You need to read the existing value, add/remove what you want and then perform an update. ... View more

That's a different request, please make a separate topic for it. ... View more

I understand that ideally, you'd want something like this: query read_texts($cid : Int!, $orderNo : Int) { useCompany(no : $cid) { order(filter :{orderNo :{_eq : $orderNo}}) { items { orderNo deliveryMethod deliveryMethod_Text(lang : NORWEGIAN) { text } paymentMethod paymentMethod_Text(lang : NORWEGIAN) { text } } } } } This API is a generic one, built dynamically from the data model. Providing joins to the text table for some particular fields in this fashion is not possible, because there are no join relationships defined between these tables (such as Order in the previous example) and the Text table. As a result, we cannot provide a generic way for making this happen. However, you can read this using two (or multiple requests), using the @export directive (and aliases). Here is an example: query read_texts($cid : Int!, $orderNo : Int, $dm : Long = 0, $pm : Long = 0) { useCompany(no : $cid) { order(filter :{orderNo :{_eq : $orderNo}}) { items { orderNo deliveryMethod @export(as :"dm") paymentMethod @export(as : "pm") } } deliveryMethodName : text(filter: { languageNo :{_eq : 47} # Norwegian textType : {_eq : 5} # delivery method textNo : {_eq : $dm} }) { items { text } } paymentMethodName : text(filter: { languageNo :{_eq : 47} # Norwegian textType : {_eq : 7} # payment method textNo : {_eq : $pm} }) { items { text } } } } This has been documented here: https://docs.business.visma.net/docs/howto/texts   ... View more

Yes, we do have some release notes: https://docs.business.visma.net/docs/releasenotes   ... View more

The fix for this has been deployed to production. ... View more

The fix for this has been deployed to production. ... View more

We have prioritized this to investigate and fix. ... View more

We have added support for including status code names in the response. Example:   { "errors": [ { "message": "A record with the same primary key already exists.", "path": [ "useCompany", "order_create", "values/0" ], "extensions": { "data": { "status": 3, "status_name": "PrimaryKeyAssignmentFailed" } } } ], "data": { "useCompany": { "order_create": { "items": null } } } }   You can read about it here: https://docs.business.visma.net/docs/features/errors#understanding-error-information   ... View more

So you built a LINQ provider for BNXT GraphQL. I think this is a very interesting project, although I don't know how many people would want to use it. But if you are willing to share it, then why not just put it on github, document it a bit more, and we can tell about it to customers so they can try it. ... View more

This is not a correct filter:   filter: { orderStatus1: {_is_on: 1}, orderPreferences: {_is_off: 4}}   It has more than one value so you need to build and expression with _and and/or _or. For instance, if both of these need to be true, then write it as follows:   filter: { _and: [ {orderStatus1: {_is_on: 1}}, {orderPreferences: {_is_off: 4}} ]}    However, it might be easier for you to write the filter using the flag fields:   filter: {_and:[ {orderStatus1Flags: {_is_on: ReadyForInvoicesAndCreditNotes}}, {orderPreferencesFlags: {_is_off: BatchInvoice}} ]}   In the GraphiQL web IDE, you can explore the documentation and see the possible flags and their numerical value for each such flags field. You can read more about that here: https://docs.business.visma.net/docs/schema/bitflags   ... View more

No, it's not read only. It's not available for reading at all. ... View more

T-SQL allows you to escape these wildcards (https://learn.microsoft.com/en-us/sql/t-sql/language-elements/like-transact-sql?view=sql-server-ver16) but this is not a feature that we are currently supported. Therefore, unfortunately, you cannot do this. ... View more

I see you are following up a post that I made some time ago. That probably didn't work in the first place. I recommended that because I knew the table in which it was stored but I wasn't aware the table is not exposed for reading. I am not aware of all the rights on all the tables and I probably recommended a query that never worked. In which case, I apologize for misleading. ... View more

The GraphQL schema is dynamically created from the VB data model, based on access rights for CRUD operations on tables, columns, processings, etc. When things change in the data model they are automatically updated in the GraphQL schema.   I see that this table has the read access set to "none" so it's not exposed for reading. ... View more