Bot deleting the wrong table?

[luizluca]

Hello,

I have a simple bot process:

Trigger:

when row is created in table A

Process:

1. Run data action: run action on rows

Table: Table B

Reference Rows: (a selection of rows)

Referenced Action: do something

2. Run data action: delete row

I expected that action 2) should delete the row from table A. However it is trying to delete a row in table B! I was luck that table B is readonly.

I workaround it by changing 2) to:

2. Run data action: run action on rows

Table: Table A (same one that triggered the bot)

Reference Rows: [ID]

Referenced Action: delete

Does anyone experienced such problem before?

[Jose_Arteaga]

Hello @luizluca,

Thanks for reaching out! I found this YouTube tutorial video that I believe it explains what you need.

Please let me know if this works!

[WillowMobileSys]

@luizluca

Table: Table B

Reference Rows: (a selection of rows)

Referenced Action: do something

2. Run data action: delete row

The Reference TAble setting indicates which Table the action is retrieved from as well as the which table the Reference Rows is exected to be from.

You CAN have the same Table as the source table AND the Referenced table.

If your source Table is A and you wish to delete other rows for Table A, then your Referenced Table should ALSO be Table A, the Reference Rows should select rows from the Table A and the list of possible actions wil be from the Table A list.

I hope this helps!

[luizluca]

Sorry but I guess I was misunderstood. The issues is that the “Run data action: delete row” was reusing the table cited in the previous Data action and not the one related to the current process. It looks like the “Run data action: run action on rows” replaced what table the process is about.

[WillowMobileSys]

@luizluca

The issues is that the “Run data action: delete row” was reusing the table cited in the previous Data action

This doesn’t make sense. Can you show an image of the action(s) that are giving you problems?

[luizluca]

@WillowMobileSys

This doesn’t make sense. Can you show an image of the action(s) that are giving you problems?

Yes, that’s expected for a bug

This is the trigger:

This is the first action over the second table (which is readonly):

This action tries to delete Iterações (Table B) instead of the expected Transações (Table A), generating an error while modifying a Readonly table:

This is the monitor error. Notice that the “Delete Row” was performed over Iterações and not Transações (yes, it does not make sense):

And this is my workaround replacing the previous scheenshot action, doing exactly the same thing but indirectly:

[WillowMobileSys]

@luizluca

Yes, that’s expected for a bug

I see. And I agree this is a bug. It appears the row context of the Bot has switched and that should not happen.

However, I wonder if there are some adjustments that can avoid the issue.

In the second step, I can’t see the full expression with the COUNT(). Does it use the Bot main row at all? If not, maybe it can be moved as the last step? An alternative would be to create an action normally and then reference the action fro the Bot step instead of using an “inline action”.

It seems your third step’s intent is only to Delete the row the Bot was triggered on - the Bot main row. If so, you have the wrong action selected. You DO NOT want the “Run Action on Rows”action. You simply need to select the Delete action directly. See image

I hope this help!

[luizluca]

@WillowMobileSys

I see. And I agree this is a bug. It appears the row context of the Bot has switched and that should not happen.

However, I wonder if there are some adjustments that can avoid the issue.

In the second step, I can’t see the full expression with the COUNT(). Does it use the Bot main row at all? If not, maybe it can be moved as the last step?

It does. This is the full expression:

FILTER(“Iterações”,[i]<=COUNT([_THISROW].[Lista]))

@WillowMobileSys

An alternative would be to create an action normally and then reference the action fro the Bot step instead of using an “inline action”.

It seems your third step’s intent is only to Delete the row the Bot was triggered on - the Bot main row. If so, you have the wrong action selected. You DO NOT want the “Run Action on Rows”action. You simply need to select the Delete action directly. See image

I hope this help!

Both the custom data action and the one you suggested failed the same way (see bellow):

There are just two steps. The third step you mentioned is not a new step but an alternative to the second one as it can workaround the bug (although it is ugly). I already have a workaround. I’m just trying to get the issue (and the workaround) published and the bug fixed.

[WillowMobileSys]

@luizluca

There are just two steps. The third step you mentioned is not a new step but an alternative to the second one as it can workaround the bug (although it is ugly). I already have a workaround. I’m just trying to get the issue (and the workaround) published and the bug fixed.

Ah ok! Just to paraphrase…Once the Bot performed the activity in the First step, originally it attempted to do a straight Delete of the row that triggered the Bot. That’s when the error occurred that it could not delete a row in the “Iterações” table because it is readonly. You were able to workaround it by adding a “Run actions on rows” type step.

Agreed it’s a bug that needs fixed…sooner rather than later!!

@Jose_Arteaga The suggested tutorial video you supplied above covers a different scenario. This problem does indeed need to be forwarded to developers at it seems they have a problem with “context” of the Bot switching with “Run actions on rows” type steps. Even if that is by design, at the very least the context should switch back to its original state once that step has completed.