This might be related to size of the data being fetched, network traffic etc. Since pagination is not properly working while filtering with Attributes, we understand that clients are unable to narrow the data scope to avoid timeouts.  Do you have a retry mechanism in place ? If so, how frequently you're receiving timeouts ?  ... View more

According to the specification, refresh_token is optional. A client requiring it is non conforming. Extra fields are indirectly allowed "typically along with some additional properties about the authorization."   So having both "token" and "access_token" is fine according to the standard but I assume Hyrum's law applies as well.       ... View more

Thanks for the confirmation 🙂 ... View more

That sounds like a good idea, if this is an improvement you'd like to see. Please post it in the "Ideas" part of the forum.  ... View more

Indeed, good to hear that it works! ... View more

I see it in the same way as stored procedures vs queries when dealing with database access.   There are cases where it is ok to expose your internal data structure. Adding an extra layer can then be an unnecessary maintenance burden. GraphQL and similar interfaces will play a role in places where you control the entire chain from data- to presentation layer.   But I don't think it is a good fit for general API:s where you give 3rd parties access to your functionality. It puts to much burden on the consumers for understanding your data model. If you have ever had to use an OData interface into someone else's system you know what I mean 🙂   You can of course create a GraphQL API which is independent from your data model but then I'm not sure what you really gain compared to REST.   (Disclaimer: I create REST interfaces at least every month and the design goal is always to expose an API which makes sense for the consumer independent of the data layout. Have also created OData interfaces in the past and found that it worked best for reporting and other data extraction scenarios. Many BI tools can read OData out of the box and I assume it is the same for GraphQL) ... View more

Visma.net Financials API updates for version 8.43.0 (April 2021) ... View more

The Idea will be followed on: Extend Sales Order Endpoint PUT operation's SOOrderLine pointer with "External-Link" Field ... View more

Thanks, Florian, and we're sorry for the issues this has caused. ... View more

b64() can be used with GET operations. ... View more

Yes we are using the API. We changed now the user-roles than we will see if we still get duplicates... ... View more

Thank you,  great! ... View more

Hi,   now I spent over 1 hour for testing this and you are right. As far as the receipt quantity on all lines is the same as the number of serialnumbers we try to read than this works.    This is also the cause why it worked before but not in this special case. In the actual receipt we had to lines with serialnumber-items but the files with the serial number we get for each inventory-number. So far we always had just 1 line with a serial-item.   BUT: The behavior in the API is not the same as in the UserInterface. As far as the Receipt is on hold its fully possible to add serialnumbers so many as you want and on the lines as you want. Its just not possible to change the Status to balanced if you not have registered all serialnumbers. This is also a bug in the API. It does not help either to explicitly send hold = true once again with the PurchaseReceiptUpdateDto. Nice if development could fix this because otherwise we have to copy and paste the files with the serialnumbers together to 1 file.    Florian   ... View more

There is a case in the backlog for this, however we don't have any influence over when the implementation will be done, as soon as we here anything we'll inform you.  ... View more

Ok, please let us know if we can do anything else. ... View more

And: than we also have solved the timing problem... (from the other post) ... View more

Thanks for the detailed answer.    So far we think we can use the addressinformation directly from the Supplier Endpoint. I still don't understand why these VAT-supplier locations are accessible through the API. We have checked that they are not extended to/as customers either, But on the other side - if this is bug - its maybe a bit problematic to count on this possibility to get around the missing funcionality. Just now we don't have a full overview yet if we really need to get the location information or if its enough to get the mainaddress from the supplier.   Florian ... View more

I can confirm that this works.  Florian ... View more

As you mentioned, opening a new browser should definitely do the trick since it'll have its own session skipping the CSRF prevention. Anti-Forgery Tokens may not be provided and that's why Dashboard is not allowing those redirections to Start Page where Visma.Net user has already logged in. ... View more

Hi,    yes thank you. But I hope you understood why we are to doing so even if you not recommend it. Otherwise we have to introduce a new parameter here in the portal which has to be setup correct dependend on the setup of the number series in Visma.Net. It would be nice and easier if this always would work like expected.   Florian ... View more

Yes you are right. Sorry this was a bit of confusion about the types since the UI and api not matches here.        Florian ... View more

I agree the issue have to be fixed - and wait for V2 -- but it applies for all endpoints with pagination so some work to do for Visma.   It would actually help with totalCount in header; because now I have no idea how many calls to do. I get empty json and 200 when calling the first page. In this case I also get empty json and 200 when calling the next 30 pages. I also get empty json and 200 when calling non-existing page 55. So how to know when to stopp trying? At least if I knew there are 3197 records; I could call only 32 pages of 100.   totalCount in header would be a pain killer while waiting for the real treatment -- V2 ... View more

Are you still getting the 502's? ... View more