I hade a quick play around with the universal app.
Have a table in the universal app with an Automation to lock the table if a single select was changed.
If I change the single select in the Universal app, the lock is locked as expected and being in the base (not in the Universal app) I indeed can’t edit anything.
In the universal app however, I can still edit data and the data is saved. Only after a refresh, the editing is not permitted or if the universal app loads the data with an already locked state.
I can work around this for this task, but don’t recall if it was mentioned during SeaDays. Looking forward to test the next version.
ok thanks.
Still thinking of the best workaround. Having the locking done in background through n8n after an export is a solution but if users keep the app open until the next day without reload they might still be able to update.
Any better ideas on how to work around this issue?
e.g. {Column A} contains the text and {Column B} is a formula which only displays Column A. So it is the same text, but you can not edit it in Column B, only in Column A
In your case, I would work with two pages containing the same table. Both tables have a single select and contain the same date. The first table only shows the single select is “in progress” using a filter and is editable. The second table only shows the single select “finished” using a filter and is write protected.
Do it like thousands of other people who have used SeaTable to develop powerful processes and get their ideas and tasks done more efficiently.