Odata Serivce Batch and Bulk Persistence Request is errored out always

[former_member727035]

Hi Experts,

I am trying to use $Batch in Odata services to import sample configuration mentioned in commerce documentation.

The request is getting errored out always. Any quick help will be truly appreciated.

https://help.sap.com/viewer/50c996852b32456c96d3161a95544cdb/2005/en-US/0d45f25361294a99997837ccbdf1...

[former_member536008]

Can you provide more information on the error? What's the error message, payload posted, IO definition? It's hard to suggest a solution without details.

[former_member739630]

Hi Johnny Loi,

All the details are present in the page link attached, i am not using any custom payload but simply testing OOTB oData support.

On a high level analysis, i found out it might be happening due to following reason.

1. The request is being treated as Multipart and CommonsMultipartResolver is reading the request before the request actually hits the controller.
2. isMultiPart method present in CommonsMultipartResolver is looking more generic content type "multipart/"
3. When the request hits the controller, the body is empty.
4. This issue is happening only for $batch and one item upload is working

Response error:

{
 "error": {
 "code": "odata_error",
 "message": {
 "lang": "en",
 "value": "An error occurred while processing the request. The most likely cause of this error is the formatting of your OData request payload. Please verify the request payload format corresponds to the EDMX metadata for the Entity that you are attempting to create."
 },
 "innererror": ""
 }
}

Request and headers-

Headers -

 Content-Type : multipart/mixed; boundary=batch
 Authorization : Basic 

POST {{host}}/odata2webservices/InboundCategories/$batch
Authorization:Basic{{user}}{{password}}Content-Type: multipart/mixed; boundary=batch

--batch
Content-Type: multipart/mixed; boundary=changeset

--changeset
Content-Type: application/http
Content-Transfer-Encoding: binary

POST Categories HTTP/1.1Accept: application/json
Content-Type: application/json



{"@odata.context":"$metadata#Categories/$entity","code":"category-21","name":"Category 21"}
--changeset
Content-Type: application/http
Content-Transfer-Encoding: binary

POST Categories HTTP/1.1Accept: application/json
Content-Type: application/json



{"@odata.context":"$metadata#Categories/$entity","code":"category-22","name":"Category 22"}
--changeset----batch
Content-Type: multipart/mixed; boundary=changeset

--changeset
Content-Type: application/http
Content-Transfer-Encoding: binary

POST Categories HTTP/1.1Accept: application/json
Content-Type: application/json



{"@odata.context":"$metadata#Categories/$entity","code":"category-23","name":"Category 23"}
--changeset
Content-Type: application/http
Content-Transfer-Encoding: binary

POST Categories HTTP/1.1Accept: application/json
Content-Type: application/json 

{"@odata.context":"$metadata#Categories/$entity","code":"category-24","name":"Category 24"}

--changeset--

--batch--

[adam_dryglak]

If you are using Postman, then verify that the correct Content-Type will be send in the Headers: