Error during Shipper Document Creation - Object named order-entry/document::Shipper is not supported in version 1-beta2

[Craig Yu]

Hi Experts,

 

We tried to create a shipper from a sales order, but we received this error:

"Object named order-entry/document::Shipper is not supported in version 1-beta2".

We were wondering if we can try to create sales order/shipper through REST API in the next BETA.

 

We also want to confirm if Sage Intacct API be able to carry UDF from sales order into shipper by the UDF defined name.

For now, our project have to read the UDF from the sales order then put them into the creation request for the shipper.

 

Thanks!

[Sterio, Louis]

@Craig Yu Would you mind providing the full endpoint and full json body to your request? I will then take it back to do some testing and get back to you.

[Craig Yu]

Hi @Sterio, Louis,

 

We just wanted to see if we can create a shipper from a given sales order.

We connected to one of our dev company "TrueCommerceMPP-DEV" using OAuth2.

 

Here are the request and the error in the response.

 

POST /objects/order-entry/document::Shipper

{
  "documentType": "Shipper",
  "state": "pending",
  "transactionDate": "2024-07-09",
  "dueDate": "2024-08-12",
  "txnCurrency": "USD",
  "baseCurrency": "USD",
  "sourceDocument": {
    "key": "7873",
    "id": "Sales Order-SO-1762",
    "documentType": "Sales Order"
  }
}

RESPONSE

{
  "ia::result": {
    "ia::error": {
      "code": "invalidRequest",
      "message": "Object named order-entry/document::Shipper is not supported in version 1-beta2",
      "errorId": "REST-1033",
      "additionalInfo": {
        "messageId": "IA.OBJECT_NAMED_IS_NOT_SUPPORTED_IN_VERSION",
        "placeholders": {
          "RESOURCE_NAME": "order-entry/document::Shipper",
          "VERSION": "1-beta2"
        },
        "propertySet": {}
      },
      "supportId": "Y_Nd1WEB033%7EZo9MkP5T0Jv4mq--X9JtngAAAAY"
    }
  },
  "ia::meta": {
    "totalCount": 1,
    "totalSuccess": 0,
    "totalError": 1
  }
}

[Sterio, Louis]

Craig I am looking into this for you. Were you able to successfully create one and now you're trying to convert it?

[Craig Yu]

Thank you @Sterio, Louis.

 

No, I was not able to create a sales order.

So I tried to create one using Client UI, then try to convert it into a shipper by the REST API.

 

And below is the request and error when I was trying to create that sales order.

REQ

{
  "customer": {
    "id": "1"
  },
  "state": "submitted",
  "transactionDate": "2024-07-01",
  "dueDate": "2024-08-12",
  "txnCurrency": "USD",
  "baseCurrency": "USD",
  "lines": [
    {
      "dimensions": {
        "item": {
          "id": "1"
        },
        "warehouse": {
          "id": "1"
        },
        "location": {
          "id": "1"
        }
      },
      "unit": "Each",
      "unitQuantity": "1",
      "unitPrice": "650"
    }
  ]
}

 

RESP

{
  "ia::result": {
    "ia::error": {
      "code": "invalidRequest",
      "message": "Object named order-entry/document::Sales Order is not supported in version 1-beta2",
      "errorId": "REST-1033",
      "additionalInfo": {
        "messageId": "IA.OBJECT_NAMED_IS_NOT_SUPPORTED_IN_VERSION",
        "placeholders": {
          "RESOURCE_NAME": "order-entry/document::Sales Order",
          "VERSION": "1-beta2"
        },
        "propertySet": {}
      },
      "supportId": "6GCYRWEB035%7EZpCVWP5U0Ix4erw-qUs-pwAAABE"
    }
  },
  "ia::meta": {
    "totalCount": 1,
    "totalSuccess": 0,
    "totalError": 1
  }
}

[Sterio, Louis]

Thank you. I reproduced this issue and created an internal ticket to the application team to review.

[Sterio, Louis]

@Craig Yu I have some answers here. The API endpoint for order entry works in development however the working version is not yet pushed to production. I have just asked the engineering team to push that to production. Once I have a timeline, I will let you know and will provide a working payload for you.

[Sterio, Louis]

@Craig Yu This will be fixed on Aug 23rd and will be available for testing then

[Sterio, Louis]

@Craig Yu Please try again this should now be fixed.