New answers tagged

0

You have many options but I'll dictate those options based on your given info's: Scenario: So when the user selects a filter the data that shows in the table might be invalid the next second #1. Possible Solution: If the user selected an invalid data you can use a message (notification) that indicates the data is invalid because * state a reason ...


0

Auto refresh will increase load on Database as well as application. Don't do that, unless user is really needed to see data changing each second. Periodically change the Key data, do not refresh ENTIRE set of data. Rest, either show users notification of latest data is available. And when they take any action, fetch data and display. Key is, ASK the ...


3

A lot of sites (this one included) simply notify the user that there are updates and provide a shortcut to load just the new data. This allows the user to proceed as they wish, in one of two ways: If what the user is doing is not critical, then he/she can continue working without interruption If the user is very concerned about having the most up-to-date ...


0

Talk to the users to see their patterns of working with the data and their preferences on how to get it refreshed — cyclically, on demand or else.


0

Depends. When is the data critical to the user? I would think that if he's fiddling with filters, he wants to filter the current data but just give him the option to update the data. Also give him the option to have an automatic refresh if he wishes. His choice.



Top 50 recent answers are included