REST API Sales Order discount details: 'Type' cannot be empty

The ‘Type’ option keys are:

Line = "L"
Group = "G"
Document = "D"
ExternalDocument = "B"
Flat = "F"

Have you tried “D” instead of “Document”?

Thanks for the reply, Daryl! I’m curious where this list is located, I didn’t see it in the documentation.

Sadly, sending “D” rather than “Document” did not resolve the issue. The API still complains about the type field.

Here’s the relevant excerpt from the response:

  "DiscountDetails": [
    {
      "id": "e61ac7d6-6778-4f02-aadc-b0655defb1fe",
      "rowNumber": 1,
      "note": null,
      "Description": {
        "value": "Coupon Discount"
      },
      "DiscountableAmount": {},
      "DiscountableQty": {},
      "DiscountAmount": {
        "value": 0.6
      },
      "DiscountCode": {
        "value": "COUPON"
      },
      "DiscountPercent": {
        "value": 0
      },
      "ExternalDiscountCode": {},
      "FreeItem": {},
      "FreeItemQty": {},
      "ManualDiscount": {
        "value": true
      },
      "SequenceID": {
        "value": "TATER15"
      },
      "SkipDiscount": {
        "value": false
      },
      "Type": {
        "error": "'Type' cannot be empty."
      },
      "custom": {}
    }
  ],

May be a red herring, but it’s curious to me that the response says DiscountPercent = 0, as opposed to the 15 which I sent to the API endpoint.

I believe it is a red herring. Type is not even editable from the UI.

I am able to add a discount to an existing SO with this (however, the DiscountAmount is not being respected for me either, but it’s a step closer):

Host: entity/Default/23.200.001/SalesOrder?$expand=DiscountDetails&$select=OrderType,OrderNbr,DiscountDetails/DiscountCode,DiscountDetails/SequenceID,DiscountDetails/DiscountAmount

{
    "OrderType": {
        "value": "SO"
    },
    "OrderNbr": {
        "value": "SO007748"
    },
    "DiscountDetails": [
        {
            "DiscountCode": { "value": "DOC00C000" },
            "SequenceID": { "value": "USBAR" },
            "DiscountAmount": { "value": 10.6 }
        }
    ]
}

Hi all,

I have been working on a similar problem on and off for months and came across this post in searching for an answer. I too was able to get the discount entered but couldn’t get the API to pay attention to the discount percentage or discount amount I was sending. ​@dominicfedco - I can see that you were able to get the discount entered by using a second request, but my client - for whatever reason - needed it all done within one request.

Today I am ecstatic to say that I have finally found the answer. Despite the fact that the ‘Type’ field is not editable through the UI, setting this field to ‘External Document’ and removing the ‘DiscountCode’ and ‘SequenceID’ fields from the message payload allows the discount percentage or discount amount to be set to the value specified in the message payload. I guess this must tell Acumatica that the discount is being set by an external application and that it should not pay any attention to discounts already configured in the application.

I hope this helps anyone else that stumbles across this post looking for the same answers that I was!

Cheers all,

Ben.

Thank you for sharing your solution with the community ​@benb1977!