It seems like there should be native support for batching in graphql-dotnet (https://github.com/graphql-dotnet/server/pull/241/files), but the API returns with a 500 error when I try it. Maybe there is some kind of body validation in nginx or in a middleware that breaks the functionality? ... View more

The best way to solve this is still to use operation batching (https://community.visma.com/t5/Diskusjon/Please-enable-operation-batching/td-p/580571), but it doesn't work with the API as of yet.    I've found an open GraphQL that supports batching in a sensible way. @Marius Bancila have a look at how they've solved batching in https://countries.trevorblades.com/graphql using the following body:     [{ "query": "query Query($country: ID!) { country(code: $country) { name } }", "variables": { "country": "NO" } }, { "query": "query Query($country: ID!) { country(code: $country) { name } }", "variables": { "country": "SE" } }, { "query": "query Query($country: ID!) { country(code: $country) { name } }" }]     The last query will fail since it's missing "variables". This will return the following response:     [ { "data": { "country": { "name": "Norway" } } }, { "data": { "country": { "name": "Sweden" } } }, { "errors": [ { "message": "Variable \"$country\" of required type \"ID!\" was not provided.", "locations": [ { "line": 1, "column": 13 } ] } ] } ]     I think this is a sensible approach. ... View more

https://community.visma.com/t5/Diskusjon/API-Updates/td-p/582556 ... View more

This should be possible using GraphQL batching, but I don't think it's enabled from Visma's side.     This will create a request like the one below, and the API returns a 500 error.        ... View more

Bonus for making it work together with the export directive. ... View more

What Florian is really asking is that you provide some documentation around rate limiting and what you consider best practice for working within the limits.   I think all of us consultants will appreciate it if you could shine a light on how rate limiting is implemented and enforced. ... View more

Hey,   Time for another update here.   I've added support for ChatGPT, and you can now get help with converting your SQL queries into GraphQL queries. Go to https://model.vbnxt.rocks/ai and add your openai key and get suggestions on how to convert your queries. I highly recommend you use GPT-4 as gpt-3.5-turbo will struggle with longer sql queries.   It will goof up sometimes (many times..), but just paste the error message you get from the API and it will adjust the suggested query. ... View more

Please include the call you use to create the order head as well. ... View more

I don't see any reason for skip and after to be used together, really. I'd use skip/first for pagination and first/after for going through a complete data set. I'm not seeing the use case for them being used together, but if it's easier to support it I see no reason not to. ... View more

Skip seldom make sense alone. All I'm asking is that you build in skip/first before you decide to change the after/before to something else. This enables me to create a traditional pagination with number of pages etc, and it works well in the current setup. ... View more

I’m using this for local mirror compatible with existing queries. ... View more

I have this as an internal api if it’s something you need. ... View more

Ok. So this is more like access to Visma.BusinessModel.xml through the api? ... View more

Will this be able to return user defined translations as well? I think "definitions" or just "model" is a better name than useModel, as I don't see how "use" fits in this context.   query { useCustomer(no: X) { definitions(language: USER_DEFINED) { tables(tableNo: 42) { ...TableDefinition } } } } ... View more

So how can we include the core team in this discussion going forward?    Øyvind, have you raised this issue already? Any feedback? ... View more

What we have today is already the latter that you don't prefer (and this is one of the support tickets from a confused user, myself.). I'm not asking for the ability to write to fields like ePw etc, but rather setting values in fields like orderType or voucherSeriesNo to values that are not available to users.   This would not be a change in the schema, but an ability to set values that are not accessible as a user. Maybe this could be a flag on the client id in the developer portal? Or maybe a setting on the access in "Connect application"?   I suspect that this is a core issue with Business though, and not an issue with the API. ... View more

Would be cool if you could implement skip/take before changing after to something else. It's working as expected for me now, so when/if you change from base64(index) please consider adding skip: index. ... View more

I just copied a quote off the internet. Neither you or I can do anything but wait for Visma to fix this. It’s up to them to fix the issues with the proxy.   It’s not uncommon to have a smaller limit for what you can upload than what you can download.   Maybe Marius/Visma can give us an update on how the implementation of blob storage is going? ... View more

"The nginx default file upload size limit is 1 MB; if suppose the user uploads a file which is more than 1 MB, then the user will get the 413 error, i.e., entity request is too large. We can increase the max size of the upload limit in nginx by using the directive of client_max_body_size."   This is an issue in the reverse proxy Visma is using. ... View more

Alright, so after digging in for a minute it seems that after is just a base64 version of skip. I'm content then 😀   Cool if you can confirm, Marius 😎 ... View more

Hey,   I'm not quite sure what you mean? You can't use SQL names with the GraphQL API, and that's why I've made this tool. It makes it much easier to convert from legacy systems to vb nxt.   You can either paste a SQL query or you can just use it to lookup different tables or fields that you need. If you have a different use case that I haven't thought of, just let me know 🙂   Cheers ... View more

Hey,   An update on the Visma Business Model Browser.   * You can now copy whole tables to clipboard. Hold down shift or control if you feel nostalgic and want the Sql names as aliases. * It now shows if a value is read-only or not accessible at all * Fields with a text type now shows the text type number * Enum fields has the option to list the available values for that field * Flag fields has the option to list the available values and calculate the correct value based on the selected flag. You can also enter a value to see what flags are active on a field.   Cheers ... View more

I think this actually is part of a bigger issue with the API-implementation. The API is treated as a user, and access to fields and values that would be useful for an integration but not a user in the UI is not available.   Another example of this is voucherType on voucher where a voucherType might be protected from being used manually ("sperret"), but it would be good to be able to set this through the API and still have it disabled for end users. I also want to set origin on batch, but that's read-only in the model.   I understand that these are limitations in the core of Business and not the API per say, but I think that this is an issue worth discussing. ... View more

Wow! Awesome! ... View more

I think there's a bug with DateTimes and _gte. Try something like this instead, with the added benefit of checking on ms instead of minutes.   filter: { _and: [ { _or: [ { changedDate: { _gt: $lastModifiedDate } } { _and: [ { changedDate: { _eq: $lastModifiedDate } } { changeTimeInMs: { _gte: $lastModifiedDateMs } } ] } ] } { processingMethod7: { _gt: 0 } } ] }   Remember that processingMethod7 is a flag-field, so you should check for bit values instead of just equals. To check if flag 1 is on do processingMethod7  & 1 = 1 in your code. ... View more

Add Employee to this wish-list and add the option to filter as well. ... View more