Bot that is triggered through another bot, can't get USEREMAIL()

AppSheet AppSheet Q&A
1

Hi all

I stumbled upon the following problem:
When I have a bot that gets triggered after another bot made changes to a table, the second bot that is triggered doesn’t get a USEREMAIL(). The field just stays empty.

Also, the NOW() formula, in a bot triggered by a bot, sets a wrong time (-1 hour to my timezone).

Is this a known problem, or am I doing something wrong?

Thanks in advance.
Adrian

2

Hi @Adrian_Enz

Adrian_Enz:

When I have a bot that gets triggered after another bot made changes to a table, the second bot that is triggered doesn’t get a USEREMAIL(). The field just stays empty.

Bots can’t use USEREMAIL(), as there are running remotely and the USEREMAIL() use the “logged in” property.
One workaround could be to update a value somewhere, and make the bot to use this value in its process.

Adrian_Enz:

Also, the NOW() formula, in a bot triggered by a bot, sets a wrong time (-1 hour to my timezone).

This makes me think about a setting to change.
Here are more informations about this:

[Spreadsheet formatting tips](https://community.appsheet.com/t/spreadsheet-formatting-tips/58931) Tips & Tricks ?

The format of a cell in a spreadsheet used as a data source for an app can affect how AppSheet uses the cell’s content. It is therefore important to take care to choose cell formatting carefully. Automatic format is okay for most data, but can cause problems in some circumstances. The safest cell format you can use for everything is plain text. The downside to formatting the spreadsheet as plain text is the spreadsheet becomes less legible to its human users. Here are my suggestions: Forma…

[Device Independent TimeCapture](https://community.appsheet.com/t/device-independent-timecapture/21448/6) Tips & Tricks ?

Hello @Suvrutt_Gurjar , AFAIK, UTCNOW() value is coming from the AppSheet server directly, not calculated from the device. But I will investigate this a bit further both from the emulator and my device. It’s quite simple to test I assume.

You may want to use NOW()+"001:00:00" instead ?

4 Likes
3

Thank you @Aurelien, both solutions are working just fine. You helped a lot.

3 Likes