App structure suggestions

[tcpallet]

I am running into an issue where a user will edit a row and overwrite changes that another user recently made due to the changes not reaching them yet.

What is the best way to restructure my table to avoid this?  Would I need to make a separate table that creates a new row with every change and the main table consist of mostly virtual columns to pull the most recent data?

Thanks

Kyle

[Marc_Dillon]

Would I need to make a separate table that creates a new row with every change

---

Yep, that's basically it. All data changes are just additions of records, no actual edits are made (by the user).

[tcpallet]

Thanks for your input.  Would you suggest be the best formula to use to for the virtual columns?  I have been using "any(select("  , but it can be delayed once the tables get larger.

[Marc_Dillon]

I think I'd need more details about what you're doing to suggest anything there. But it is likely that there won't be a more efficient VC formula, but rather a more efficient method of updating the values. I.e. running form save Actions or Bots to enact real data changes.