Issue with Lookup Single Row Action in Same Table Functionality

Hi team, Somehow I can't use the "Lookup Single Row in other Table" action to look up a value in the same table, even though in this tutorial at 2:06 it works. But for some reason, it’s not working on my end. Is this a bug, or has this feature changed? Is it no longer possible to use this action to look up values in the same table? Context: I want to count how many jobs in one column were posted by the same person (using the Recruiter Name as an identifier), all within this same table. Thank you for your support

10 comments

Jannis E.
·
·
https://app.clay.com/workspaces/479052/workbooks/wb_CijkxvVXmARQ/tables/t_vhyUMr4CG4SG/views/gv_utbqfe86QwGD
Bo (.
·
·
Hey Koichi, You can definitely use the “Lookup” action within the same table—it’s often the better fit for what you’re trying to do. However, I'd recommend to use the " Multiple Rows in Other Table" not the "single rows" It looks like the issue might be with the table name you’re referencing. The correct name is “Find Jobs Table, 2nd April, 2025”—not the workbook name. Double-check that you’re pointing to the table itself in the setup. Let me know if you want help configuring the logic!
Jannis E.
·
·
Thank you for getting back to me Bo (. and good call - indeed I was referencing the workbook name instead of the table name. I now followed this tutorial but somehow the formula does not give me the number in which array position the uniqueID was found. Can you help?
Here is the tutorial
Here is my table
Attached you can also find a screenshot of the wrong result
Jannis E.
·
·
I believe the formula only works in the video because there are only two duplicates present, and the number shown in the second row is actually the fallback value, not the row value. I replicated the steps exactly as shown in the video and tested it in a table with six duplicates. However, the formula continues to return “2” as the result. When I replace the “2” with “error” as the fallback, I consistently see “error” instead of the expected index. Could you please take a look and check what’s going wrong?
Jannis E.
·
·
Also this fix provided by Anaum K. does not seem to be the right fix for my issue
Jannis E.
·
·
Jannis E.
·
·
(Short 1:30 Video to elaborate the issue and what I'm trying to achieve)
Bo (.
·
·
Hey, The issue was due to the rows not being fully run and the formula needing an update. I’ve fixed it for you—everything should now work as expected. Here’s the updated formula I used: LBKS{{Unique ID}} ? ( {{Lookup Multiple Rows in Other Table}}?.records?.findIndex( r => r['Unique ID']?.toString() === {{Unique ID}}?.toString() ) > -1 ? {{Lookup Multiple Rows in Other Table}}?.records?.findIndex( r => r['Unique ID']?.toString() === {{Unique ID}}?.toString() ) + 1 : 2 ) : 2LBKSLet me know if you want to adjust the fallback or tweak the logic further!
Jannis E.
·
·
Awesome, thanks a lot Bo! 🤩
Channeled
APP
·
·