User Profile
ExactGebruiker
35
Posts
1
Kudos
1
Solution
05-06-2024
15:54
Hi, It seems there have been changes to the Visma.net API since June 1st? I cannot find any updates regarding this on the release notes page of Visma.net. I am having issues reading data from the API, as well as Nmbrs (that links with Visma via the old API connection) can no longer communicate with Visma. https://releasenotes.vismanet.sweden.visma.com/ How can I find out the changes done to the API? Let me know, thanks! Izan
... View more
11-03-2024
13:51
We are trying to create a dashboard in an external BI environment in order to create an overview over all of our clients (which include about 200 branches in 60 company contexts) in regards to total work supply. That includes total number of purchase invoices pending, sales invoices pending and mainly bank transactions to be processed, comparable to the overview in the Client Manager Monitor. The CM Monitor is not sufficient however in our Visma data needs.
... View more
05-03-2024
20:39
Hi, Either CA306500 or CA306000 would work. When I consult the Query design screen (SM208000), then I am referring to table CABankTran.
... View more
01-03-2024
16:02
Hi, Not an expert on this, but I am guessing it has something to do with the customer settings. Is this error also happening with other customers? Izan
... View more
01-03-2024
16:00
Hi, I have a question regarding the Visma.net ERP API. When I look at the endpoints, I cannot recognize any way to extract the bank/cash transactions. In particular, I am looking for table CABankTran. Endpoint CashTransaction does not do it for me, as these are only the processed transactions (and does not concern the original document), not all. So, is there an endpoint for CABankTran? This seems to me a very basic endpoint to use, for example in order to evaluate the quantity of bank transactions to be processed. Thanks!
... View more
25-08-2023
11:27
Hi Yildirim, Could you also try it with a custom made access role? We use access roles to split access to branches between users, so we cannot use Admin for the split, as there should be multiple roles assigned to different branches. Thanks!
... View more
22-08-2023
17:59
Thanks. Ok, but did you try it with an access_role attached to a branch? See below. When applied to a branch, only users attached to the access_role can access the branch, which an API cannot as does not have a user. Please try it with a user role attached to the branch (and wait a day or 2) and try again. It seems you have some saved cache on this subject so immediate change in these roles is not the case via the API. That, or try to recreate the error (no access to branch n) on your own, as without this, you would not get the error I feel.
... View more
21-08-2023
10:35
Hi, Any news on this issue?
... View more
21-08-2023
10:30
Hi, It seems this has not been fixed. Maybe I am misunderstanding the fix? When trying to create a SupplierInvoice we still get the no_access error. How am I supposed to provide access if there is no user account linked to the access role? 'No access to branch 1' is the exact same error as before. Could you explain the fix? Thanks.
... View more
10-08-2023
08:59
Great to hear!
... View more
12-07-2023
14:38
Great, thanks!
... View more
12-07-2023
14:36
Hi, This was already know. It is simply rediculous that the new authentification process omits your own Service API way of working. Am I to understand that there will be no fix for this? We do use access roles in over half of our companies (around 30 contexts) in order to divide access rights to certain branches for certain users. This means that for these companies our new application is simply unusable. This seems to me honestly like an urgent problem for the API department, but apparently Visma thinks otherwise.
... View more
05-07-2023
16:55
Hey there, the cause has been found, it appears to be a problem on our end that would've come to light had we just thrown the CURL call through. If others are finding this in PHP using Guzzle, then they need to try catch capture the BadResponseException around the ->send() and recreate it as Guzzle cuts it off in creating the error. The response body still holds the original full sized error. https://github.com/guzzle/psr7/blob/2.5/src/Message.php#L75
... View more
05-07-2023
14:52
Hi, We have found the error. It seems when creating a purchase invoice via the Service API, and we fill in a ledger account on a purchase invoice line, if this is also the default ledger account for costs in the Employee settings, it does not work. If I change, given above example, the default ledger account from 4199 to 4300, the push does work. So if we want to push an invoice line with (the already) default ledger account of 4199, it does not work, but if the default does not match the pushed value (either by changing the pushed value or default value) then it DOES work. Please look into a fix for this, because we have to currently change all defaults for running invoices from employees in the meantime as this gets stuck. Thanks ahead!
... View more
04-07-2023
17:02
Hi, Please review as this all is not the case. It does work if we use a different ledger account in the API POST. And it does work if we push the POST with a different GL account and change it manually to the erroneous account. So it is not a null value that is the issue (just a different value), the account is not inactive (as we can change the ledger account in the same purchase invoice manually). All mandatory fields (as shown before) are filled in. This is a glitch with a certain set ledger account in Employees for which it apparently requires EU and Import ledger accounts as if it is a supplier. This had earlier not been an issue, and now it occurs en masse for loads of our companies. This seems to be a bug from an update, probably the one in week of 305h of May.
... View more
04-07-2023
10:40
Hi, Any updates on this?
... View more
04-07-2023
10:25
Hi, Where are we with this issue? Thanks.
... View more
27-06-2023
16:59
Hi, This error mainly occurs with purchase invoices made for Employees. My example concerned an employee, and when I change the supplierId to one of an actual supplier, then it does work. Also, I am pushing VatCode NULL, as I do not want to fill in a VAT code and do not want Taxlines on the invoice. But when changing this to VatCode 0, this also circumvents the error. Do you know where the problem lies? Maybe a combination of VATcode and account numbers? Below the settings of another employee which experiences the same error (as the original invoice has been solved manually in the meantime). Look forward to hearing from you. Thanks.
... View more
26-06-2023
17:36
Hi, 038e874c-8aa0-4123-b8fe-2519d9617394 This gets truncated as shown below Client error: `POST https://integration.visma.net/API/controller/api/v1/supplierInvoice` resulted in a `400 Bad Request` response:
{"message":"Error creating supplierInvoice. {\"1\":{\"SubID\":\"An error in processing of field Subaccount: Error: Koste (truncated...) Whereas 3b787520-066d-42bc-abc8-be4cc1409da5 This one was done in Swagger and does not get truncated as shown below {
"message": "Error creating supplierInvoice. {\"1\":{\"SubID\":\"An error in processing of field Subaccount: Error: Kostenplaats of Subaccount do not exist.\"},\"2\":{\"SubID\":\"An error in processing of field Subaccount: Error: Kostenplaats of Subaccount do not exist.\"},\"3\":{\"SubID\":\"An error in processing of field Subaccount: Error: Kostenplaats of Subaccount do not exist.\"}}"
} But there are a lot more errors that just get truncated, anything big just gets cut off entirely.
... View more
26-06-2023
14:05
Hi, When something goes wrong in our API service call to Visma, we get a truncated error. However, when making the same call from the Swagger page, we get the full error. It would be really useful if we could somehow also get the full error to our own app with a header to indicate that, or just by default. We can retrieve entire documents but are somehow not allowed to retrieve a full error when doing a request. There is also no id except the ipp-request-id to maybe fetch what went wrong, which us users can not use. Can you help us retrieve full errors when something fails in our API call? Thanks ahead.
... View more
26-06-2023
12:00
Hi, Per company there seems to be 1 specific ledger account number that does not work with the call. It is not a consistent one overall from company to company. For the one it concerns 4199, the other company has a problem with 4400 in our case. What could cause this? Because when we push it with another account, and manually change (or create manually entirely) the invoice, it does work. This seems to be a problem with the API.
... View more
02-06-2023
18:21
1 Kudo
Hi, Does that mean we have to create a new application with different authentification methods (As we now use the Service to Service API, we would have to switch to Web based for example)? That seems like saying 'this API service does not work, please try a different one'. Why offer this one then if authorizations are based on users and this service does not include user rights? Seems like a top priority to fix, and now it sounds like you are fine with the current situation for the time being.
... View more
02-06-2023
17:35
Hi, Since the 30th of May 2023, we have been getting an error for some invoices we have been trying to create via the Service API. The error we keep getting for some invoices is 'Supplier transactions' record raised at least one error. Please review the errors.\r\nMissing taxable, non-taxable, EU or import accounts. Check the GL account settings for the item, supplier and supplier class\r\n" When changing the GL account, we indeed sometimes get to create the invoice, but this issue has been occuring for mutltiple of our companies (contexts) and within the same company it is not consistent. For example, one invoice we try to create is the following: {
"documentType": {
"value": "Invoice"
},
"hold": {
"value": false
},
"date": {
"value": "2023-06-02T00:00:00.000Z"
},
"supplierReference": {
"value": "7792639-Declaraties juni"
},
"description": {
"value": "7792639-Declaraties juni"
},
"supplierNumber": {
"value": "25008"
},
"currencyId": {
"value": "EUR"
},
"branchNumber": {
"value": "01"
},
"paymentMethod": {
"value": "2"
},
"taxDetailLines": [],
"invoiceLines": [
{
"operation": "Insert",
"lineNumber": {
"value": 1
},
"transactionDescription": {
"value": "period screening"
},
"costInCurrency": {
"value": 33.85
},
"accountNumber": {
"value": "4199"
},
"vatCodeId": [],
"branchNumber": {
"value": "01"
}
}
],
"overrideNumberSeries": {
"value": false
},
"validateLineDetails": {
"value": true
}
} And we get the before mentioned error. When changing the accountNumber value to '4504' for example, the invoice is created. In other companies other accounts are the problem. This process has been working no problem for the last 3 months for all of our companies, but since the 30th opf May, it gives the error. Foes anyone know why this is happening? Thanks! Izan
... View more
12-04-2023
16:23
Hi, For your information, we have no problems with companies that do not use branch protection (user access roles). When a company of ours has no restricting roles, then after a day or two, the error dissappears and the endpoint becomes fully funcitonal. Hope this input helps!
... View more
12-04-2023
16:18
Hi, Thanks for the answer. Though it seems I will have to wait for the fix, because this option is not available for me I think.
... View more
11-04-2023
10:52
Hi, any update? Has it been marked as a bug? Thanks ahead!
... View more
21-03-2023
13:17
Ah ok. That is what I am looking for. Thank you!
... View more
21-03-2023
12:27
We are using the Service API in order to create SupplierInvoices. I don't know wht the nextGen salesOrder would help with this. Please elaborate.
... View more
21-03-2023
10:59
Hi, We are currently working on a Service to Service app, in which we CREATE a SupplierInvoice. However, as adding an attachment is only possible via another endpoint in which we are obligated to GET by Invoice ID. We need to retrieve the Invoice ID of the invoice we created with the other call, but when succesfully created, we do not get a response containing the ID. How are we supposed to add an attachment to these invoices we create if we cannot retrieve them? Thanks.
... View more
20-03-2023
11:39
Hi, I am not using a user, it is a Service Application, so I have a client-id, client-secret and tenant-id. When using my own user account via the Swagger, I am able to add (write) new Suppliers to the environment, but I cannot create a SupplierInvoice, as I mentioned in my post.
... View more
Activity Feed for ExactGebruiker
- Posted API changes since June 1st? Limited requests and connection with Nmbrs. on Forum in Developers Visma.net. 05-06-2024 15:54
- Posted Re: Pending banktransaction endpoint on Forum in Developers Visma.net. 11-03-2024 13:51
- Posted Re: Pending banktransaction endpoint on Forum in Developers Visma.net. 05-03-2024 20:39
- Posted Re: Branch '1 ' cannot be found in the system on Forum in Developers Visma.net. 01-03-2024 16:02
- Posted Pending banktransaction endpoint on Forum in Developers Visma.net. 01-03-2024 16:00
- Got a Kudo for Vastaus: No access to branch when trying to create SupplierInvoice. 10-01-2024 13:43
- Posted Re: No access to branch when trying to create SupplierInvoice on Forum in Developers Visma.net. 25-08-2023 11:27
- Posted Re: No access to branch when trying to create SupplierInvoice on Forum in Developers Visma.net. 22-08-2023 17:59
- Posted Re: When creating a SupplierInvoice via API Service to Service error GL account settings on Forum in Developers Visma.net. 21-08-2023 10:35
- Posted Re: No access to branch when trying to create SupplierInvoice on Forum in Developers Visma.net. 21-08-2023 10:30
- Posted Sv: No access to branch when trying to create SupplierInvoice on Forum in Developers Visma.net. 10-08-2023 08:59
- Posted Re: When creating a SupplierInvoice via API Service to Service error GL account settings on Forum in Developers Visma.net. 12-07-2023 14:38
- Posted Sv: No access to branch when trying to create SupplierInvoice on Forum in Developers Visma.net. 12-07-2023 14:36
- Posted Re: Encoutering errors in truncated form from API response on Forum in Developers Visma.net. 05-07-2023 16:55
- Posted Re: When creating a SupplierInvoice via API Service to Service error GL account settings on Forum in Developers Visma.net. 05-07-2023 14:52
- Posted Re: When creating a SupplierInvoice via API Service to Service error GL account settings on Forum in Developers Visma.net. 04-07-2023 17:02
- Posted Re: Encoutering errors in truncated form from API response on Forum in Developers Visma.net. 04-07-2023 10:40
- Posted Re: When creating a SupplierInvoice via API Service to Service error GL account settings on Forum in Developers Visma.net. 04-07-2023 10:25
- Posted Re: When creating a SupplierInvoice via API Service to Service error GL account settings on Forum in Developers Visma.net. 27-06-2023 16:59
- Posted Re: Encoutering errors in truncated form from API response on Forum in Developers Visma.net. 26-06-2023 17:36
Visma Denmark
Visma Finland
Visma Latvia
Visma Netherlands
Visma Norway
Visma Sweden
Visma Developers & Partners
Visma Latin America