Hi @MicLabElmo,

ODP_NOT_ALLOWED means the particular operation not allowed through OData provider.
For example: Performing a delete operation on a non-collection item.
 

Could you try adding the PartNo to path parameters since it's a required parameters,
PATCH /main/ifsapplications/projection/v1/PartsHandling.svc/PartCatalogSet(PartNo='MYPART') HTTP/1.1

Cheers !
Dhananjaya.

Hi,

I tested with the added PartNo= in the query but the error is the same at the end. There is no more information than error message {"error":{"code":"ODP_NOT_ALLOWED","message":"Illegal operation."}} when this problem occurs.

Michel

Hi @MicLabElmo,

This is a strange behavior.
However, it works fine when I tested with Postman on a "APP10 CORE UPD8" reference environment.

You could try the following to troubleshoot this,
1. Since you are consuming the endpoint from /main, you could try to update the same part from Aurena and check the network calls in the browser.
2. Try to update only the Description from your program (by only including Description on your request body).
3. Try removing the "If-Match" parameter from the header.
4. Test the endpoint using another tool like Postman.
5. View the actual http request generated by your program and cross check it with the request generated by Postman.

Cheers !
Dhananjaya.

Hi Dhananjaya,

The solution that worked is your point #3 : try removing the “If-Match” parameter from the header. After removing it, the Update operation worked correctly. Thank you for the help.

Michel

Hi @MicLabElmo,

You are welcome and I'm happy to help
However, I would suggest you to try out to set "If-Match" parameter value to "*" as well.

Cheers !
Dhananjaya.

I encountered the same error when working with Microsoft.OData.Client v7.9.1. Removing or modifying the If-Match parameter didn’t work for me. 

For the PATCH request, it seems like the API expects only the modified attributes to be sent. However, the framework was not doing the desired action which resulted in the error.  

On a quick search into the Microsoft devblogs I found a related post which helped me resolved the issue. _Tutorial & Sample] Client Property Tracking for PATCH

The solution:

DataServiceCollection<PartCatalog> parts = new DataServiceCollection<PartCatalog> 
   context.PartCatalogSet.Where(o => o.PartNo == "TESTPART"));

parts 0].Description = "test description";
DataServiceResponse rs = context.SaveChanges();