Lookup() formula works but that still requires you to know the ID of the row. The question I had was in reference to @nigel’s statement that you can use the @reference to pinpoint the row and then retrieve another column from that specific row. Looks like both you and @evan found the solution which is using the equals sign before doing the @reference
@chris_homburger How does your workaround work with the control item? Could you post a screenshot with formula?
The concept of using the @reference to pinpoint a row and then pulling in the column reference could be an anti-pattern compared to a
VLOOKUP() in Excel. When you have a long list of IDs/unique names and you need to pull in data for a summary table, you would type the handful of IDs/names in the summary table and then run
VLOOKUP() to find associated data. With the Coda @reference used in the canvas, it feels like the user needs to be trained to disregard the ID and think about the unique value (in my case, thinking about “More Text”) as the lookup value. This means the first column–or whatever the “display” column is–should be truly unique be it a list of your friends’ names, team names in your company, etc. Then the user should be conditioned to reference the unique name in the formula vs. the row ID.