Search
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Sign In
My Products
Help
Sign in or create account
to get a personalized navigation.
Sign in or create account
to get a personalized navigation.
User Profile
guidol
41
Posts
4
Kudos
2
Solutions
20-12-2023
10:15
Ah, I see. I needed to click save, while all fields were filled correctly, before the Invitation codes box came up.
... View more
20-12-2023
09:54
I am trying to test the service-to-service integration for Visma ERP. In order to do that I have created a service application in the OAuth section of the Developer Portal. I have added the required scopes. Now I am trying to call the /token OAuth endpoint to obtain a token. I understand the tenant has to consent to use the application, as per the documentation. I understand this is done using the App Center. However, how to consent the use of a service application when the application is still in development? I see no option in the Developer Portal or App Center to give consent to a service application.
... View more
15-12-2023
13:07
No problem. You have been very helpful as always. You have quite a lot of knowledge on these subjects... This question was inspired by the problems I am facing on this topic that isn't getting anywhere at the moment. I hoped deleting the old token would help, but unfortunately it doesn't work.
... View more
15-12-2023
10:29
Yes, there it can be deleted indeed. I still wonder why the original screen gives the HTTP 404 error instead of a regular error message.
... View more
15-12-2023
09:16
The URL provided is correct. The bug reported seems to be user-specific. I have tried the link with another Visma .net user and now it does work. So the tenant consent update error is specific for this user, who has consented with other OAuth settings before.
... View more
14-12-2023
16:46
1 Kudo
Still you'd like to know who you are connected to. As an ISV you do not know on beforehand who connects to your application, so some context is useful. You can get that though a call to https://connect.visma.com/connect/userinfo, although that needs openid scopes to be present. For Visma .net ERP you can call `controller/api/v1/organization`, which will yield one single company.
... View more
14-12-2023
16:44
Thanks, this would be an A case indeed. However, I see no apps registered for either of the two companies there while I do have an active access token.
... View more
14-12-2023
16:26
I don't think it should be necessary to call the API for a token revocation. What if I am a regular user wanting to delete the authorization? How to revoke it in that case? For now I am trying to diagnose the problem of this issue by seeing if removing the token makes any difference.
... View more
14-12-2023
14:52
I am not able to remove a previously issues token using https://adm2.visma.net/user/details/mymobiletokens. Chrome DevTools shows a call to https://api.adm2.visma.net/webapi/rest/userdetails/revokeCurrentUserTokenByScope/Financi%C3%ABle%20taken resulting in a HTTP 404.
... View more
14-12-2023
13:02
The currently used call to `authorize` is (replacing the client ID): https://connect.visma.com/connect/authorize?response_type=code&client_id=xxxx&redirect_uri=https%3A%2F%2Fdcloud%3A44362%2Fapp%2Fsetup%2Fdatabases%2Fnew%2Fvismanet%2Ftoken&state=INVANTIVE-fb5bc40483ad402e97d4821eeae71ce9&scope=openid+email+profile+vismanet_erp_interactive_api%3Aread+vismanet_erp_interactive_api%3Acreate+vismanet_erp_interactive_api%3Aupdate+vismanet_erp_interactive_api%3Adelete
... View more
14-12-2023
12:48
Grant type = Authorization code
... View more
14-12-2023
11:41
Why is there a `code_challenge`? That only applies to PKCE which we don't intend to use.
... View more
13-12-2023
15:17
I see. Thanks! That button deserves a little more emphasis and possibly a mention in the error dialog for development users. After making some changes and retrieving an access token I get the next error: Message - Unhandled exception: Failed to update tenant consent for user b0be87dc-xxxx, client xxxx and tenant 0feb108a-xxxx, errorId: a2c7cd20-xxxx Response - HttpResponseInfo { StatusCode: InternalServerError, ErrorCode: null } SourceContext - VismaConnect.Web.IdentityProvider.Middlewares.ExceptionHandlerMiddleware RequestId - 0HMVR44A0F0S5:00000002 RequestPath - /connect/authorize/callback ConnectionId - 0HMVR44A0F0S5 Request_Ipv4Address - xxxx Request_UserAgent - Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36 Request_Method - GET Request_Path - /connect/authorize/callback Request_Host - connect.visma.com Request_ClientId - xxxx CorrelationId - 3e98b89f-xxxx UserId - b0be87dc-xxxx SessionId - af9151a4-xxxx IdentityProvider - Visma Connect TenantId - null Timestamp - 12/13/2023 14:12:05 +00:00 Level - Error ExceptionSource - VismaConnect.Dal.ConnectDb ExceptionType - VismaConnect.Dal.ConnectDb.Connector.ConnectDbException ExceptionMessage - Failed to update tenant consent for user b0be87dc-xxxx, client xxxx and tenant 0feb108a-xxxx StackTrace - at VismaConnect.Dal.ConnectDb.Services.UserTenantConsentDbService.UpdateAsync(Guid userId, String clientIdentity, Guid tenantId, IEnumerable`1 scopes) in /tc-agent/work/d20c03d2a8e0d24e/src/VismaConnect.Dal.ConnectDb/Services/UserTenantConsentDbService.cs:line 81 Any clue?
... View more
13-12-2023
13:42
The above error also happens when we open the OAuth URL (similar to https://connect.visma.com/connect/authorize?response_type=code&client_id=xxxxxx&redirect_uri=https%3A%2F%2Fxxxxx%3A44362%2Fvismanet%2Ftoken&state=4b99d796a75f4a1cb4ab019b2cc79c51&scope=vismanet_erp_interactive_api%3aread) from an Incognito session.
... View more
13-12-2023
13:31
We worked with our partner manager to get some things checked since this is getting critical for us now. It seemed that there was a new license made for us, but it seems it was separated from our profile. This leaded to all kind of weird problems. This has been resolved now by support by moving all users to the new license. Currently we get one step further in the log on process: we can choose what company to connect, but selecting either of the two companies leads to another error: Can you check the actual problem?
... View more
12-12-2023
14:06
The same problem is shown there: "0 of 0 licenses in use". There is no way to select any of the roles there:
... View more
12-12-2023
09:14
Yes, all users in our ISV account have the Customer Administrator role. Still, none of the users can assign Integration Administrator.
... View more
11-12-2023
14:37
We are trying to implement the Visma Connect log in for our applications. Using the documentation on https://community.visma.com/t5/Forum-in-Developers-Visma-net/Visma-net-ERP-API-Developer-Portal-Startup-Guide/m-p/544710/thread-id/2965 we have come quite far, but now we are facing a similar problem as described here: https://community.visma.com/t5/Forum-in-Developers-Visma-net/Access-denied-during-authorisation-through-Visma-Connect/m-p/585571#M3728, specifically: > You do not have access to the selected company or to any companies for this application You are signed in as ("company", "account") According to the post mentioned above, the “Integration Administrator" role must be granted to the user trying to log on. However, it is not possible to select that option on any of the companies available giving there are no licenses in use: Checking with our Visma Partner manager it seems there is an active license and from their point of view everything should be okay. What is the reason this option is not available? How to check if we have the appropriate license to perform this action? Any other thoughts?
... View more
21-09-2023
15:58
Sample [
{
"type":"VoidPayment",
"refNbr":"405812",
"status":"Closed",
"hold":false,
...
"paymentLines":[
{
"documentType":"Invoice",
"refNbr":"987654321",
"amountPaid":1234.7700,
"cashDiscountTaken":0.0,
"balanceWriteOff":0.0000,
"writeOffReasonCode":{
"id":"BK01",
"description":"DESC"
},
"date":"2023-12-31T00:00:00",
"dueDate":"2021-07-23T00:00:00",
"cashDiscountDate":"2023-12-31T00:00:00",
"balance":0.0,
"cashDiscountBalance":0.0,
"description":"FAKTUUR ORDER456",
"currency":"EUR",
"postPeriod":"202106",
"customerOrder":"ORDER456",
"crossRate":1.0
},
{
"documentType":"Invoice",
"refNbr":"987654321",
"amountPaid":-1234.7700,
"cashDiscountTaken":0.0,
"balanceWriteOff":0.0000,
"writeOffReasonCode":{
"id":"BK01",
"description":"DESC"
},
"date":"2023-12-31T00:00:00",
"dueDate":"2021-07-23T00:00:00",
"cashDiscountDate":"2023-12-31T00:00:00",
"balance":0.0,
"cashDiscountBalance":0.0,
"description":"FAKTUUR ORDER456",
"currency":"EUR",
"postPeriod":"202106",
"customerOrder":"ORDER456",
"crossRate":1.0
},
{
"documentType":"Invoice",
"refNbr":"987654321",
"amountPaid":1234.7700,
"cashDiscountTaken":0.0,
"balanceWriteOff":0.0000,
"writeOffReasonCode":{
"id":"BK01",
"description":"DESC"
},
"date":"2023-12-31T00:00:00",
"dueDate":"2024-01-01T00:00:00",
"cashDiscountDate":"2023-12-31T00:00:00",
"balance":0.0,
"cashDiscountBalance":0.0,
"description":"FAKTUUR ORDER456",
"currency":"EUR",
"postPeriod":"202312",
"customerOrder":"ORDER456",
"crossRate":1.0
}
],
...
]
... View more
21-09-2023
15:56
The API /controller/api/v1/customerPayment/{paymentNumber} contains "paymentLines", an array of payments. However, the lines within the list of payment lines are not unique; it can contain duplicate lines due to missing fields such as batch number (which was different for the two lines with the positive amount in the UI) or an ID or GUID. Making the lines not unique makes it hard to uniquely identify, leading to problems in reporting and integrity checks. It would be great when an ID, line number or batch number could be added to make the lines within a customer payment unique.
... View more
16-02-2023
09:36
We have solved issue 1 by switching back to one of the old Swagger JSON files. That fixed it for now. With Visma Connect upcoming, there are probably more issues ahead so we will again in a few months how the Swagger evolves. When you don't have it, I can send an old swagger to you. Issue 2 can be seemingly be solved by removing cookies.
... View more
10-02-2023
09:23
Was there a specific introduction date for invalidating all previous tokens when a new one is acquired? We have one customer with that problem.
... View more
10-02-2023
08:14
My privileges on the forums seem to be flip flopping, leading to disappearing posts/replies. The Bad Requests seem related due to breaking changes in the swagger. I have created a separate topic on the problems with Swagger (can't find it back but maybe it will appear again). I will try to close this topic.
... View more
10-02-2023
08:13
Apologies for the test. My privileges on the forums seem to be flip flopping, leading to disappearing posts/replies. I have created a separate topic on the problems with Swagger, since this one has been marked already as solved.
... View more
10-02-2023
08:11
Related to https://community.visma.com/t5/Forum-in-Developers-Visma-net/Visma-Net-API-Swagger-page-not-showing/m-p/558087 and https://community.visma.com/t5/Forum-in-Developers-Visma-net/HTTP-400-Bad-Request-answers/m-p/558071 There are several issues it seems, part of which leads to a largely full production stop: Issue 1 - Swagger broken The Swagger at https://integration.visma.net/API-index/doc/swagger opens, but seems to have changed largely. The following entries are completely missing: - ipp-company-id - ipp-application-type The Swagger lists version 9.33 of unknown date. The missing of ipp-company-id ensures that practically all Invantive Cloud users are seeing either HTTP 400 Bad Requests with an error like: Invalid parameter exception: ipp-company-id (12002_12002_7b28d6d8-104b-4acc-991b-e5290bde8fdb) when their cached copy of the Swagger is not updated, or getting errors when retrieving data from Visma.net since there is no longer a way with the current driver of Invantive SQL to access the APIs providing the company (called "partition" in Invantive SQL). The missing of ipp-company-id might be related to the early December announcement that the VNI will be deprecated during 2023 (no specific date mentioned) (source: https://community.visma.com/t5/Knowledge-base-in-Developers/Guide-Move-from-VNI-to-Visma-Connect-Authentication-for-Visma/ta-p/542146). The linked PDF in that article specifies on page 19 that ipp-company-id will be dropped in 2023. Impact: Blocking; the impact is that almost all Visma.net use on Invantive Cloud has come to a halt. Question: Is it possible to revert the changes on the Swagger metadata? Issue 2 - Swagger UI broken The Swagger UI works unrealiably it seems. On my PC (Windows, Chrome), a 404 error occurs on service-worker.js Error during service worker registration: TypeError: Failed to register a ServiceWorker for scope ('https://integration.visma.net/API-index/') with script ('https://integration.visma.net/API-index/service-worker.js'): A bad HTTP response code (404) was received when fetching the script. However, a co-worker on another Windows PC with Chrome has a new filename continuously on main*.js which fails and returns an empty page. This may explain problem on https://community.visma.com/t5/Forum-in-Developers-Visma-net/Visma-Net-API-Swagger-page-not-showing/td-p/558087 He is located in same city as I am. His error: The page displays however. Authorize works, but leads to a weird error: The fact that authorization works is proven that finance.visma.net does not require authentication when opened after the weird error. Impact: low; we can live without Swagger UI. Question: None. Issue 3 - Release notes incorrect The release notes don't mention that ipp-company-id would be dropped (source: https://community.visma.com/t5/News-in-Developers-Visma-net/Release-Notes-Visma-Net-API-9-32-0-02-02-2023/ba-p/557104). The point of financial periods is known; it was for one of the older Visma.net users, but there is no other breaking changes listed. Impact: low; as long as intended situation known we can fix it. Question: would be great when release notes would be updated when switch on OAuth is actually required with this release.
... View more
09-02-2023
15:23
test whether can post again.
... View more
09-02-2023
14:51
The Swagger seems seriously broken, and this may explain the intermittent errors across a larger user base of Visma.net users on Invantive Cloud. The impact depends on whether the users have already switched to the new Swagger released with 9.33 (no release date in Swagger). Issue 1: the Swagger metadata page https://integration.visma.net/API-index/doc/swagger seems to open, but the content is seriously changed with major impact for all users that we support since the datamodel is generated dynamically. We are missing for instance: - ipp-company-id - ipp-application-type The first one is critical for many users, since we don't know how to exchange the company and discover that an API has different outcome per company (we call it "partitions" in the SQL engine) The removal of ipp-company-id may explain the still occurring Bad Requests (see forums post https://community.visma.com/t5/Forum-in-Developers-Visma-net/HTTP-400-Bad-Request-answers/td-p/558071), such as in an error like: Invalid parameter exception: ipp-company-id (12002_12002_7b28d6d8-104b-4acc-991b-e5290bde8fdb) Question: where can we find current documentation for providing the company ID? We seem unable to find the docs. Issue 2. The Swagger-UI seems unstable. The Swagger-UI page https://integration.visma.net/API-index/ opens on my Chrome on Windows. However, it gives a 404 on service-worker.js: A bad HTTP response code (404) was received when fetching the script.
main.17349a4d.js:2 Error during service worker registration: TypeError: Failed to register a ServiceWorker for scope ('https://integration.visma.net/API-index/') with script ('https://integration.visma.net/API-index/service-worker.js'): A bad HTTP response code (404) was received when fetching the script. At a co-worker on Chrome on Windows on another PC, the name of the main...js download changes on every Hard Refresh (Ctrl+F5), see picture. The browser shows an empty page. Question: none, we can live without Swagger-UI, as long as the actual metadata is correct. Issue 3: Authorize does not work at my PC. It can authorize after selecting all scopes (selecting none gives a weird error), but the following page is displayed: However, I can access Visma.net without problems: I was also able to complete the full Visma.net authorization flow using Code Grant Flow on Invantive Cloud for Visma.net Financials. However, an old database with a previously completed Code Grant Flow would not open and spin forever in a loop with Visma.net API servers. Question: none. Issue 4: I seem unable to find any hints on these changes in the release notes on https://community.visma.com/t5/News-in-Developers-Visma-net/Release-Notes-Visma-Net-API-9-32-0-02-02-2023/ba-p/557104. The financial periods is known; it was an issue for one of our older Visma.net users. Question: where can we find current documentation of the changes?
... View more
08-02-2023
14:36
Yes, that is ensured. It started occurring across a larger number of Visma.net users and Visma.net subscriptions in various countries at the same day. Previously, they all had a working setup and it only affeects a % of the call. Somehow the frequency of Bad Requests has increased and now lessened again.
... View more
08-02-2023
13:18
We seldom to never receive HTTP 400 Bad Request errors on Visma.net API. Starting February 2, we have seen an increasing quantity of errors. Few on February 2, 4, 5 and 6. Approximately 10 times more on February 3. The errors are like: (400) Bad Request. (1875374) En ukjent feil oppstod. And a sample of the full text is: {"ExceptionType":"IPPException","ExceptionMessage":"Invalid parameter exception: ipp-company-id","ExceptionFaultCode":"12002","ExceptionMessageID":"12002_12002_2d41db7b-d43c-43ba-96b0-2700d5f5e257","ExceptionDetails":""} The Bad Requests occurs intermittently across many APIs. We have not seen them yesterday (February 7). Was there are incident or is there something we must do to avoid these Bad Requests?
... View more
02-11-2022
12:22
Thank you for the clarity! We will disable pagination on this endpoint for now.
... View more
Activity Feed for guidol
- Posted Re: invalid_tenant when authenticating using client_credentials on Forum in Developers Visma.net. 20-12-2023 10:15
- Posted invalid_tenant when authenticating using client_credentials on Forum in Developers Visma.net. 20-12-2023 09:54
- Posted Re: Can't delete token - HTTP 404 on Forum in Developers Visma.net. 15-12-2023 13:07
- Posted Re: Can't delete token - HTTP 404 on Forum in Developers Visma.net. 15-12-2023 10:29
- Posted Re: Can't assign App Store “Integration Administrator" role on Forum in Developers Visma.net. 15-12-2023 09:16
- Got a Kudo for Re: context endpoint gone in swagger doc for service api + invalid scope. 14-12-2023 17:45
- Posted Re: context endpoint gone in swagger doc for service api + invalid scope on Forum in Developers Visma.net. 14-12-2023 16:46
- Posted Re: Can't delete token - HTTP 404 on Forum in Developers Visma.net. 14-12-2023 16:44
- Posted Re: Can't delete token - HTTP 404 on Forum in Developers Visma.net. 14-12-2023 16:26
- Posted Can't delete token - HTTP 404 on Forum in Developers Visma.net. 14-12-2023 14:52
- Posted Re: Can't assign App Store “Integration Administrator" role on Forum in Developers Visma.net. 14-12-2023 13:02
- Posted Re: Can't assign App Store “Integration Administrator" role on Forum in Developers Visma.net. 14-12-2023 12:48
- Posted Re: Can't assign App Store “Integration Administrator" role on Forum in Developers Visma.net. 14-12-2023 11:41
- Posted Re: Can't assign App Store “Integration Administrator" role on Forum in Developers Visma.net. 13-12-2023 15:17
- Posted Re: Can't assign App Store “Integration Administrator" role on Forum in Developers Visma.net. 13-12-2023 13:42
- Posted Re: Can't assign App Store “Integration Administrator" role on Forum in Developers Visma.net. 13-12-2023 13:31
- Posted Re: Can't assign App Store “Integration Administrator" role on Forum in Developers Visma.net. 12-12-2023 14:06
- Posted Re: Can't assign App Store “Integration Administrator" role on Forum in Developers Visma.net. 12-12-2023 09:14
- Posted Can't assign App Store “Integration Administrator" role on Forum in Developers Visma.net. 11-12-2023 14:37
- Posted Re: Duplicate rows in Customer Payment - Lines API on Forum in Developers Visma.net. 21-09-2023 15:58
Useful pages
Contact us
Copyright © 2022 Visma.com. All rights reserved.
Visma Denmark
Visma Finland
Visma Latvia
Visma Netherlands
Visma Norway
Visma Sweden
Visma Developers & Partners
Visma Latin America