One log for all app changes?

[Test_Test]

Hi all,
So, I’m coming back to my old post, which has been solved by @Darren_Murphy.

@Test_Test

here’s a quick recap of the columns that are used to construct the HTML table.

It is actually also connected to this great post:

@Gregory

can give something back today:

https://change-log-v2.glideapp.io/

Both posts are somewhat limited in the sense that they’re “tracking” a single table/sheet. They are rather custom-made which makes them look great, but also makes it very unpleasant to expand them to track more tables/sheets.
In many cases, we don’t need such elaborate logs, or even elaborate update screen to support these changes. We can use the native EDIT option by Glide. Is there any way to log changes made by this native edit? Something like “Cell History” in Google Sheets.

Any other ideas for one unified change log are more than welcomed.

Thanks!

[David_Gabler]

Hi, in one app I am allowing data add/mods/dels by users (of certain tables), and I needed to track those. My solution was to simply write to a “history” table which contains the user id, the table name, the action (add/mod/del) and the data. For the data, I construct a template column which appends all the columns together and write that as a delimited string.

The only maintenance headache I have is when I add a column (or remove a column – more rare), I have to update the template for that table. I’d love to have a “Joined List” column type that joins the values for every COLUMN rather than for one column in every ROW.

This history allows me to roll back changes when necessary (even of row deletes).

Then my method would be a piece of cake as far as app maintenance is concerned.

[Test_Test]

@David_Gabler

history” table which contains the user id, the table name, the action (add/mod/del) and the data.

Thanks.
Are you using the native “Edit” or a custom form?
If native, how do you track it and/or control where it writes to once done editing?

[David_Gabler]

I use a custom action on add or edit which writes to the log and then does the save record.

For my delete, I like to provide a delete confirmation, so I have three buttons. When they click ‘delete’, it makes the “confirm delete” and “cancel delete” buttons visible. When they click the ‘actual’ delete, I log the row and then perform the remove row. I also set a column in the user’s record as to the last action they did and the timestamp.