True Relation column not set

If you are still seeing QUERY in the cell after following every step to add a “Relation” column, it means Glide is treating that column as a Query-type column, not a true Relation column. This may be due to:

  • Accidentally picking Query when creating the column (the UI can be confusing).
  • A bug or a temporary glitch in Glide.
  • Advanced layouts where “Relation” is nested inside a Query column or vice versa.

I have a simple 2 tables - users table and volunteers table, both have email ID column, when I add relation column in users table to connect email from users table and volunteers table email ID and pick type relation, I always see QUERY in the cell, not ROW even though email matches in both tables.


No that is not what it means. That looks like an AI response, which isn’t always accurate. If you see the word ‘Query’ as a clickable value in a cell, that means you are using a Glide Big Table. Big Tables only load data as needed. When viewing in the data editor it will not load the entire contents of the table, and instead show Query for content that loads dynamically. The front end handles this loading automatically as needed, but sometimes you need to click on it manually while in the data editor.

That is normal and expected behavior that will work properly on the front end. If you want to see the value on the back end, just click on Query.

2 Likes

Thanks for the feedback. Could you please advise how to achieve this in my app.

  • User is prompted to enter their email address.
  • The system checks if this email exists in the Volunteers table.
    • If found: Show the volunteer’s existing profile/info for editing.
    • If not found: Show an empty form, allowing the user to submit their details (which creates a new row in Volunteers).
  1. An email entry field.
  2. Conditional logic to display either:
  • The user’s info (for updating), or
  • An empty form (to add a new volunteer).
    Also, how should the relation column be built in the Volunteers table?
    Thanks in advance!

Do users sign into your App?
If they do, then asking for an email address is not necessary, because this is already captured and included in their profile the first time they sign in.