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

Yes, it helped. 🙂 ... View more

Thank you for the help, Arnstein. The error stopped after you added the missing Exchangerate Table. ... View more

Hi, I realised I missed a step, thank you! ... 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 can confirm that our queries now seems to return the expected result with and without paging, so it looks good from our end. Thanks! ... View more

I have not had any issues since that. Thank you! ... View more

Hi @David Tandberg-Johansen, You are right, we have had a few issues lately with GraphQL that do not really qualify as incidents (and hence we should not inform about them in status.visma.com), since they were bugs in our application that affected a few customers. At the moment we do not have a web site dedicated to this purpose, so I think we could be better at informing here in the forum. We are focusing on improving the quality of our application and hopefully there won't be too much to inform about going forward. ... View more

Thanks, it works now. ... View more

Thank you for your reply.   My comment was not related to the absolute best performance, but a more performant way to fetch data than going through VBS for every request. I think wiring up all the queries and joins manually for a complex system as VB will take so much time that the API is obsolete before it's done, and with the performance in existing ORMs I see no reason to invent the wheel again.   I'm mentioning specifically EF Core because that's what I have experience with and have been tinkering with using the Business data model, scaffolding and GraphQL. Dapper or other ORMs might have scaffolding solutions, but I know nothing about that.   I think the API would benefit tremendously by skipping the VBS for queries that don't access calculated fields. This would probably also lower the compute power required to run the API-solution, as much of the query can be off-loaded to the SQL-server(s). Computed fields can be fetched using a data loader using primary keys. I'm seeing a 10x improvement in query times using the SQL+dataloader approach over the implementation in nxt, using approximately the same dataset.   I'm happy to demonstrate this over teams. ... View more

Thank you, thank you, thank you, thank you!! ... View more

I didn't include the comma 🙂 But I don't currently have access to a user with access in vb nxt so that must be the issue, I only have the service application created on developers.visma.com + an existing user in vb nxt with the matching client id username.   So it seems I must request access to vb nxt, thanks for the quick help 🙂 ... View more