About Magnus Johnsen

Magnus Johnsen · ‎14-09-2022

Hi, We'll have a look at it and get back to you. As it is specified in the documentation we would assume that it should be returned, we'll lift this with the development team.

Magnus Johnsen · ‎08-09-2022

Hi, Have you seen any patterns to which items return what value? Could you provide us with some examples? Thank you.

Magnus Johnsen · ‎06-09-2022

Magnus Johnsen · ‎06-09-2022

Hi, As it is not a field that is exposed a not working, it will not be considered a bug. It's a new field that needs to be exposed via the API which means it will be treated as a wish for improvement and not a bug. If there is an issue with how the value for the branch associated with the cash account set on the invoice is handled, it would be a bug case.

Magnus Johnsen · ‎05-09-2022

Hi, This field is currently not exposed via the supplierPayment endpoint. By default, the branch is set according to the cash account on the invoice. If this is a functionality you need, we recommend that you create a post under the Ideas part of the forum.

Magnus Johnsen · ‎01-09-2022

Hi, You'll need to encode the inventoryNumber in this case, have a look at this article and try it: Method for getting resources with reserved characters - B64URL Encoding

Magnus Johnsen · ‎01-09-2022

Hi, We are not able to reproduce this:

Magnus Johnsen · ‎01-09-2022

The feature causing the issue has been toggled of and the fields are now available on post.

Magnus Johnsen · ‎01-09-2022

We are waiting for more information from the developer team. Meanwhile, the feature causing the issue has been toggled of and the fields are now available on post.

Magnus Johnsen · ‎31-08-2022

This does not look like a companyID, could you please doublecheck?

Magnus Johnsen · ‎31-08-2022

Could you please send us the companyID?

Magnus Johnsen · ‎31-08-2022

Could you please send us the companyID?

Magnus Johnsen · ‎31-08-2022

Hi, Could you please send us the error message returned as well? We are not able to reproduce this, but it might be related to companyInContext issues.

Magnus Johnsen · ‎31-08-2022

Hi, We have confirmed that lineDescription and UoM is omitted when posting, we'll open a case with the developers. For now the workaround is to send this in a PUT.

Magnus Johnsen · ‎31-08-2022

Hi, We're not able to reproduce this, is it still an issue?

Magnus Johnsen · ‎30-08-2022

The issues seems to be resolved now, calls are going through. Please let us know if you are still having issues. Thank you.

Magnus Johnsen · ‎30-08-2022

Thank you, we'll pass it on.

Magnus Johnsen · ‎30-08-2022

Hi, We are able to reproduce this on some endpoints, do you have any examples that we can pass on to the developer team? We are currently looking in to this. It would help knowing: Endpoint Timestamp Request-ID Thank you.

Magnus Johnsen · ‎30-08-2022

Hi, Thank you, we'll forward this to the development team. The issue is being prioritized.

Magnus Johnsen · ‎25-08-2022

Hi, The payload that is sent is a JSON array. This is because under load, Visma.net Integrations will group the notifications together and send them only once instead of sending each one individually. For instance if there were 5 "customerinvoice_changed" events that happen in a short period of time, Visma.net Integrations will group these and invoke the "hookUri" only once, instead of making 5 http requests.

Magnus Johnsen · ‎25-08-2022

The issue has been reviewed and is currently in the backlog.

Magnus Johnsen · ‎24-08-2022

Hi! The error message should contain what policy triggered it. Example: HTTP Status: 429 Exception Message: "Same request made too many times" Response Headers: x-ratelimit-limit: 5 x-ratelimit-policy: IntervalLimit x-ratelimit-reset: 1551868340 (Epoch-Unix Format which is representing the start of next sliding window) You can see the different policies in this article: Why am I receiving "HTTP 429 - Too many request / throttling" response from API ?

Magnus Johnsen · ‎23-08-2022

HI, Could you please send us an example JSON? Thank you.

Magnus Johnsen · ‎23-08-2022

Hi, We haven't been able to replicate the exact same behaviour, however the salesOrder webhook is sent as soon as the shipment confirmation is sent, we'll check if it is intended to be this way. There is a background operation, currently there is no way of getting notified when this operation has succeeded or failed, your only notified in the response that the operation has been queued.

Magnus Johnsen · ‎23-08-2022

Hi, The symptoms sound like they are the same, we'll have a look at it and get back to you.

Magnus Johnsen · ‎22-08-2022

I can say with certainty that it has been mandatory at least since November 2021, but it has most likely been mandatory since long before that. When set up in the itemclass, you would most likely not think about it as it gets populated from the itemClass.

Magnus Johnsen · ‎19-08-2022

Yes, posting class is mandatory for all items: The posting classes are generally tied to stock/non-stock and then the VAT rate of the item. If you are unsure of what rules are applied to the posting classes you have, we recommend having at look at the screen for Posting Classes mentioned in post above, or just looking at other items of the same sort.

Magnus Johnsen · ‎19-08-2022

Hi, Posting class is a mandatory field, so you can't avoid it: Posting class(From the ERP documentation): The posting class of the stock item, which by default is the posting class assigned to the item class. You can select another posting class for the item. You use the Posting classes (IN206000) window to define posting classes and their properties. The default item classes will have this field set, if you need more help on how to setup posting classes we recommend that you get in contact with your partner service. Thank you.

Magnus Johnsen · ‎18-08-2022

Ok, I found an email where you can send your questions: cloud.api.support@visma.com Thank you.

Magnus Johnsen · ‎17-08-2022

Hi, The Visma.Net Financials endpoint for Employee does not return the organization number. If it's regarding the Visma Payroll API, we'd recommend creating a post in their forum: Visma.Net Payroll Api Or visit their github page: https://github.com/visma-net/payroll-public-api-docs

Re: No lastModifiedDateTime for attributes

Re: /inventory returning checkbox attribute as bot...

Re: Allow updating the conversion table on Invento...

Re: POST supplierPayment : Make supplierpayment in...

Re: POST supplierPayment : Make supplierpayment in...

Re: Inventory - specific inventory item now return...

Re: Inventory - specific inventory item now return...

Sv: Errors after Visma update today - Critical

Sv: Errors after Visma update today - Critical

Sv: "You don't have permission to access this reso...

Sv: "You don't have permission to access this reso...

Svar: "You don't have permission to access this re...

Svar: "You don't have permission to access this re...

Sv: Errors after Visma update today - Critical

Svar: "You don't have permission to access this re...

Re: "You don't have permission to access this reso...

Re: "You don't have permission to access this reso...

Re: "You don't have permission to access this reso...

Re: Problem creating ‘Invoice separately’ See tick...

Re: Question about webhook body

Re: Problem creating ‘Invoice separately’ See tick...

Re: Same request made too many times

Svar: Possible bug in Post RC SalesOrderV2

Re: shipment_changed webhook fires prematurely?

Re: Possible bug in Post RC SalesOrderV2

Re: API Inventory / Posting Class error

Re: API Inventory / Posting Class error

Re: API Inventory / Posting Class error

Re: Payroll API - posible to show active fields

Re: Payroll API - posible to show active fields

Useful pages

About Visma

Contact us

Follow us