I am using the table and have been appending data to it. Is there a way to allow it to accumulate a specific number of rows and then replace older rows in a FIFO manner?
I can imagine implementing this by storing the data outside of the table and sending each update as a Replace instead of an Append action. My only problem with this approach is that if I want the limit to be something like a thousand rows and I have 10-15 updates per minute, that is a lot of traffic. Additionally, I am not sure what the user experience is if the user is on page 4 and the data gets replaced.
I am thinking that perhaps the solution is to just keep the data in my flow and have a user action trigger populating the data with a snapshot at the moment of trigger.
I do recognize that the Max Rows that superficially looks like this might address my requirement only speaks to the pagination and not the actual max rows to be stored.
