Lookup columns populated in data but not displaying in collection list

Solved: In the user table I had selected row owner within my email coloumn and that was the issue. Thank you again Darren_Murphy

I’m running into an issue where lookup values from my Users table are not displaying consistently in my Orders collection, and I’m at a loss.

Setup:

  • Orders table stores CustomerID
  • Relation: Orders.CustomerID → Users.UserID
  • Lookups in Orders:
  • CustomerAddress
  • CustomerUnit
  • CustomerCity
  • State
  • CustomerZIPCode
  • CustomerName
  • Template in ‘Orders’ builds an Address Line from those lookups

Problem:

  • First order displays correctly
  • Customer Name shows
  • Address Line shows
  • All lookup values render

But for subsequent orders:

  • Customer Name does not show
  • Address Line does not show
  • Template still runs (commas appear), but lookup values are blank
  • Data does exist in the Orders table

This is happening on my Plant Dashboard collection sourced from Orders.

Important notes:

  • Relation is correct and populated
  • Lookup columns show values in the data editor
  • Template is built in Orders, not Users
  • If I pull from Users directly, it shows the signed-in user instead (so Orders context is correct)
  • This same architecture has worked in previous builds

I’ve also seen odd computed column behavior in this app:

  • Bag fee not updating initially
  • Rush fee amount not showing for a bit
    Both eventually fixed after restructuring calculations

So I’m wondering if this is:

  • lookup rendering issue
  • template evaluation issue
  • collection row context issue
  • computed column dependency issue

Any ideas why lookup values would exist in the Orders table but not render consistently in the collection?









It’s because you have Row Owners applied in your Users table.

3 Likes

This is why I love this community page. Thank you! I was going crazy trying to understand what I did wrong.