Odata - Update failed when trying to update entity via Postman (404 resource not found)

(1) Share

Report

Posted on by Christine B

Hi,

We are working with a custom built entity called CC_PartsTraderTransaction which contains invoice lines in D365. I want to update one field in this entity known as PTInvoice using the PATCH verb. An example of a Get call for this CC_PartsTraderTransaction entity returns:

The defined key for this entity is:

When I perform a PATCH to update the PTInvoice value to be Yes for a specific item I get a 404 resource not found and yet I know that this invoice exists. Why could this be the case ? What is wrong with the URL construct I am using ?

Secondly, is there a way to update multiple invoices in the same ODATA API call, ie. the URL does not contain the params of the row to update but the request body contains an array of invoice lines with the required key entity data specified for each row to update.

I have the same question (0)

All responses (8)

Answers (2)

Verified answer

Layan Jwei 8,118 Super User 2025 Season 2 on at

Like (0)

Report

Hi,

I think it's because the body format is wrong. Try to put the body like this:

{

"PTInvoice": "Yes"

}

For example, if i want to update the customer currency, here's what i would do with PATCH:
url/data/CustomersV3(CustomerAccount='xx',dataAreaId='yy')

and the body will be like this:
{

"SalesCurrencyCode": "USD"

}

Thanks,
Layan Jweihan

Please mark this answer as "Verified" if it solved your issue. In order to help others who will face a similar issue in the future.

Was this reply helpful? Yes No
Christine B 14 on at

Like (0)

Report

Hi Layan,

Thanks for your suggestion. I tried just posting the PTInvoice in the request body, with the PATCH to the URL https://xxxxxxxxxxx.dynamics.com/data/CC_PartsTraderTransaction(dataAreaId='sk',Voucher='APIMP000032562',InvoiceNumber='66504331',InvoiceDate='2019-07-27T12:00:00Z')?cross-company=true

However, I still get the http 404 response.

Was this reply helpful? Yes No
Suggested answer

Leah Ju Microsoft Employee on at

Like (0)

Report

Hi，

You should provide GUID of the record in your patch request:

You can refer to this blog for detailed steps:

https://arunpotti.com/2022/10/31/how-to-update-the-table-row-values-in-a-dataverse-environment-from-postman/

Was this reply helpful? Yes No
Suggested answer

Anthony Blake 2,963 Super User 2025 Season 2 on at

Like (1)

Report

Hi,

Take a look at the customer PATCH example here in case it helps, its a working example from a standard table:

https://www.postman.com/anthonyblakedev/workspace/dynamics-365-finance-apis/request/22139284-8cd167d7-6e12-463a-9550-464bbdb33086?active-environment=a6fe8359-b53f-49db-bd87-616db2899d1a

To answer your second point, you can send multiple OData requests at once, but not as a simple array. The method is using OData $batch, which involves sending an array of requests rather than an array of records.

It is briefly documented here: https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/odata#batch-requests

Was this reply helpful? Yes No
Verified answer

Layan Jwei 8,118 Super User 2025 Season 2 on at

Like (2)

Report

Hi CB,

After you changed the body format, I think you also need to remove the single quotation for the InvoiceDate in the URL:
https://xxxxxxxxxxx.dynamics.com/data/CC_PartsTraderTransaction(dataAreaId='sk',Voucher='APIMP000032562',InvoiceNumber='66504331',InvoiceDate=2019-07-27T12:00:00Z)?cross-company=true

give it a try and let us know

Thanks,
Layan Jweihan

Please mark this answer as "Verified" if it solved your issue. In order to help others who will face a similar issue in the future.

Was this reply helpful? Yes No
Christine B 14 on at

Like (1)

Report

Hey Layan, fantastic that worked. Removing the single quotation from the URL and just having the attribute to update in the request body. Thank you.

Was this reply helpful? Yes No
Layan Jwei 8,118 Super User 2025 Season 2 on at

Like (0)

Report

Hi,

I'm glad your issue is fixed :)

Please don't forget to verify the answers that solved your issue.

Was this reply helpful? Yes No
Christine B 14 on at

Like (1)

Report

Hey layan, I'm trying to verify your answer but I get a 403. I'm afraid I can't verify it. Will keep trying though.

Was this reply helpful? Yes No