Sub accounts not applied to sales order rows, HIGH priority

[RRTT]

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.

[RRTT]

Hi!

What is the status of this case?

[Sandra Anté]

Hi again,

The fix is turned on for this customer now.

We will write and update in the case when it is active in prodcution.

Kind regards
Sandra

[Sandra Anté]

Hi,

this issue is in the development teams backlog.

We'll ask them for an ETA on the issue.

Kind regards
Sandra

[RRTT]

Hi!

What is the status of this case?

[Sandra Anté]

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é

[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é

[RRTT]

Hi,

Setting the default quantity of the salesOrderLines to 1 is ok to the customer. So please proceed with the fix.

[RRTT]

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.

[Magnus Johnsen]

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. 

[Timo_O]

Company number sent to 'developersupport@visma.com '

[Magnus Johnsen]

Hi,

It's in the developers backlog, we'll ask them for an ETA.

[RRTT]

Hi there!

What is the status of this case?

[RRTT]

Hi!

What is the status of this case?

[RRTT]

Hi!

What is the status of this case?

[RRTT]

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. 

[Magnus Johnsen]

Thank you, we'll inform the development team and get back to you as soon as we have more information.

[RRTT]

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.

[RRTT]

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.

[Magnus Johnsen]

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?

[RRTT]

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.