Skip to main content
Solved

i am not able create check for bill through rest api after upgrade acumatica

  • October 21, 2024
  • 7 replies
  • 217 views

Forum|alt.badge.img

i am not able create check after upgrade acumatica in october 2024
got this error
{"message":"The request is invalid.","modelState":{"":["An exception occurred during input parsing"]}}
please suggest me but missing 
my endpoint 
https://local//entity/Acumatica/1.0.3/Check
json body this 
{"CuryOrigDocAmt":{"value":0},"CashAccount":{"value":"10060"},"Type":{"value":"Check"},"Vendor":{"value":"V001097"},"CurrencyID":{"value":"USD"},"Hold":{"value":false},"PaymentAmount":{"value":10.19},"PaymentMethod":{"value":"CREDITCARD"},"Details":[{"CashAccount":{"value":"10060"},"PostPeriod":{"value":"102024"},"BranchID":{"value":null},"InventoryID":{"value":null},"OrderQty":{"value":0},"WarehouseID":{"value":null},"AmountPaid":{"value":10.19},"Balance":{"value":10.19},"CashDiscountBalance":{"value":null},"DocType":{"value":"Bill"},"ReferenceNbr":{"value":"001301"}}],"PostPeriod":{"value":"102024"}}

Best answer by jinin

Hi @DharmandarKumar ,

We can create the check using the Acumatica default endpoint. Please refer to the sample of the endpoint below,
 

Url: /entity/Default/22.200.001/Check
Method: Put

Request:

{

    "CashAccount": {

        "value": "10200"

    },

    "Description": {},

    "Hold": {

        "value": true

    },

    "PaymentAmount": {

        "value": 10

    },

    "PaymentMethod": {

        "value": "CHECK"

    },

    "PaymentRef": {},

    "ReferenceNbr": {

        "value": "002329"

    },

    "Status": {

        "value": "On Hold"

    },

    "Type": {

        "value": "Payment"

    },

    "Vendor": {

        "value": "ATDSECUR"

    },

    "Details": [

        {

            "AmountPaid": {

                "value": 10

            },

            "CashAccount": {

                "value": "10200"

            },

            "DocType": {

                "value": "Bill"

            },

            "ReferenceNbr": {

                "value": "003647"

            }

        }

    ]

}
 

 

7 replies

Dmitrii Naumov
Acumatica Moderator
Forum|alt.badge.img+7
  • Acumatica Moderator
  • October 21, 2024

@DharmandarKumar why do you use a custom endpoint here? I’d recommend using the default one. 

 


Forum|alt.badge.img

custom endpoint because we have some changes on our endpoint

 


Dmitrii Naumov
Acumatica Moderator
Forum|alt.badge.img+7
  • Acumatica Moderator
  • October 21, 2024

@DharmandarKumar I see that it is a custom one. The question is why? You should use the default one.


Forum|alt.badge.img

@Dmitrii Naumov  before upgrade i am able to create check using this endpoint and this json body but now i can not create chcek


jinin
Pro I
Forum|alt.badge.img+11
  • Pro I
  • Answer
  • October 21, 2024

Hi @DharmandarKumar ,

We can create the check using the Acumatica default endpoint. Please refer to the sample of the endpoint below,
 

Url: /entity/Default/22.200.001/Check
Method: Put

Request:

{

    "CashAccount": {

        "value": "10200"

    },

    "Description": {},

    "Hold": {

        "value": true

    },

    "PaymentAmount": {

        "value": 10

    },

    "PaymentMethod": {

        "value": "CHECK"

    },

    "PaymentRef": {},

    "ReferenceNbr": {

        "value": "002329"

    },

    "Status": {

        "value": "On Hold"

    },

    "Type": {

        "value": "Payment"

    },

    "Vendor": {

        "value": "ATDSECUR"

    },

    "Details": [

        {

            "AmountPaid": {

                "value": 10

            },

            "CashAccount": {

                "value": "10200"

            },

            "DocType": {

                "value": "Bill"

            },

            "ReferenceNbr": {

                "value": "003647"

            }

        }

    ]

}
 

 


Forum|alt.badge.img
  • Jr Varsity III
  • February 19, 2025

Hi @DharmandarKumar ,

We can create the check using the Acumatica default endpoint. Please refer to the sample of the endpoint below,
 

Url: /entity/Default/22.200.001/Check
Method: Put

Request:

{

    "CashAccount": {

        "value": "10200"

    },

    "Description": {},

    "Hold": {

        "value": true

    },

    "PaymentAmount": {

        "value": 10

    },

    "PaymentMethod": {

        "value": "CHECK"

    },

    "PaymentRef": {},

    "ReferenceNbr": {

        "value": "002329"

    },

    "Status": {

        "value": "On Hold"

    },

    "Type": {

        "value": "Payment"

    },

    "Vendor": {

        "value": "ATDSECUR"

    },

    "Details": [

        {

            "AmountPaid": {

                "value": 10

            },

            "CashAccount": {

                "value": "10200"

            },

            "DocType": {

                "value": "Bill"

            },

            "ReferenceNbr": {

                "value": "003647"

            }

        }

    ]

}
 

 

 

@jinin Do you know why the default works over a custom endpoint? I had the same issue as ​@DharmandarKumar  where when i upgrade from 2023 R2 → 2024 R2 my custom endpoint stopped working for some action calls. This is not ideal as I have a custom endpoint because I access data that is not there by default in the “default” endpoint.


jinin
Pro I
Forum|alt.badge.img+11
  • Pro I
  • February 21, 2025

Hi ​@manley75 ,

We are also using custom endpoints in our projects but have not encountered any issues like this. The exact reason for this is unclear.