When using an auto-generated ID column (such as the Row ID column of an AppSheet Database) as the primary key, it appears that this key cannot be used to look up a row in an AppSheet Bot’s “Call a process” step.
In the Call a process node, the column selection dropdown only lists editable columns. As a result, the auto-generated ID column (which is read-only) cannot be selected.
This is a problem because when “Lookup” is chosen as the call type, the primary key column is essential for referencing a specific row.
Is this expected behavior or a bug in AppSheet?
And is there any known workaround to use the auto-generated primary key for lookups inside a bot process?
Thank you for your kind response!
Unfortunately, I wasn’t referring to the LOOKUP() function.
I mean the “Lookup” option in the “Call a process” step of an AppSheet Bots (formerly automation).
Thanks again — I really appreciate your help, and I’m looking forward to your further advice!
The phenomenon described in this post has been observed in my environment for some time.
Apologies for butting in, but I’ve conducted a simple test regarding this issue and would like to explain the results.
・There is only one table. (The data source is a spreadsheet.)
The Key’s Editable property is ON.
Since ‘Call a process’ merely ‘searches’ for the target row using the key column, I cannot see why the Key must be editable.
Personally, I consider this to be a kind of bug.
