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.
I see, thank you, I'll have a look
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:
Could you please investigate, to get sub acoounts working properly in v2?
Copyright © 2022 Visma.com. All rights reserved.