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
JohanFriedrichs
30
Posts
1
Kudos
0
Solutions
07-11-2024
13:04
Prior to v3 when an orderline was Marked for PO the corresponding source was automatically picked up from the inventory item. The same thing happens when an order line is manually marked in the UI. In v3 the source is a mandatory which requires the integration to know more information that is actually already in the system. Is this intended?
... View more
07-11-2024
09:56
During migration to SalesOrder v3 we have come across some behavioural changes that might require customer intervention before code is released. It is therefor imperative that we understand the correct intended behaviour. Question: Some of the order lines sometimes miss a value in the tax category field when creating a v3 order. It seems to occur when the item is missing an item class. If the same order is created manually in the UI then it receives the correct tax category. Is this intentional?
... View more
21-08-2024
11:45
19/6: It was communicated that the deadline was EXTENDED to 31/3 2025 20/8: New deadline is communicated that is again 31/12 2024 (3 months SHORTER than last communicated) So the planning that was made based on the 19/6 communication means that not only did we loose 2 months of possible work during the summer but we also have a shorter time fram until deadline? Does this mean that the timeframe can be even shorter?
... View more
20-08-2024
15:46
Is it correct that the due date for the removal of the Sales Order endpoints have changed AGAIN? Back to 31st of December 2024?
... View more
19-01-2024
14:55
When POST:ing a new SalesOrder the enpoint is just responding with a successful HTTP-response. If the integration needs to access the created order you are uinstructed to GET it using the address in the location-header. At a couple of instances the Visma API has had problems so the GET has resulted in a 502 response. This makes it impossible to know if the order was created correctly. The request is to include the created object in the POST resonse body to eliminate the need for the extra GET request.
... View more
19-01-2024
12:40
That is what we are trying to do but in the cases where the API-response is 502 we'll get a problem. Since customers want to to take advantage of the automations in Visma.net we need to know about the actual order created. Would it be possible to include the created object in the response in the v3 version of the API? That would give us the information needed without an extra API-call.
... View more
15-01-2024
11:20
I have done some more digging and here is the problem: When we create an order we need some information about the created order to continue working with it. However, the order POST just responds with a 201 but no order payload so we need to manually fetch the new order to get the information that we need. On this occation (5:th of january at 12:24) the POST was successful but a GET to the location header address from the POST resulted in a 502 Bad Gateway. That was seen as an incomplete POST and therefor the order was sent again resulting in a duplicate order. So technically it wasn't the API that created the duplicate but since the POST didn't respond with the created order (which is the most common way) it lead to the error. From what I can see in the SalesOrder documentation the POST still doesn't contain a response payload so this logical problem can continue to come up in the future. How should this be handled in the best way?
... View more
08-01-2024
10:35
Hi I can see that there has been a few threads about the "502 Bad gateway" reponse before. Our problem isn't the response itself but the fact that the response doesn't reflect what is actually happening in the back end: We try to send orders, get the 502 response but it seems like the order is created anyway. The problem here is that the response is treated as unsuccessful and therefor we try to send the order again which leads to duplicates in Visma.net. We need to be able to rely on the response and not have to double check everything. Is this behaviour somthing that will change once we transition to the SalesOrder-API?
... View more
22-11-2023
14:46
When will the Sales Order Service API be available for interactive authentication?
... View more
03-11-2023
09:16
More information: 3 customers have tried this week and they have all failed with the same message. It worked last week for at least 1 customer.
... View more
03-11-2023
08:43
Some of our users get an error page during the Oauth-flow using the new authentication. It is only for some of the users so the application should be configured correctly. The debugger says: "Message - Unhandled exception: Failed to update tenant consent for user xxx" Last week other users were able to authenticate using the same app and they haven't reported any problems. How to proceed?
... View more
16-08-2023
08:21
Correction: the problem occurs with SalesOrder but not with SalesOrderv2 It is the contacts that are affected. If "overrideContact" = false is combined with additional values (see below) on the first SO for a customer these values will be used on this SO and every consecutive SO, regardless of if it is created via API or manually. "soBillingContact": { "value": { "overrideContact": { "value": false }, "name": { "value": "Billing Contact" }, "attention": {}, "email": { "value": "billing.contact@mail.com" }, "phone1": {}, "phone2": {}, "fax": {} } }, It can be argued that override and extra values shouldn't be used at the same time but there is nothing stopping it (tehcnically or in the docs). The effects are also very problematic since it will affect every future SO. Regarding the use of v1 over v2: we had prior to this no urgent reason to move to v2 since the focus was on the initial SalesOrderService timeline. But since that has been pushed we have to rethink what we need to do.
... View more
27-06-2023
09:04
No, there is no technical reason. I believe that my collegue have verified this behaviour manually with v2 also.
... View more
22-06-2023
14:55
HTTP POST to https://integration.visma.net/API/controller/api/v1/salesorder {
"orderType": {
"value": "SO"
},
"orderNumber": {
"value": "007-75"
},
"customerVATZone": {
"value": "01"
},
"soBillingContact": {
"value": {
"overrideContact": {
"value": false
},
"name": {
"value": "Kajsa Testar"
},
"attention": {},
"email": {
"value": "external.accounts@sharespine.com"
},
"phone1": {
"value": "0000000000"
},
"phone2": {},
"fax": {}
}
},
"soBillingAddress": {
"value": {
"overrideAddress": {
"value": false
},
"addressLine1": {
"value": "PB adress"
},
"addressLine2": {},
"postalCode": {
"value": "45132"
},
"city": {
"value": "Uddevalla"
},
"county": {},
"countryId": {
"value": "SE"
}
}
},
"soShippingContact": {
"value": {
"overrideContact": {
"value": false
},
"name": {
"value": "Kajsa Testar"
},
"attention": {},
"email": {},
"phone1": {
"value": "0000000000"
},
"phone2": {},
"fax": {}
}
},
"soShippingAddress": {
"value": {
"overrideAddress": {
"value": false
},
"addressLine1": {
"value": "PB adress"
},
"addressLine2": {},
"postalCode": {
"value": "45132"
},
"city": {
"value": "Uddevalla"
},
"county": {},
"countryId": {
"value": "SE"
}
}
},
"date": {
"value": "2023-05-09T10:45:39.000"
},
"shipVia": {
"value": "DHL"
},
"branchNumber": {
"value": "1 "
},
"printDescriptionOnInvoice": {
"value": false
},
"printNoteOnExternalDocuments": {
"value": false
},
"printNoteOnInternalDocuments": {
"value": false
},
"note": {
"value": "."
},
"currency": {
"value": "SEK"
},
"customer": {
"value": "10990"
},
"status": {
"value": "open"
},
"hold": {
"value": false
},
"lines": [
{
"operation": "Insert",
"warehouse": {
"value": "2"
},
"inventoryNumber": {
"value": "test123"
},
"lineDescription": {
"value": "En mycket fin testprodukt"
},
"quantity": {
"value": 1.0
},
"unitPrice": {
"value": 15.2
}
}
]
}
... View more
22-06-2023
07:53
In our current order integration we have an option that controls the overrideContact flag. Regardless of that setting is true or false we are sending contact details on the order if those are available in the order source (I don't have the reason why this is done). The result if we create an order with overrideContact: false is that the order is created with the supplied contact details even though the contact shouldn't be overridden. The bigger problem is that the next order you create for the same customer will also inherit the same details even if the order is done manually via the GUI. 1. Is it intended that supplied contact details takes precedence over the override flag? If so this needs to be documented. 2. It can be argued that you shouldn't send both details and override: false but it isn't documented that you can't. It would be OK if it only affected the current order but since it also affects future orders it feels that the API should handle it better. 3. Does the SalesOrder service handle this type of behaviour better?
... View more
12-04-2023
10:34
When will the new removal date be communicated? We would like to plan our customer communication so that it will include both required authentication changes and information about the sales order changes.
... View more
05-04-2023
14:10
We're planning an authentication upgrade of 60+ customers in preparation of moving to the SalesOrder service. However, there seem to be more and more issues where the "solution" is to use the old auth model or v1/v2 endpoints. This seems a bit strange sine the communicated deadline is now less than 2 months away. With multiple customers affected we need to be sure that we can have clear communication with them regarding when things need to change. As it seem right now this is not a production ready implementation.
... View more
31-03-2023
07:20
If we want to build a Single-Page Application (SPA) that handles orders how would we go about it given that the order api can only be accessed using client-credential-auth?
... View more
20-03-2023
08:28
Ok, but the Sales Order Service API should today contain features that cover the endpoints that are going to be removed in June?
... View more
15-03-2023
17:40
Do you have a list of parameters that have changed name so that it is possible to verify that we have 100% feature coverage? Example from Finance-API (GET /controller/api/v1/salesorder/{orderType}/{orderNbr}): "printDescriptionOnInvoice": true, "printNoteOnExternalDocuments": true, "printNoteOnInternalDocuments": true Service: "print": { "descriptionOnInvoice": true, "noteOnInternalDocuments": true, "noteOnExternalDocuments": true } Service respons has different structure and parameter names which makes it very easy to miss missing features.
... View more
15-03-2023
17:35
Is all of the features of the SalesOrder service implemented so that it should be possible to migrate from the old to the new? It is vital that we know that the support is there before we dig to deep. Time is flying quickly and since we have multple customers that are affected by these changes (due to the new auth etc) we need to inform and implement our changes well before the deprication date.
... View more
15-03-2023
17:02
1 Kudo
In this response (https://community.visma.com/t5/Forum-in-Developers-Visma-net/Problem-with-scopes-in-Visma-App-Store/m-p/560932/highlight/true#M3207) it is stated that you are working on unifying the SalesOrder and Financial-API tokens. - Is this something that will be done before the endpoint deprication? Would save a lot of work. - Is there a reason why the interactive token isn't valid for the SalesOrder service?
... View more
29-11-2022
13:54
Any updates on this question? We would like to be able to get the next delivery date as a parameter on the inventory item itself. Would that be possible?
... View more
14-09-2022
09:34
When calling the GET /controller/api/v1/attribute the documentation states that the response should include a lastModifiedDateTime. However, we only receive this: {
"attributeID":"ARF",
"description":"arf",
"controlType":"Text",
"internal":false,
"details":[],
"metadata":{
"totalCount":18,
"maxPageSize":1000
}
} Is it a bug or some sort of setting that needs to be set?
... View more
14-09-2022
08:58
Any update on this? We have more customer related information but it isn't something that is suitable to post in an open forum.
... View more
08-09-2022
13:17
Yes, we have examples of both kinds of results but we have not been able to see any pattern between them (yet). SPAS0480170 {"id":"WEBARTICLE","value":"1"} SPAG0480170 {"id":"WEBARTICLE","value":"1"} SPBL04120240 {"id":"WEBARTICLE","value":"True"} SPAG03120240 {"id":"WEBARTICLE","value":"True"}
... View more
08-09-2022
11:16
A customer has added an inventory attribute as a checkbox called WEBARTICLE. When using a GET on /inventory and expanding attributes some inventories return the attribute as "1" and some as "True". Why is this? No filtering is used, just expanding. The full call is: https://integration.visma.net/API/controller/api/v1/inventory?addCostPriceStatistics=true&expandCrossReference=true&expandAttachment=true&expandAttribute=true&expandWarehouseDetail=true&expandSupplierDetails=true&expandSalesCategories=true&expandAccountInformation=true&pageSize=100&pageNumber=1&orderBy=lastModifiedDateTime
... View more
24-01-2022
07:36
The issue that we're having when moving to the v2 POST of CustomerInvoices is that the the location-header returned is incorrect. Your documentation doesn't mention a v2 of the GET endpoint, just the POST. Is this something that will be corrected?
... View more
20-12-2021
08:31
Hi In the POST of /customerpayments it is (according to the documentation) possible to add "paymentlines" with the documentType FinCharge. What is that suppose to do? I have not been able to complete a successful POST with lines of that documentType. Is there any special circumstances that need to be met?
... View more
09-12-2021
14:14
Hi Have you been able to test this? Is the current "solution" to create orders with hold status true?
... View more
Activity Feed for JohanFriedrichsen
- Posted Mark for PO in v3 on Forum in Developers Visma.net. 07-11-2024 13:04
- Posted V3 order line missing tax category on Forum in Developers Visma.net. 07-11-2024 09:56
- Posted Svar: [Release Notes] - Visma.Net API 10.14.0 - 20-08-2024 on News in Developers Visma.net. 21-08-2024 11:45
- Posted Svar: [Release Notes] - Visma.Net API 10.14.0 - 20-08-2024 on News in Developers Visma.net. 20-08-2024 15:46
- Posted Return created object in POST response body on Ideas in Developers Visma.net. 19-01-2024 14:55
- Posted Svar: 502 Bad gateway response but order is created anyway on Forum in Developers Visma.net. 19-01-2024 12:40
- Posted Svar: 502 Bad gateway response but order is created anyway on Forum in Developers Visma.net. 15-01-2024 11:20
- Posted 502 Bad gateway response but order is created anyway on Forum in Developers Visma.net. 08-01-2024 10:35
- Posted Interactive use of Sales Order Service? on Forum in Developers Visma.net. 22-11-2023 14:46
- Posted Svar: VISMA net shows error page during OAuth flow on Forum in Developers Visma.net. 03-11-2023 09:16
- Posted VISMA net shows error page during OAuth flow on Forum in Developers Visma.net. 03-11-2023 08:43
- Posted Re: OverrideContact: false gives incorrect details on Forum in Developers Visma.net. 16-08-2023 08:21
- Posted Re: OverrideContact: false gives incorrect details on Forum in Developers Visma.net. 27-06-2023 09:04
- Posted Re: OverrideContact: false gives incorrect details on Forum in Developers Visma.net. 22-06-2023 14:55
- Posted OverrideContact: false gives incorrect details on Forum in Developers Visma.net. 22-06-2023 07:53
- Got a Kudo for Unified token management SalesOrder/Financial?. 28-04-2023 08:42
- Posted Re: No access to branch when trying to create SupplierInvoice on Forum in Developers Visma.net. 12-04-2023 10:34
- Posted Re: No access to branch when trying to create SupplierInvoice on Forum in Developers Visma.net. 05-04-2023 14:10
- Posted Single-Page Application (SPA) and SalesOrder service on Forum in Developers Visma.net. 31-03-2023 07:20
- Kudoed Questions regarding web application authentication and authorization for Michel V. 29-03-2023 16:30
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