Automation Using New Record

Hi

I have created an automation to update a column when a record is created using lookup

LOOKUP([_THISROW].[Employee Email], “User List”, “EMail Address”, “Employee No”)

However at the time this runs the Employee Mail column shows as “_PII_” as it is created using an Initial Value of UserEmail() .. is there a way to get the bot run after the new record is fully created and the Employee Mail column is populated ?

FIRST, “_PII_” stands for “Personally Identifiable Information” and is a value that is shown ONLY in log entries or data table views. It is not the actual value in the column. It’s just a way to hide the actual value should anyone gain access to displayed analytical information. Having the value of “_PII_” shown indicates that there IS a valid email address assigned to that row.

**************

As I understand it, you want some row in another table to be updated with the [Employee No] but only AFTER the [Employee Email] value has been populated in the User List. Is that correct?

Something is odd here. It seems the User List table should have been populated well before inserting that OTHER row and, if so, you would have been able to populate the [Employee No] using an Initial Value. In other words, you shouldn’t need to do the LOOKUP() in a Bot at all and be able to silently set the [Employee No] at the time that OTHER row is created.

Can you describe your process more? Was there some other issue that lead you to the LOOKUP() solution in a Bot?

2 Likes

I initially tried it in the initial value of the field but it still did not populate .. basically i want to extract the employee id from another table whenever a new record is created .. the other table contains the user email address which should match useremail()

1 Like

Ignore me .. the account i was testing with did not have a valid lookup in the other table :frowning:

2 Likes

Hi @Robert_Taylor

try changing “Email Address" to “Employee Email”

LOOKUP([_THISROW].[Employee Email], “User List”, “Employee Email”, “Employee No”)