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

Notifications

Announcements

Sign Up for Ask a Community Pro Today!
Introducing our New Video Series: Community Spotlight
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Data Entity - ODATA de...
Finance | Project Operations, Human Resources, ...
Unanswered

Data Entity - ODATA delay when selecting new records

(1) ShareShare
ReportReport
Posted on by Basti Aurand 252
Hello,
 
we face the problem that a record, which is newly created in a table (through the normal user interface) is not immediately available via the corresponding data entity in an ODATA GET. Sometimes the delay is up to 1 minute before the record /arrives/ at the ODATA GET.
 
e.g.: the user creates a new customer = open the /Create customer/ dialog -> enter the information including a new address -> hit save -> the new customer and the corresponding logistics postal address is displayed in the UI
 
The new record for the LogisticsPostalAddress, which is created in the background, arrives up to a minute later in the entity = /LogisticsPostalAddressHistoricalCDSV2Entity/ - ODATA: /CDSPostalAddressHistoryV2/.
 
Does anybody have similar issues? Why is there a delay and how could I control / influence the delay in the ODATA calls?
 
Thanks in advance for any help.
 
Sebastian
I have the same question (0)
  • André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 302,403 Super User 2025 Season 2 on at
    Hi Sebastian,

    What application are you using where you use the OData GET calls? When I'm using the Excel add-in which is also based on OData, the information is directly available once I created a new customer in the application.
  • Basti Aurand Profile Picture
    Basti Aurand 252 on at
    Hi Andre,
     
    it's a third party interface which does the ODATA get calls. On the "dynamics-side" we implemented a method in the "Inserted Eventhandler" on the table (e.g. LogisticsPostalAddress) in order to inform the interface that a new record is available. Straight after receiving this "call" the interface tries to get the record via ODATA.
     
    I will really appreciate any hint.
  • Basti Aurand Profile Picture
    Basti Aurand 252 on at
    Any other hints on this?

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

News and Announcements

Sign Up for Ask a Community Pro Today!
Introducing our New Video Series: Community Spotlight

Quick Links

Responsible AI policies

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

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Congratulations to the December Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
André Arnaud de Calavon Profile Picture

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

#2
Abhilash Warrier Profile Picture

Abhilash Warrier 438 Super User 2025 Season 2

#3
Martin Dráb Profile Picture

Martin Dráb 348 Most Valuable Professional

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans