501 Error on Update #73
Comments
|
Hi Rafael, how does your Postman call look like? Another alternative (introduced with version 2.16.0) is using the Greetings |
|
Hi Chris, thanks for the response! On Postman I'm doing a The body of my request looks like: {
"d": {
"ChangeNumberStatus": "1"
}
}I'll try to run it with the Greetings, |
|
Hi Chris, We've tested it and the Thanks for the help! 😄 |
|
Hi Rafael, one question that came up during further investigation of the issue: which version where you using when the initial problem occurred? Currently we cannot reproduce the behavior with PATCH, neither with 2.16.0 nor with 2.8.1 (some arbitrarily chosen old version). Greetings |
|
Hi Chris, We were using version 2.13.2 before. I ran into the same problem with PATCH after updating to 2.16.0, but the PUT approach has solved our problems for now. Greetings, |
|
Hello Rafael, I ran into the same issue. Could you please share what is your request payload and how you can set attributes to {changedOriginalFields={Status=2}}? |
|
Hi Rafael, While we get to its root cause and potential resolution, we would like to seek some more information. We understand that in your request payload The field "ChangeNumberStatus" is actually not modified. That is, its value is the same as that of the persisted Business Partner entity. Is this correct? If so, would it be possible for you to let us know what is the business use case here? Best regards, |
|
Hi Akhil and all, I'm working with Rafael on this issue. We were using the builder from To workaround this behavior, we created a wrapper for Is that the correct behavior? It seems In case it helps, below is the SDK-generated method on /**
* Constraints: Not nullable, Maximum length: 40 <p>Original property name from the Odata EDM: <b>ChangeNumberDescription</b></p>
*
* @param description
* Change number description
*/
public void setDescription(
@Nullable
final String description) {
rememberChangedField("Description", this.description);
this.description = description;
}Thank you for your help and regards, |
|
Hi Tales, thanks for your response! The issue with the wrong key in the Regarding your workaround: The expected usage of the I hope this clears the issue up! Greetings |
|
Hi Chris, We verified that indeed the 2.17.0 version fixed the property naming issue. Regarding the PATCH API, we didn't want to perform a GET just to update the entity, since in our case the synchronization is one-way (i.e. object won't be changed in S/4 directly). It seems we'll be able to achieve this with version 2.17.0, calling the API with Thank you again for your help. |
|
Hi Tales, The instead of as Greetings |
Hello colleagues,
We are working with the Change Master API and we are having some issues updating the status.
We are calling the API as:
While debugging, we could validate that
changemasteris set as:However, we get HTTP 501 error with the message:
Do you see anything that we could be doing wrong? When we try calling the API using Postman it works fine. Let me know if there's any additional info that we could provide you.
Thanks,
Rafael
The text was updated successfully, but these errors were encountered: