One row in one table is added or updated, columns in another table can be updated please?

[Syd_Stewart]

Is there a simple example app or video where when one row in one table is added or updated, columns in another table can be updated please?

[1minManager]

You can have an " Execute an action on a set of rows" action as the "Event Actions: Actions to take when events occur [Form Saved]" on the form UX in question. This may help:

help.appsheet.com

Actions: The Essentials

Learn how to use actions to modify data and navigation in your app.

[bonameblisto]

or

help.appsheet.com

AUTOMATION | AppSheet Help Center

This collection organizes all automation related articles.

[1minManager]

Dont do it that way - doesn’t seem to work right. You need to do it as an action

Bot set to trigger ON data change seems to run BEFORE data change Questions

So I have an App formula in a table that does a SUM of some items in a different table. Nothing complicated. When I click edit on row in that table the SUM() works fine. Yet I want this to update everytime you make a change in a totally different table. Again, not a drama, done it loads of times. I’ve got a bot where the trigger is a change in one column which then calls an action to look at multiple rows and writes a timestamp in a column of the where the SUM() formula is. The reasoning b…

[bonameblisto]

You are partly right, but the question is not formulated unambiguously. In some cases it is possible to use Actions, in some it is not.
In my industrial application, such logic is used to keep a log of operations (all changes in data are recorded in the “log” table transparently for users)

[1minManager]

bonameblisto:

In my industrial application, such logic is used to keep a log of operations (all changes in data are recorded in the “log” table transparently for users)

I suspose the difference is yours appears to work asynchronously. Whereas mine had to save the data then run this Bot. Doing it as a Bot meant the bot seemed to run before the data was save. Despite the fact that the saving of data was the trigger for the bot