I have an app where:
Is this delay in place on purpose? Since the timing is so consistent, it seems to be built in.
Currently,I am using Excel DropBox, the changes for user in Device A can be Refreshed and viewed almost instantly in Device B.
(Either Android - Android, Android - iOS, Android - Win 10, vice verse).
Guess maybe CDS problem?
(I have not been using CDS for couple of weeks)
Just wonder of the difference...
I ran a test where
The result is that changes to the affected record are not detected from one browser to the other until 34s have elapsed (changes within one browser are detected in that browser).
To put this into perspective of why this is a huge problem:
If one user updates data and another user attempts to update the same one within 30s, then they will not have detected the previous changes.
In additional testing, the change may not be detected for minutes. So Refresh() is not always working correctly. The surefire way of detecting new changes is to reopen the app or reload the webpage.
Essentially, only one user can be on the app at any given time. There is no point to multiple instances or users because they can't receive the most up-to-date data.
Is the delay by design or is it on schedule to be eliminated?
I don't know what you had changed, but it seems the 30s delay is less significant.
I had stored a variable online into a CDS entity. When the variable was false, then users could post messages. When I turned the variable on, it activated moderation mode, so user messages would need to be confirmed before they were visible.
It was only possible for this variable to work if changes to the entity were immediately recognized between different computers. There has clearly been an improvement in CDS. It is nice to discover these things, but I feel the PA team could get more credit if these improvements were fully communicated.