About Magnus Johnsen

Magnus Johnsen · ‎28-09-2020

If it is any of these, it is unfortunately not available: ScreenId=CA306000 ScreenId=AR305000 ScreenId=AR305500 ScreenId=CA3065PL These processes are only available in the UI

Magnus Johnsen · ‎28-09-2020

Hi, We cannot answer to what that app might be able to do within Visma.Net Financials. If you in the Financials UI, go to the page where you would manually perform the operation that you are looking for and share the part of the URL for ScreenId, we can help you see if there are any endpoints available.

Magnus Johnsen · ‎28-09-2020

Hi, Please send us the screenId of the module in Visma.Net Financials and we'll have a look. It can be found in the URL in the UI: The app you link seems to be a different product, unfortunately on the Visma.Net Api Support team we will not be able to answer to this.

Magnus Johnsen · ‎25-09-2020

Hi, As per Yildirims answer to your Ideas thread, I was misstaken. Segment Key > Segment Values can be fetched via Dimension Endpoint.

Magnus Johnsen · ‎25-09-2020

Hi, The best way to find out this information apart from getting the document via the API and looking at the fields is to check Swagger. What ScreenID corresponds to what endpoint van be seen in the header: For what the fields are corresponding to, you can check the description of the model:

Magnus Johnsen · ‎22-09-2020

Hi, We have opened a case with the development team for this and sent you an email. Progress in the case will be posted here. Thank you.

Magnus Johnsen · ‎22-09-2020

Hi, This example: Should be posted as such: POST currency/exchangerates/NOK { "currencyId": { "value": "SEK" }, "rateType": { "value": "SPOT" }, "effectiveDate": { "value": "2020-09-22T12:33:51.915Z" }, "rate": { "value": 5 }, "multDiv": { "value": "Multiply" } } However, it does not seem to be working. We have opened a case for this and will post the progress in this thread. Thank you.

Magnus Johnsen · ‎22-09-2020

Have you been able to collect a JSON where this issue occurs or has it not happened yet?

Magnus Johnsen · ‎22-09-2020

Hi, You can find it either in the developerconsole of your browser when checking swagger: Or, you can GET https://integration.visma.net/API-index/doc/swagger via for example Postman and save the file:

Magnus Johnsen · ‎22-09-2020

Hi, Ok, thanks for clearing that up. We'll report it as unexpected behaviour to the development team. This shold definitely be looked at, but as with any other field in the JSON, if the field is not being used, we do not recomment sending it.

Magnus Johnsen · ‎21-09-2020

The developers are investigating the issue. When we have more details to share, we will update the thread. Thank you.

Magnus Johnsen · ‎21-09-2020

Hi, Could you please send us a screenshot of your number series settings? When you first tested now, you sent it without the overide field in your JSON? Is that correct? What numbering did you get back? And are you saying that you have "Manual numbering" & "Allow for manual numbering on import"?

Magnus Johnsen · ‎21-09-2020

Hi, Indeed, if you request a token again, the last one will get invalidated. If you save it when you request it, you can use the same token in both places.

Magnus Johnsen · ‎21-09-2020

HI, Please don't share your tokens. The Visma.Net FInancials API's do not use refresh tokens as they do not expire unless you have requested a new one. If you have several people using the same user account/client ID combination, you should be sharing the same token. What error message are you receiving?

Magnus Johnsen · ‎18-09-2020

Hi, Ok thank you. It is being reviewed with high priority by the development team.

Magnus Johnsen · ‎18-09-2020

Hi, Are you using customerinvoice v1 or v2?

Magnus Johnsen · ‎18-09-2020

Hi, The issue has been reported to the development team and we'll update this thread according to the information provided. Until we have tested more, the workaround would be to Post the invoice without branch/cashaccount and one line, change the branch in the UI and then PUT the remainder of the invoice and change the cash account.

Magnus Johnsen · ‎18-09-2020

Hi, Ok, this issue only seems to happen on some companies, it might be a caching issue but as of now we cannot say what the cause is. In the past the issue has generally dissapeared during the day. As mentioned, the development team is currently working on the issue and we'll post updates in the case in this thread.

Magnus Johnsen · ‎18-09-2020

Hi, Could you please send us the JSON and screenshots of the cash account so we can test this and bring it up to the development team?

