Hi Shital,

If it is in line with your business case, you can just update the value entered by the user in the OnChange event of the textbox. This way, the value you want is updated in DB as soon as user changes the value, so that it wouldn't get lost when going to another page. 

Another way would be not to refresh the data source when pagination changes.

So, instead of getting the records with a Start and a Limit (MaxRecords) via Aggregate/Data Action, you would get everything at once, assign them to a list record variable, and use that variable as the source of your table.

You can still apply pagination to that list, so you don't have to show the whole list at once. The values changed by the user would stay in the list record, and you would update the changes together at once when user clicks an 'Update' button in the screen.

You can check out this component on List Pagination: https://www.outsystems.com/forge/component-overview/7700/list-pagination-reactive

This second method has some disadvantages: The performance can suffer if there are a lot of records to get at once. You would also need a more intelligent way of only saving the changed values in the last step, instead of running a CreateUpdate action for each of the records, to improve performance.