Hi All,
I’m working on an ad-hoc feature that subscribes to the DOM for real-time updates. I'm performing some necessary sorting based on date and time values within the ad-hoc, so when the GetNextPage method executes, all the rows are sorted as expected.
The issue arises when a user creates an instance or updates the time of an instance. If I update the time of the instance, my table is no longer fully sorted since the _updater only updates the modified row, leaving the sorting partially incorrect.
Below is a screenshot showing the table sorted as expected.
Here is the updated value, but since the _updater
only updates a single row, the entire table doesn’t get re-sorted.
Is there a way to accomplish this within the ad-hoc so that when a DOM instance is updated (single row), the entire table refreshes to maintain proper sorting?
Thank you!
Hi Carlos,
The table refresh behavior can be achieved by adding any operator that does not support real-time updates, such as the sort operator.
When your ad hoc data source then updates a row, instead of sending a row update to the client, GQI will send a notification indicating that the data has changed (in real-time but rate-limited at 1 per 30s). This will cause the client to refetch the data for the table in a sorted order.