Magnus Johnsen · ‎18-09-2020

Hi, "OverrideNumberSeries" should only have an effect when the series is automatic, and the checkbox to allow it is ticked. If the series is manual, this setting should not make a difference. How long time passed between ticking the setting and trying? We have a case in the backlog where there is a delay between when the setting is set and it is in effect from the API.

Magnus Johnsen · ‎16-09-2020

Hi, As per UI, CreditAdj, does not have the possiblity to add purchaseOrder: It is available for type: DebitAdj Please have a look at your JSON and correct the type as per your picture. Thank you.

Magnus Johnsen · ‎16-09-2020

Hi, Could you please send us the URL and method as well as a screenshot of the "add poReceipt Line" window showing the line: Thank you.

Magnus Johnsen · ‎16-09-2020

Hi, Yes, that is correct. They are made to optimize performance and resolve SQL issues.

Magnus Johnsen · ‎16-09-2020

Hi, We have tried this out and can't see any issues: customer?pageNumber=1&pageSize=100&attributes=%7B%22test%22%3A%22testvalue%22%7D What error are you getting now?

Magnus Johnsen · ‎15-09-2020

Hi! For feature requests, we ask that you post these in the Ideas part of the forum. We'll move it for you. Thank you!

Magnus Johnsen · ‎15-09-2020

Hi, We have had a look at your JSON and tested it in our local company. Firstly, salesOrderOperation should always have a value, either "Issue" or "Receipt". Secondly, the issue with subaccount not being accepted seems to have to do with the salesPerson field: With "salesPerson": {"value": "null"} : Without the "salesPerson" field: We do not recommend sending any fields with null, if a field is not meant to be used in the operation, please omit it. Please remove the field and try again. Thank you.

Magnus Johnsen · ‎14-09-2020

Hi, As this is regarding Visma.Net Financials ERP setup, we would recommend that you get in contact with your ERP consultant at [email protected]. When you have this setup as per your needs, feel free to ask us here on the forum regarding your API inquiries. Thank you.

Magnus Johnsen · ‎14-09-2020

Hi, To set manual numbering for Customer(this also works for any other number series) you need to go to Number Series(ScreenId=CS201010) and tick "Manual Numbering":

Magnus Johnsen · ‎14-09-2020

Hi, We don't think that skipping pagination should be done in any case, all we are saying is that for now, when using pagination and filtering together it is not working. We fully agree that this needs to be resolved and the case has been opened with high priority. Thank you.

Magnus Johnsen · ‎14-09-2020

Hi, It depends on if it will be enforced or not, for this endpoint. We'd say that until the bug with on what page the results shows up in is resolved, you won't be able to properly handle the requests. For the case of the metaData, as long as the above is working as expected, GET ALL works for fetching all objects with pagination, termination of the query would be when you have increased pageNumber until a empty array is returned. But as mentioned, for this to work, the first point needs to be working.

Re: Endpoint for loading BankTransactions/BankMuta...

Re: Endpoint for loading BankTransactions/BankMuta...

Re: Endpoint for loading BankTransactions/BankMuta...

Re: Segment keys - How to see if 'Validate' is set

Re: Finding correct UI fields in JSON

Re: missing vat in orderhead

Re: How to add a new exchange rate

Re: TX-error The document status is invalid for p...

Re: Visma.NET Open API Specification (swagger.json...

Re: Override numberseries

Re: Problem selecting CashAccount on CustomerInvoi...

Re: Override numberseries

Re: refresh oauth token

Re: refresh oauth token

Re: Problem selecting CashAccount on CustomerInvoi...

Re: Problem selecting CashAccount on CustomerInvoi...

Re: Problem selecting CashAccount on CustomerInvoi...

Re: Override numberseries

Re: Problem selecting CashAccount on CustomerInvoi...

Re: Override numberseries

Re: Adding PurchaseReceipt - Type Return to Suppli...

Re: Adding PurchaseReceipt - Type Return to Suppli...

Re: V2 endpoints

Re: Filter customer on attribute, 500 Internal ser...

Re: Customer/Location references in SalesPerson

Re: subaccounts salesorder lines

Re: automatic Customer number generation setting

Re: automatic Customer number generation setting

Re: Issue with filtering of attributes

Re: Issue with filtering of attributes

Useful pages

About Visma

Contact us

Follow us