My Products
Help
RRTT
CHAMPION ***

Supplier data is not applied to sales order rows when using API v3

by RRTT

Supplier ID, name, supplier price etc. are not applied from the stock item data when using API v3.

API v2 works fine with these.

RRTT_0-1692009800644.png

 

RRTT_1-1692009865137.png

 

6 REPLIES 6
Accepted solution
Yıldırım
VISMA

by Yıldırım (Updated ‎18-08-2023 14:00 by Yıldırım VISMA )

Hello, just an update, following is the status of the V3 Sales Order Endpoint on Inventory (Supplier Details). 


It is set up right now that the supplier data is set to the line if/when the "purchase order source" is specified in the payload, as the supplier is used when creating PO for the order line. So, In order POST SalesOrder V3 to be able to fetch the Supplier data of the selected item,  

"purchaseOrderSource": "string" should be specified in the payload. 
source_Swagger UI.jpg

 

Example:

{
    "type": "SO",
    "date": "2023-08-18",
    "description": "Test Sales Order",
    "customer": {
        "id": "10022"
    },
    "orderLines": [
        {
            "inventoryId": "1",
            "description": "Test Sales OrderLine 1",
            "quantity": 5,
            "unitPrice": 10,
            "taxCategoryId": "3",
            "unitOfMeasure": "STK",
            "purchaseOrderSource": "purchaseToOrder",
            "subaccount": {
                "1": "00",
                "2": "01",
                "3": "03",
                "4": "04"
            }
        }
    ]
}
Yıldırım
VISMA

by Yıldırım

Hello, we confirm the issue. This has been registered as a bug, and we'll keep you informed on any progress. 

RRTT
CHAMPION ***

by RRTT

Hi! Please high prioritize this, as customer is creating purchase orders directly from sales orders and now this is very difficult almost impossible.

Yıldırım
VISMA

by Yıldırım

Hi, unfortunately we don't have information on how fast this can be resolved, therefore if it's urgent, we recommend using v2 until the fix. 

RRTT
CHAMPION ***

by RRTT

Hi!

 

It would be quite expensive for the customer to get the third party to build a new integration to v2. In this case v2 has not been used earlier. I am sure they will not accept that as a solution.

Yıldırım
VISMA

by Yıldırım

Hello, thanks for reporting, we'll look into this.