InView Version 3.5.3 introduced a new control at the top of data table screens that changes the way data is refreshed and enables you to

a) Choose how many row or incidents (100 in this example) of data to fetch each time the table is refreshed.

b) Select the next 100 rows.

c) Select the previous 100 rows.

d) Jump to the first 100 rows.

e) Jump to the last 100 rows.

Inview only refreshes data grids when the a different set of records is requested, the refresh button is clicked or automatically 15 minutes after the previous refresh.

This gives the you control over how much data you are requesting from InView each time the screen is refreshed allowing you to take control of the balance between system speed (primarily your internet connection speed) and completeness of the dataset that is fetched from the server. If you choose a value that is greater than the number of incidents available InView will return all available data.

The default number of rows of data to return is 250, you can change this for each screen independently and save your preference by right clicking the header of the table and choosing 'save layout'. The maximum number is 9999 and depending on your internet connection speed this may take several minutes to refresh and is not therefore recommended.

The first incident to be fetched (row 1) is always the most recently modified item, the default sort setting of the table is also by the last modified data field and so this data would also appear in row 1 of the table. However you can change the way the data that has been fetched is displayed by sorting on a different column, you can also save this as your default using the 'save layout' function. This means that the most recently modified item may not be at the top of the table, but it will always be in the first set of records retrieved.

Increasing the number of rows to fetch may move the incident up or down the table as it is refreshed depending on your sort preferences. It also means that if for example you are viewing 20 rows of data at a time and you are currently looking at rows 41 to 60 after modifying an incident and the grid is refreshed it would result in the incident moving to row 1 and effectively disappearing, you can use the jump to first row button to quickly find the incident in the data.

Column filters are applied to the data locally, this means that fewer rows of data may be displayed than you have requested, removing the filters will display all the rows that you have previously requested, without getting the data again.

And finally remember that incidents may be updated by InView (for example an engineer arrives on site) or other users which means that things that you did not change may also move.