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?
Data Entity - ODATA delay when selecting new records
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.
Data Entity - ODATA delay when selecting new records
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.
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.