Bot's task step Table

[TUI]

How I can change "Table that this task works with. This is set in the process or determined by the event." to other

[TeeSee1]

Display its process

[AndreuE]

Hi!

But until now it was not necessary, in the event I had one table and in the process another without having to do anything. Is this a recent AppSheet bug?

[TeeSee1]

I am not sure what you mean. If you want to set different tables between the event and a process, you need to change the table setting of the process because the system does not know what table you want to use in the process. The bot setting interface indeed changed some time ago, but I hardly call it a bug.

[AndreuE]

Hello, let's see if I can explain myself better. I have a bot I made a few weeks ago that has a event on a table that looks at the changes and the process sends an email with the data from another table, if I now go to the process the table in the drawing is the table of the "Report" event but instead the process table is "Delivery Note". (image 1)
If I create this now it turns out that I cannot change the process table (image 2).

image 1 (old process diferent tables). image 2 (new process same table, not change un task to get dato to send email):

image 1image 2

[AndreuE]

I have searched the internet for a screenshot of how a task was configured to send an email and how
You can see the "Table Name" can be selected without problem, now it appears in blue and cannot be changed.
I hope it clarifies the problem.Old configuration: Can change table name

[crescenttech]

I have the same exact issue. 

[crescenttech]

Direct from Google support.. it looks like it is gone for good. the workaround suggested was for me to create another bot, based on the the table I wanted to reference, and trigger off of my process from the other bot (which was when an add happened to the table) to send the embedded email. Still playing with it to see if it introducing more issues for me, but I think it will work just fine.

Quoted from google support "We earlier allowed to make these change in the bot but now we to avoid confusion and error cause due to this now we do not support putting different table view here."

[Jamie]

This can't be right! This has fundamentally broken automation / reporting functionality that I used throughout my app. @lizlynch was there any notification or documentation of this change? Creating a process does not allow you to choose a slice, only a table. And creating a bot requires that there be some action (data change or schedule) which makes no sense when it is being called by another bot. This seems like a classic case of dumbing down the platform and eliminating functionality that was extremely useful because some subset of the community could not understand how these objects work. Reduce confusion by improving documentation and support channels, not by stripping away important features that more advanced users depend on. Super disappointing and clueless move by Google, if true and not just another bug.

[lizlynch]

Apologies for not getting back to you sooner, and for not calling this out in the release notes. It should have been called out... It was my mistake for missing the rollout of this update. 

Confirmed with the team that the reason for removing the table selector from Tasks is because it wasn't working properly and caused confusion. You can still achieve the same functionality of referring to a table that is different from the Event by using the Call a process step. I've updated the documentation to note this in the task descriptions.

Again, apologies for any inconvenience.