<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Execute delete request using payload in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/execute-delete-request-using-payload/m-p/12236760#M1984875</link>
    <description>&lt;P&gt;Hi, &lt;BR /&gt;DELETE requests usually are sent with no payload.&lt;BR /&gt;The &lt;A href="http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#_Toc31358982"&gt;OData Spec says&lt;/A&gt;, "should" be empty&lt;BR /&gt;But even if not forbidden, I assume no OData library would handle a payload in DELETE request&lt;BR /&gt;I guess, unforeseen data mismatch can occur between server and client if the contract of DELETE is not clear, in the sense that data is removed without changing the state&lt;BR /&gt;In your use case, maybe you can use custom header for sending additional info? &lt;BR /&gt;Or even custom URL param?&lt;/P&gt;&lt;P&gt;Kind Regards,&lt;BR /&gt;Carlos&lt;/P&gt;</description>
    <pubDate>Wed, 19 Aug 2020 07:22:25 GMT</pubDate>
    <dc:creator>CarlosRoggan</dc:creator>
    <dc:date>2020-08-19T07:22:25Z</dc:date>
    <item>
      <title>Execute delete request using payload</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/execute-delete-request-using-payload/m-p/12236759#M1984874</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
  &lt;P&gt;Please let me know if it is possible to pass payload while executing a delete request in Odata.&lt;/P&gt;
  &lt;P&gt;I have a requirement where I need to validate &amp;amp; update few values in table ( based on the values passed from payload) and then process the delete request.&lt;/P&gt;
  &lt;P&gt;Thanks in advance! &lt;/P&gt;</description>
      <pubDate>Wed, 19 Aug 2020 07:02:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/execute-delete-request-using-payload/m-p/12236759#M1984874</guid>
      <dc:creator>divyanarayanan94</dc:creator>
      <dc:date>2020-08-19T07:02:24Z</dc:date>
    </item>
    <item>
      <title>Re: Execute delete request using payload</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/execute-delete-request-using-payload/m-p/12236760#M1984875</link>
      <description>&lt;P&gt;Hi, &lt;BR /&gt;DELETE requests usually are sent with no payload.&lt;BR /&gt;The &lt;A href="http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#_Toc31358982"&gt;OData Spec says&lt;/A&gt;, "should" be empty&lt;BR /&gt;But even if not forbidden, I assume no OData library would handle a payload in DELETE request&lt;BR /&gt;I guess, unforeseen data mismatch can occur between server and client if the contract of DELETE is not clear, in the sense that data is removed without changing the state&lt;BR /&gt;In your use case, maybe you can use custom header for sending additional info? &lt;BR /&gt;Or even custom URL param?&lt;/P&gt;&lt;P&gt;Kind Regards,&lt;BR /&gt;Carlos&lt;/P&gt;</description>
      <pubDate>Wed, 19 Aug 2020 07:22:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/execute-delete-request-using-payload/m-p/12236760#M1984875</guid>
      <dc:creator>CarlosRoggan</dc:creator>
      <dc:date>2020-08-19T07:22:25Z</dc:date>
    </item>
    <item>
      <title>Re: Execute delete request using payload</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/execute-delete-request-using-payload/m-p/12236761#M1984876</link>
      <description>&lt;P&gt;Hello, &lt;/P&gt;&lt;P&gt;It’s not possible to use payload in delete request and you can do few tweaks like use update request instead of delete and within class method first validate and update values and then go for delete code. You can think of using function imports.&lt;/P&gt;&lt;P&gt;Many times we get requirement where we cannot use standard processes for CRUD as dictated by guidelines. In such scenarios we have to tweak standard process as per our requirement. I know it’s not best way but sometime have to go for it because of no other option.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Thanks,&lt;/P&gt;&lt;P&gt;Dhiraj M&lt;/P&gt;</description>
      <pubDate>Wed, 19 Aug 2020 18:26:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/execute-delete-request-using-payload/m-p/12236761#M1984876</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2020-08-19T18:26:52Z</dc:date>
    </item>
  </channel>
</rss>

