Tasks don't populate if you select a table and then change it

If you make a bot and set the event for ie AppSheetReference_INVOICE_SPLITTING, cause the table list is unsorted and your eyes hurt from looking at it, and then change it to the correct table then the task list doesn’t seem to want to ever update to use that new tables tasks list so the bot is basically bricked and must be deleted.

1 Like

Escalated.

Attn @prithpal @Dan_Bahir

1 Like

What’s happening is the Event and the Process are two distinct entities. Each one is associated with a table. Changing the table associated with the Event does not change the table associated with the Process (since the process might be used elsewhere). In fact, if you saved after changing the Event’s table you would get an error that the event is not compatible with the process.

Tasks are associated with a table as well. You can see this by editing the task in the “Tasks” tab. We suppress it in the side-panel in an attempt to reduce what is (usually) redundant information.

What you’re attempted to do is change the table for all the Bot’s nested entities. Currently (after changing the event table), you would need to update the table associated with the process (on the Processes tab) as well as any Task / Action used by said process in their respective tabs. This would run into issues if any of the entities are used in a context that requires their current table.

As you can see, the editor is not well suited for this operation. I’m not sure if there’s an easy fix but it’s something I’ll think about. Some good news is that a fix is in for the sorting issue (pending deployment). Hopefully that will help us avoid this situation entirely. You can also type the name of the table when the dropdown is open and it should select it.

Oh it is so much more beautiful, I guess deployment has occurred. I would still like to see some method of an easier fix to selecting the wrong table eventually but this sorting does at least make my day.
image

2 Likes

Restore workflows and reports.

4 Likes

We will explore some UX optimizations @Moura FYI. Lets focus on the direction forward.