fontName and fontStyle have been made available for formElement and all the other tables (systeminformation, window, workspace, etc.) where a font size column was already available. query read_forms($cid: Int!) { useCustomer(no :$cid) { formElement { items { fontSize fontName fontStyle fontStyleFlags } } } } mutation write_forms($cid: Int!) { useCustomer(no: $cid) { formElement_create(values:[{ fontStyleFlags:[Bold,Italic,Underline,StrikeThrough] fontSize : 14, fontName : "Consolas" }]) { affectedRows } } } This will become available in the next release (tomorrow). ... View more

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. ... View more

This wish/idea also applies to /api/v3/SalesOrders ... View more

This also applies for /api/v3/SalesOrders ... View more

Then it would be best to use the Partner Portal with this link. If you don't have access, I recommend to contact us by chat on vismasoftware.no 🙏 ... View more

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? ... View more

I've now tried with insertAtRow as well, and now I'm getting Error: You are not authorised to edit primary keys.   mutation CreateFormElement($customerNo: Int!, $create: FormElement_Insert_Input!, $insertAtRow: FilterExpression_FormElement, $insertPosition: InsertPosition) { useCustomer(no: $customerNo) { formElement_create( values: [$create] insertAtRow: $insertAtRow insertPosition: $insertPosition ) { affectedRows } } } { "customerNo": 1182082, "insertAtRow": { "formType": { "_eq": 6 }, "formNo": { "_eq": 11 }, "lineNo": { "_eq": 2 } }, "insertPosition": "BEFORE", "create": { "formType": 6, "formNo": 11, "x": 4000, "y": 1500, "dx": 7500, "dy": 500, "textOrParameters": "New Element", "justification": 1, "elementType": 1, "fontSize": 10 } } ... View more

Hi!   Thanks for the suggested solution!   We need to see if there is a discount for several of a certain product.   The creation of the orderlines on the temporary order is what takes the longest time even for just a few orderlines the answer from NXT can take up to 20 seconds I've seen. So with a long line of customers in a store this is a problem.   I hope that Visma could provide a query to ask for customer prices for products with different quantity and combinations.   BR ... View more

Perfection! ... View more

I can't see there being any other limitations on creating tokens than the 10k/5 mins. Creating the tokens is done by Visma Connect and is outside the scope of Business NXT. The API will just verify the token, and I don't think it cares how often it changes. ... View more

Is this new API available in documentation? ... View more

Do you have any idea what might be the root cause? ... View more

Yes, it helped. 🙂 ... View more

_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). ... View more

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. ... View more

Hi, I realised I missed a step, thank you! ... View more

I agree the message is obscure. I will add a ticket in our backlog to see how we can improve this. ... View more

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

Thanks Ole, we have created a case for this and will get back to it. ... View more

I second this. This is an implementation detail that we as api consumers should’t have to care about. ... View more

Thanks! My workaround broke this morning, so I figured you had fixed it 🙂 ... View more

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   ... View more

Hi Adrian,   Thanks for you input. Unfortenately I can't keep a client secret secured, that why I use a native app. Still think that the expiration period of a refresh token should be sliding since last use instead compared to the first user consent.   Best regards, Sander     ... View more