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
Timo_O
22
Posts
9
Kudos
0
Solutions
30-10-2023
14:35
Company number sent to 'developersupport@visma.com '
... View more
12-04-2023
10:59
Hi, this seems to be version dependent issue ( v1 vs v2). We tried to send the same SalesOrder via v1 ( https://integration.visma.net/API/controller/api/v1/salesorder) and Sub accounts did apply to sales order rows succesfully. We have been using the v2-version since 10.3.2023 because we were suggested avoid this issue: https://community.visma.com/t5/Forum-in-Developers-Visma-net/SalesOrder-added-via-Api-despite-response-code-500/td-p/564976 Could you please investigate, to get sub acoounts working properly in v2?
... View more
10-03-2023
08:42
More information to this issue from our logs. We have got this error code several times as response with different customers in time gap 7.3. 16:52 - 8.3. 02:45. In the same time there has been more succesfull requests with normal response. Here under some examples. The 2 first requests/messages did add a new Salesorder in Visma.net to company 3502689. The 5 later requests/messages did not, company for these requests is 2862416. 2023-03-07 16:52:01 ERROR - HTTP/1.1 500 Internal Server Error / {"message":"VismaId: 34a3a460-b31f-4a62-99b7-17fa8cb5a39c. Error communicating with message broker"} 2023-03-07 17:38:05 ERROR - HTTP/1.1 500 Internal Server Error / {"message":"VismaId: 0d55a12b-2e36-4c16-bf34-5b130e5748d5. Error communicating with message broker"} --------------------------------------------------------------------------------------------------------------------------------------------------------------------- 2023-03-08 00:59:34 ERROR - HTTP/1.1 500 Internal Server Error / {"message":"VismaId: 13f9eed0-3693-4df2-b601-4299af88fd0d. Error communicating with message broker"} 2023-03-08 01:17:59 ERROR - HTTP/1.1 500 Internal Server Error / {"message":"VismaId: 8c84e08d-2513-4827-abfd-763d95d38358. Error communicating with message broker"} 2023-03-08 01:22:06 ERROR - HTTP/1.1 500 Internal Server Error / {"message":"VismaId: 9664d53f-b6fb-4bbe-ae84-e91a0acff995. Error communicating with message broker"} 2023-03-08 01:25:41 ERROR - HTTP/1.1 500 Internal Server Error / {"message":"VismaId: 33373143-c2ee-48fb-8900-c5e9259c76f8. Error communicating with message broker"} 2023-03-08 02:45:16 ERROR - HTTP/1.1 500 Internal Server Error / {"message":"VismaId: b808ec27-eb44-40b5-a2c2-188ea87e33de. Error communicating with message broker -Timo-
... View more
09-03-2023
13:04
Hi, yesterday 7.3. at 16:50 local Finnish time we sent our customers salesorder request via api : POST https://integration.visma.net/API/controller/api/v1/salesorder As response we got: HTTP/1.1 500 Internal Server Error / {"message":"VismaId: 34a3a460-b31f-4a62-99b7-17fa8cb5a39c. Error communicating with message broker"} Despite the error code, a new SalesOrder instance was added in Visma.net. Due to the error message, our integration interpret that the request had not been received, and we resent a duplicate order to customers Visma.net company. Is this error 'Error communicating with message broker' such that it always requires a closer check for success or failure? Wbr, Timo
... View more
02-03-2023
13:13
Hi, shipViaId and shipTermsId default values fields seems to be filled with values from the Customers Location now. These filelds seems to be visible in swagger documentation now, but they do not move into new SalesOrder.
... View more
26-10-2022
13:39
4 Kudos
Hi,
when adding a new SalesOrder via https://salesorder.visma.net/api/v3/SalesOrders (without giving the fields 'shipVia' and 'shipTermsID' in request) these field values become empty in the new Order.
I expected that these fields would get default values from the orders Customers Location (fields 'CCarrierID', 'CShipTermsID').
If I do add SalesOrder from UI or via API https://integration.visma.net/API/controller/api/v2/salesorder these fields are filled with values from the Customers Location.
Is it possible to get nextGenApi work in the same way as version V2?
Or is it possible to give fields 'shipVia and 'shipTermsId' in the request body in nextGen?
Did not find these fields in the nextGen SalesOrders Swagger documentation.
Regards, Timo
... View more
See more ideas labeled with:
19-10-2022
10:35
Hi,
if you POST an order/orderline with an 'inacticve' product, the response does not tell the right position (line index) of the problematic line. This happened with real customer data, but in our own tests too. Maybe you could check and improve the messaging?
While if you send an orderline with nonexisting product code(s) the response tells you the exact line position(s). Which is really good feature.
We had an case where inactive product was sent in lineindex 40, and the response told that it is in lineindex 48. Here is the response, for clarification:
{ "details": [ { "code": "0100-OutsideValidRange", "message": "Invalid or empty InventoryId", "parameters": { "property": "orderLines[48].inventoryId" } } ], "errors": { "DomainValidation": [ "Invalid or empty InventoryId" ] }, "title": "One or more validation errors occurred.", "status": 400, "detail": "Refer to the errors property for additional details", "instance": "/api/v3/SalesOrders" }
... View more
See more ideas labeled with:
14-10-2022
12:32
The resource is now working, thanks!
... View more
13-10-2022
14:18
Hi, get projects https://integration.visma.net/API/controller/api/v1/project?pageSize=10 gives error: {
"message": "VismaId: bf14f71b-6066-43f7-ab43-021296eda86d. Invalid column name 'PublicId'.\r\nInvalid column name 'SystemTemplate'."
} Is this known issue? Or is this only 'my problem? regars, Timo
... View more
05-07-2022
08:46
Hi, I am starting to learn/use the nextGen API SalesOrder. Has there been, or is there going to be some kind of on-line introduction, how to get started with this nextGen. I found the introduction pdf written by Yildrim (https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-service-Visma-net-ERP/ba-p/401436?attachment-id=11764) . Is there more info somewhere in forum? Wbr, Timo
... View more
01-06-2022
08:08
Same problem with all our integrations, starting yesterday afternoon ( and this concerns several customers). Please get roesources and solve this problem asap! Wbr, Timo
... View more
14-01-2022
12:24
For more information here is a picture of the field, marked with red pen
... View more
14-01-2022
12:21
Hi, trying to get leadTime ( VLeadTime in UI) via API GET request: /controller/api/v1/supplier. Is this field available/exposed in the Endpoint? In swagger document I can see that the field is a part of 'SupplierDetailsLineDto' model.
... View more
19-02-2021
12:27
Hi, our customer still has problems with this. The interface error message has changed format, but the message still does not mention the product key that is causing the problem. They had recently order with 800 lines, one product-id was erronous. Checking which one is pain. The error message is changed and is more informative but could you please add the erronous inventoryId in the error message? Error message now: {"message":"Error: Inserting 'Sales order line' record raised at least one error. Please review the errors.\r\nThe specified inventory ID or alternate ID cannot be found in the system.\r\nError: 'Warehouse' cannot be empty.\r\nError: 'Undership threshold %' cannot be empty.\r\nError: 'Overship threshold (%)' cannot be empty.\r\n"
... View more
29-01-2021
10:27
Sorry for the rubbish after signing. -Timo-
... View more
29-01-2021
10:24
Hi, What kind of error events rise up at '/resources/v1/notification/failed' endpoint? I set by mistake an erronous "hookUri" in the Subscription. In the UI 'webhook' -tab I can see that the notification is sent ( or tried to sent?), but this notification did not rise up in the '/resources/v1/notification/failed' endpoint. I think the situation is same if the "hookUri" - 'service endpoint' is down for some reason, for example because of maintenance . Is there a list of 'http response statuses' which will rise up in Vismanet '/resources/v1/notification/failed' endpoint? Should failures appear in the UI 'webhook' -tab some way? Does Visma.net retry to send a failed notification, or does it sent notification only once? Wbr, Timo What kind of events rise up at /resources/v1/notification/failed endpoint? If the target service given in subscription is downappearing at this Ticket Point
... View more
21-01-2021
14:55
The Inventory Note field should be made multilanguage and should also be published as such at the Inventory endpoint.
... View more
See more ideas labeled with:
21-01-2021
14:49
1 Kudo
For example Inventory endpoint produces the mulitilanguage 'Description' field value, only in default language. All languages are needed. This might be a problem with all multilanguage fields on all endpoints?
... View more
- Find more ideas tagged with:
- mulitilanguage
See more ideas labeled with:
21-01-2021
14:40
3 Kudos
Please, add Note to Inventory Get and Post methods.
... View more
See more ideas labeled with:
11-09-2020
10:22
1 Kudo
Hi Visma, This need has come directly from our Vismanet users. PONumber seems to be available in GET operation in "buyerReference" -field.
... View more
- Find more ideas tagged with:
- PONumber
- Supplierinvoice
03-09-2020
14:41
Hi, thanks, for quick answer. In my experience, you get this response "Inventory error: The unit conversion is missing." also when the inventoryId is not found from VismaNet at all. Our customer receives salesorders from their customers, with several rows = several inventoryIds. Every now and there has been incorrect inventoryId(s) and its quite frustrating to find out first which inventoryID:s are used in request, and there after to browse/check out Visma which inventoryId is missing or incorrect. It would be much more informable to give the incorrect inventoryIds in the response. For example 'Inventory error: Please check the status of inventories: xxxxxx,yyyyy,zzzzz....' -Timo-
... View more
03-09-2020
13:43
Hi, sending a request 'POST /API/controller/api/v1/salesorder' with inventoryId, which is not found from VismaNet, gives a response 'HTTP/1.1 400 Bad Request / {"message":"Inventory error: The unit conversion is missing."}. Is it possible to get the inventoryId(s) which are incorrect in the response? Sometimes there are several orderlines, and its hard do solve which inventoryId is incoorect. Wbr, Timo
... View more
- Find more ideas tagged with:
- api
- inventoryId
- SalesOrder
Activity Feed for Timo_O
- Posted Vastaus: Sub accounts not applied to sales order rows, HIGH priority on Forum in Developers Visma.net. 30-10-2023 14:35
- Got a Kudo for Expose PONumber(Purchase Order NUmber) in POST/PUT operations for SupplierInvoice Endpoint. 13-06-2023 09:18
- Got a Kudo for nextGen-Api: Posting Salesorder, fields 'shipVia and 'shipTermsId'. 08-05-2023 08:33
- Posted Vastaus: Sub accounts not applied to sales order rows, HIGH priority on Forum in Developers Visma.net. 12-04-2023 10:59
- Posted Vastaus: SalesOrder added via Api , despite response code 500 on Forum in Developers Visma.net. 10-03-2023 08:42
- Posted SalesOrder added via Api , despite response code 500 on Forum in Developers Visma.net. 09-03-2023 13:04
- Got a Kudo for nextGen-Api: Posting Salesorder, fields 'shipVia and 'shipTermsId'. 02-03-2023 14:10
- Posted Vastaus: nextGen-Api: Posting Salesorder, fields 'shipVia and 'shipTermsId' on Ideas in Developers Visma.net. 02-03-2023 13:13
- Kudoed Expose Generic Inquiries in API for erik-kle. 15-02-2023 08:52
- Got a Kudo for nextGen-Api: Posting Salesorder, fields 'shipVia and 'shipTermsId'. 02-01-2023 09:14
- Got a Kudo for nextGen-Api: Posting Salesorder, fields 'shipVia and 'shipTermsId'. 02-01-2023 09:13
- Posted nextGen-Api: Posting Salesorder, fields 'shipVia and 'shipTermsId' on Ideas in Developers Visma.net. 26-10-2022 13:39
- Posted nextGen API POST https://salesorder.visma.net/api/v3/SalesOrders , inactive product on Ideas in Developers Visma.net. 19-10-2022 10:35
- Posted Re: API Projects resource returns http status 500 on Forum in Developers Visma.net. 14-10-2022 12:32
- Kudoed PickPriority for locations under Get Warehouse for RRTT. 14-10-2022 07:08
- Posted API Projects resource returns http status 500 on Forum in Developers Visma.net. 13-10-2022 14:18
- Got a Kudo for Note is missinng on Inventory endpoint. 09-09-2022 09:39
- Posted NextGen API, introduction on Forum in Developers Visma.net. 05-07-2022 08:46
- Posted Sv: Processing Exception while reading ODP response on Forum in Developers Visma.net. 01-06-2022 08:08
- Kudoed Expose Inventory item Replenishment information to API for RRTT. 18-01-2022 07:01
Kudos from
Useful pages
Contact us
Copyright © 2022 Visma.com. All rights reserved.
Visma Finland
Visma Latvia
Visma Netherlands
Visma Norway
Visma Sweden
Visma Developers & Partners
Visma Latin America