Hi,
I have an issue about triggering a bot by the action of another bot.
My first Bot deletes some records and my second Bot is set to "Delete" actions for triggering.
Although Deletions are realized the second Bot is not being triggered,
Here are the SS showing the configuration of both Bots
Bot which is Deleting records
Bot which is listenening "Deletion"
Solved! Go to Solution.
My scenario is a little bit different.
I have three tables:
Table A has a data change and Bot 1 is triggered with this data change and Deletes some records in Table B.
Bot 2 is set to be triggered by the Deletions in Table B and updates a value in Table C
Bot 1 's configuration is ("trigger other bots" enabled)
Even though there could be more details required about your bot, you could try a "Soft delete" in the first bot , meaning set a [Delete_Record] column to Y in the first bot. Then the second bot could be run that listens to the first bot. Then there could be another third bot that actually deletes the records that were set to Y in the first bot.
Even though the following post is not about bots delete and deletes through actions, you would find it relevant to your scenario. And hence the suggestion for a soft delete first.
Grouped Action: Delete and Navigate - Google Cloud Community
The problem is not deleting the records. I want to update "Stock" field in another table based on deleted records, " inventory". My first bot deletes the records successfully but the second bot which is set to listening "Deletions" it is not activated. However, when I delete the records manually, the second bot is triggered and updates the stocks successfully.
Hi @kutluhang , maybe is this your case?
https://www.googlecloudcommunity.com/gc/AppSheet-Q-A/New-feature-Trigger-other-bots/m-p/348995
This is the Appsheet announcement that I read which made me try this option. If it doesn't help my case what is the use of this feature?
I reproduced the following scenario: Bot 1 is triggered by a data update in a record from Table A and deletes that same record ("trigger other bots" enabled). Bot 2 is triggered by the deletion of a record in Table A and updates a record in Table B. It worked perfectly. If you'd like, feel free to share all Bots configurations (events and steps).
My scenario is a little bit different.
I have three tables:
Table A has a data change and Bot 1 is triggered with this data change and Deletes some records in Table B.
Bot 2 is set to be triggered by the Deletions in Table B and updates a value in Table C
Bot 1 's configuration is ("trigger other bots" enabled)
Quite strange,
I didn't change anything from the last time that I test and fail. It is working now.
Does it require sometime to get this feature become active?
("trigger other bots" enabled)
Interesting... In my case, It worked immediately. Good to know that now it is working for you.
User | Count |
---|---|
16 | |
7 | |
5 | |
5 | |
3 |