Hello, What is the status about rate limiting today? I can't find any documentation about this, nor do I observe any limitations occurring. I started 500 calls in parallel and as far as I can tell from the logs, none of them failed. Does it depend on what the query is trying to fetch? Thank you for your help. ... Mostrar más

What is the status here? We also need the suspension date info and still can't get this information from the API. We wonder how to do it? ... Mostrar más

Perfection! ... Mostrar más

Hey,   I really hope you can have a new look into setting fontName and fontStyle using the API. There is probably an internal processing in vbus that lets you update it, since setting the fields directly through the API is forbidden.   This is starting to become an issue, as when we copy a complete print layout we are not able to set the font name, and when the font name isn't set, it seems that it doesn't care about the font size either.   Consulants and users are actually editing and working with formulas, and changing fonts and fontsize is really important. ... Mostrar más

_Ppn stands for Processing Parameter Node _Rpn stands for Report Parameter Node   There are some additional suffixes. The reason for this is that there were cases with colliding type names which resulted in invalid schema (a schema that didn't reflect well the data model). ... Mostrar más

Just read the docs. Would be useful if when both parameters are defined it would use the lang: NORWEGIAN as a fallback if langNo is not defined or invalid. ... Mostrar más

Hi, I realised I missed a step, thank you! ... Mostrar más

I agree the message is obscure. I will add a ticket in our backlog to see how we can improve this. ... Mostrar más

It's documented here https://docs.business.visma.net/docs/schema/mutations/inserts#insert-between-existing-records but works as described above basically. ... Mostrar más

I want to second this NB. The order of fields assignment is important in BNXT. This is way putting the suggested fields at the end may lead to incorrect results. For this reason we made that feature obsolete a while ago (should be removed actually from our API). Use null as a value to indicate suggest.   voucher_create( values: [ { batchNo: $batchno, voucherNo: null, amountDomestic: 14296.19, debitAccountNo: 7519, valueDate: 20240602, voucherDate: 20240601, voucherType: 50 }, { batchNo: $batchno, voucherNo : null, amountDomestic: 14296.19, creditAccountNo: 2920, valueDate: 20240602, voucherDate: 20240601, voucherType: 50 }] ) { affectedRows } Note that I'm not saying this is the cause of your problem, but it can be the cause of problems in other cases. ... Mostrar más

Thanks! My workaround broke this morning, so I figured you had fixed it 🙂 ... Mostrar más

We have made some changes to that fields that are assigned from unset variables are ignored.  https://docs.business.visma.net/docs/schema/mutations/inserts#assigning-fields-from-unset-variables   ... Mostrar más

Is this still occurring? We deployed last week a fix for a parsing error. It's possible that we have another one. But if you still experience this (as I assume from your question), can you share another trace ID?  ... Mostrar más

Yes, we can add the database type to the model info. We will consider the access rights on tables, columns, etc. too. ... Mostrar más

This problem is now fixed. When you got this message, the problem was a row locked by other process. There was an error in our parsing of this response from the backend.  ... Mostrar más

This was implemeted a while ago. Can also be combined with @export to fetch keys from one table and look them up in another. ... Mostrar más

In my code I do get the correct finished qty if I do a query directly after I have done the mutation but in my view I should not have to do that query because the mutation should project those values back. Could it be that the mutation returns to quickly before the finish processing has been completed ? ... Mostrar más

Distinct is available for now only in the old table_aggregate fields. ... Mostrar más

Ok, then we'll update the queries on our end. ... Mostrar más

This problem is now fixed. https://docs.business.visma.net/docs/releasenotes ... Mostrar más

This problem is now fixed. https://docs.business.visma.net/docs/releasenotes ... Mostrar más

Hey,   This would be incredible useful. Please see if there's any chance to implement it. ... Mostrar más

Haven't heard anything about this issue for a little while. Any plans to address these issues? ... Mostrar más

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 } }, ... Mostrar más

Great, thanks for letting me know. ... Mostrar más

That's great, thanks! ... Mostrar más