web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Supply chain | Supply Chain Management, Commerce / Entities Patch with re...
Supply chain | Supply Chain Management, Commerce
Unanswered

Entities Patch with returned data

(0) ShareShare
ReportReport
Posted on by Lizelle 140

Hi everyone, 

We have the requirement that when a patch is done on an entity, that the data is returned that was patched. 

So I found this link: https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/webapi/update-delete-entities-using-web-api

However, it is as if everything after the entity key is ignored. 

Here is my postman call: {{rootURL}}/data/ACCCustomersV3(dataAreaId='KEV',EMSCustomerId=30299)?$select=EMSCustomerId

Does anyone have any idea of what am I missing? 

I have the same question (0)
  • Martin Dráb Profile Picture
    Martin Dráb 237,880 Most Valuable Professional on at

    The link is about the CDS API, while you seem to be using OData services of D365FO. These are two different things.

    What kind data do you want to get back? You already know what you updated, don't you?

  • Lizelle Profile Picture
    Lizelle 140 on at

    That is true. I was just thinking maybe there might be some correspondence between the two in this regard.

    This is a requirement from my client's development team. They are integrating with an external website. As soon as the customer record has been updated, they refresh the screen with the latest data.

  • Martin Dráb Profile Picture
    Martin Dráb 237,880 Most Valuable Professional on at

    Then they should get the data in another request, in my opinion.

    The PATCH command patches the data and returns information about whether the update was successful; its responsibility is not to return the whole resource. Also, because returning the resource isn't needed in most cases, you would end up returning a lot of data that would be ignored.

    Patching the data and then fetching the current resources sounds like the right approach to me.

  • Lizelle Profile Picture
    Lizelle 140 on at

    The big issue they have with doing a second request is that there is a speed impact.

    Every single issue we had thus far is related to speed. When working with customers on a website, you can't make them wait for too long. This can have an impact on sales.

    However, I tested on the UAT environment and patching takes around 2 seconds and retrieving the record takes about another 1 - 2 seconds. That isn't such a bad response.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Supply chain | Supply Chain Management, Commerce

#1
Laurens vd Tang Profile Picture

Laurens vd Tang 298 Super User 2025 Season 2

#2
Siv Sagar Profile Picture

Siv Sagar 179 Super User 2025 Season 2

#3
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 121 Super User 2025 Season 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans