LinkedIn
Twitter
2 ACCEPTED SOLUTIONS
Then you save it with 'No Table' selected. Then if you want a table name other than 'No Table' in that email process you can repeat your steps again and select a different table name and save. However, a scheduled bot will always fall under the 'Other' category vs under a 'Table' name for Bots, unless you check 'ForEachRow'.
Now subsequent steps in the process under a bot configured on a schedule might provide the illusion that a Table Name can be configured, however as your original error showed, this process fails when trying to use a specific column value in your template like <<[Column Name]>>. So as I was explaining you can use a formula such as <<SUM()>> or <<ANY()>> in your template or furthermore you can also use <<Start: >><<End>>.
I have deleted the old bot and created a new one. Unchecked "ForEachRowInTable" The new bot is functioning without requiring the column name to be filled in the email body. However, when I do enter the column name in the email body, an error seems to occur.
Just for your information, no expressions have been used in the slice table, and I haven't employed any expressions in the bot condition. I've created three virtual columns, all of which are of number type. I aim to receive the daily value in one of the columns through email.
These expressions have been utilized in all three virtual columns.
Master table name:- Scan Sheet
1. SUM(
SELECT(
Email Report Process[QUANTITY],
ISBLANK([PUTAWAY NO])
)
)
2. SUM(
SELECT(
Email Report Process[QUANTITY],
AND(
DATE([PUTAWAY UPDATE TIME]) = TODAY(),
ISNOTBLANK([PUTAWAY UPDATE TIME])
)
)
)
3. SUM(
SELECT(
PHOTOS[PAIR QTY],
AND(
DATE([DATE]) = TODAY(),
ISNOTBLANK([DATE])
)
)
)
So, this is OK:
But using a <<[Column]>> in the context of an email template does not function, unless it is contained within a ANY/SUM function or within a <<Start:>><<End>> context. Unfortunately that is a limitation of the platform. So within your scheduled event under the email step it is taking all rows of that table and that is why <<[Column]>> in the template breaks because it is not available within the context of the event.
