Awesome ... View more

Wouldn't that break all queries ala "query x($cid: Int!) { useCompany(no: $cid)..."? Not sure how this can be done backwards compatible. ... View more

Wow! Thank you! ... View more

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

Would also be great if useModel could take a numeric languageNo instead of (or in addition to) lang: Enum. This would let me fetch the correct translations based on the languageNo on an associate. If no match, fall back to the value provided in lang or something that makes sense. ... View more

Thank you! ... View more

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

Turns out I'm not able to update the fontName after all - it's just there in the schema taunting me.   Please let me read and write fontName and fontStyle. ... View more

Enum is the way to go 👍 ... View more

Magnificent! ... View more

Well, this was the issue until I figured that out and just started sending a non-base64-encoded string instead.   The issue with sending the non-base64-encoded string is that base64 preserves the windows-1252 or iso-8859-1 encoding that bnxt uses for its labels, but when I send it through the API they get mangled with the utf-8 encoding.    I've managed to partially work around this by latin1 encoding the data first, but this does not totally solve the issue.   Please fix so that I can send base64 in again. ... View more

That would be really good! ... View more

This makes sense to me. ... View more

Good! Visma added some more logging after I encountered this, so now maybe they’ll be able to figure it out.   The update is successful even though the response says otherwise. ... View more

Please include the visma trace id for this response, as this is bug that I haven't been able to reproduce, but have encountered myself. This is probably an issue somewhere between vbus an graphql, and must be investigated by Visma. ... View more

I think the bigger issue is that this has been changed without any notice, no release notes, no heads up for integrations to change. We only notice when the integrations blow up after a release has been done, without notice. ... View more

Hey, This is probably in regards to Visma moving away from VBS - a change we were suppose to not notice at all. Your mutation is updating with empty values. If you want to maybe update some fields, you should have the whole entity as a parameter instead. At least that's your workaround until Visma (maybe) fixes this.   mutation UpdateCompany($companyID: Int!, $customerNo: Int!, $entity: Associate_Input!) { useCompany(no: $companyID) { associate_update(filter: {customerNo: {_eq: $customerNo}}, value: $entity) { affectedRows } } }   { "companyID" : 4000000, "customerNo": 11000, "entity": { "phone": "94000000" } }   The drawback here is that if you are using dotnet you need to make sure that your serializer is set to not include NULL-values, or you'll be in for a surprise with suggested values. ... View more

The sample code I presented at ISV Partner day today is available at https://git.new/bnxt-hooks. Install the Connect Application Access window from NXT Ninja to start setting up webhooks.   But webhooks is not working at the moment, unfortunately, so no need to start playing with this yet. I'll update this thread when I see that it's up and running again. ... View more

Hey Sander,   You should use a service application instead of a web-application for this use case. Access to your app will be granted through the app store, and you won't have this problem.   This will let you authenticate using client_credentials with a tenant id instead.   ... View more