Today the same "CompanyLimitInterval" error occurred at a Swedish site. We have checked and double-checked, but the user uses "Visma Connect", not "VNI".   An identical configured Dutch Visma.net account could load more rows without problem.   Also see https://forums.invantive.com/t/itgenvnt067-you-have-run-out-of-api-requests-please-try-again-after-560-seconds-50/4763.   What can cause this "CompanyIntervalLimit" rate limiter to kick in on Visma Connect with Visma.net ? ... View more

Yes, but still missing formal documentation what it is. Now just BSOD type of error. For Power BI and data integration on Visma.net financials the on boarding experience we provide must be that the user can on board and serve himself within 2 minutes. Not understanding what an error means when it occurs makes that hard. ... View more

Terzijde: Invantive is implementatiepartner. ... View more

Is there any news regarding the meaning of the policy "CompanyIntervalLimit"? We have one customer that runs into this error but we do not know how to help him solve. ... View more

Yes, probably. Some formal documentation would help us to provide users better feedback. ... View more

Ah, I see. I needed to click save, while all fields were filled correctly, before the Invitation codes box came up. ... View more

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

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

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

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

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

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

Grant type = Authorization code ... View more

Why is there a `code_challenge`? That only applies to PKCE which we don't intend to use. ... View more

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

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

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

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

Yes, all users in our ISV account have the Customer Administrator role. Still, none of the users can assign Integration Administrator. ... View more

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

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

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

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