to get a personalized navigation.
to get a personalized navigation.
Sub accounts have not been applied to sales order rows since 13.3.2023 when order is posted via API (
https://integration.visma.net/API/controller/api/v2/salesorder) (10.3.2023 was last sales order without problems with sub accounts)
Via UI there is no problem with sub accounts.
Sub accounts are set to be applied behind sales person:
Customer is Hydro Extrusion Finland Oy (Company ID 1882757)
Here is sample message:
{
"branchNumber": {
"value": 1
},
"customerOrder": {
"value": "LU00087456"
},
"customerRefNo": {
"value": "Sami.Ekholm"
},
"date": {
"value": "2023-04-11T06:05:54Z"
},
"description": {
"value": "lu;LU00087456;5637171594;LU00087456-1"
},
"gln": {
"value": "FI22544498"
},
"hold": {
"value": true
},
"lines": [
{
"branchNumber": {
"value": 1
},
"externalLink": {
"value": "1;L127192561;11311105;m"
},
"inventoryId": {
"value": "11311105L6600HR1"
},
"lineNbr": {
"value": 1
},
"note": {
"value": "1\nProductionBatch:lsu50686691\nColor:SA716JR RAL 9016 INTERPON D1036\nEfiBarQuantity:1"
},
"operation": "Insert",
"quantity": {
"value": 6.6
},
"requestedOn": {
"value": "2023-04-18T12:00:00"
},
"shipOn": {
"value": "2023-04-18T12:00:00"
}
}
],
"note": {
"value": "Pakkausohje:Bundle pack / Wrap machine packing\nPurchPoolId:"
},
"orderType": {
"value": "SO"
},
"requestedOn": {
"value": "2023-04-18T12:00:00"
},
"soShippingAddress": {
"value": {
"addressLine1": {
"value": "Korjalankatu 27"
},
"city": {
"value": "KOUVOLA"
},
"countryId": {
"value": "FIN"
},
"overrideAddress": [
{
"value": true
},
{
"value": true
}
],
"postalCode": {
"value": 45130
}
}
}
}
These sub accounts are very important to customer. Their bookkeeper noticed the problem while closing last period.
Hi,
When using a default SalesPerson on a customer we were able to reproduce this issue.
The workaround for now is to include the SalesPerson in the OrderLine when using the API.
We have asked the developers for an ETA for this issue.
Thank you!
Kind regards
Sandra Anté
Hi again,
The development team has found a potential fix for this issue, however this involves setting the default quantity of the salesOrderLines to 1.
Please check with the customer if this is an acceptable solution.
If so, we can activate it for them now.
Let us know their decision and if we need to raise this again with the development team for a different solution.
Kind regards
Sandra Anté
Hi!
What is the status of this case. Customer is waiting for the solution with high priority. These sub accounts are very important to customer. Their bookkeeper noticed the problem while closing last period.
Hi,
The development team is looking into this case and would need some more information.
Could you please send an email to developersupport@visma.com with the companyID?
Thank you.
Hi,
It's in the developers backlog, we'll ask them for an ETA.
Hi!
For the sales order Visma.net chooses default location for selected customer. Sales persons are set for every location and default sales person is selected for default location. This works fine with UI and API endpoint v1.
Thank you, we'll inform the development team and get back to you as soon as we have more information.
Hi!
What is the status of this case. Customer is waiting for the solution with high priority. These sub accounts are very important to customer. Their bookkeeper noticed the problem while closing last period.
Hi!
What is the status of this case. Customer is waiting for the solution with high priority. These sub accounts are very important to customer. Their bookkeeper noticed the problem while closing last period.
Hi,
Are you sending the salesPerson field in your JSON? Can't see it in the post above, or do you have some setup that automatically sets the salesperson due to some other field?
Hi,
Salesperson is not in JSON. Salesperson comes from behind customer data and sub accounts are behind salespersons. This works just fine when using UI or V1 endpoint.
How is it setup to be automated? Do they have 1 salesperson per customer?
If so, does this happen to all orders? If not, in what way is the salesOrder set to get the salesPerson?
Hi!
For the sales order Visma.net chooses default location for selected customer. Sales persons are set for every location and default sales person is selected for default location. This works fine with UI and API endpoint v1.
We have recently discovered an issue when posting a new sales order to the Visma.net API when using the v2 endpoint for at least one company id (not others to our knowledge). The issue is that all item lines get 0% VAT (should be 25% VAT). VAT is correct when using the v1 endpoint.
The CompanyID is 3083136.
This seems to be a different case than the main post, please create a new post for new issues.
I didn't post this in this thread, I think the forum has merged the two threads.
The URL for my post was:
which now seems to redirect here, but sure I'll make another try.
New thread:
Copyright © 2022 Visma.com. All rights reserved.