Hi Expert
I just kind of don't know how to get around it. If there are 3 tables and they're sequentially reference to each other means 1st table reference to 2nd table and 2nd table reference to 3rd table, can the action in 3rd table (action from 2nd table) fired off when the 1st table is submitted?
First table (Arrow is Key)
2nd Table (Arroe Is Key)
3rd Table (Arrow Is Key). The actions are below
Solved! Go to Solution.
Yes, it is possible to set up actions in AppSheet so that an action in the 3rd table is triggered when a record is submitted in the 1st table. To do this, you need to create a sequence of actions that propagate through each table. First, ensure that the 1st table references the 2nd table, and the 2nd table references the 3rd table correctly.
Next, create actions for each table. In the 1st table, create an action that triggers upon form submission. This action should then trigger an action in the 2nd table. In the 2nd table, create an action that gets triggered by the action from the 1st table and then triggers an action in the 3rd table. Finally, create the desired action in the 3rd table that you want to perform.
To link these actions together, create grouped actions. In the 1st table, create a grouped action that includes the action for the 1st table and the action for the 2nd table. Similarly, in the 2nd table, create a grouped action that includes the action for the 2nd table and the action for the 3rd table. When a record is submitted in the 1st table, the grouped action will trigger, executing the actions in the 2nd table, which in turn will trigger the actions in the 3rd table. This setup ensures that the desired action in the 3rd table is automatically triggered by the submission of a record in the 1st table.
Yes, it is possible to set up actions in AppSheet so that an action in the 3rd table is triggered when a record is submitted in the 1st table. To do this, you need to create a sequence of actions that propagate through each table. First, ensure that the 1st table references the 2nd table, and the 2nd table references the 3rd table correctly.
Next, create actions for each table. In the 1st table, create an action that triggers upon form submission. This action should then trigger an action in the 2nd table. In the 2nd table, create an action that gets triggered by the action from the 1st table and then triggers an action in the 3rd table. Finally, create the desired action in the 3rd table that you want to perform.
To link these actions together, create grouped actions. In the 1st table, create a grouped action that includes the action for the 1st table and the action for the 2nd table. Similarly, in the 2nd table, create a grouped action that includes the action for the 2nd table and the action for the 3rd table. When a record is submitted in the 1st table, the grouped action will trigger, executing the actions in the 2nd table, which in turn will trigger the actions in the 3rd table. This setup ensures that the desired action in the 3rd table is automatically triggered by the submission of a record in the 1st table.
Not that easy. I will try again in another way
Not an easy way to do it and dereference is complicated. I found any smart way to get around this. So I consider this is solved.
User | Count |
---|---|
34 | |
8 | |
2 | |
2 | |
2 |