Lookup not updating when relation changed from single to multiple

[HeartwoodTreeCo]

Team ID:

• In the Glide dashoard URL, e.g.
  https://go.glideapps.com/o/ss3WJJDqbqwlJwQjks9W

App ID:

• In the Glide builder URL, e.g.
  https://go.glideapps.com/app/P9TnCgAIVECR0x8Qnlqk/layout

Description

• I changed this relation from single to multiple.

  

• This lookup column based on the relation was still showing checkboxes, as if it was pulling from a single relationship instead of a multiple

  

• So I re-created the lookup with the same relation and target, and the new column returns multiple values as it should

• 

• Here are the two columns side by side

• 

How to replicate

• Inspect the relation column in the Trips table “Feedback/mrel Trip ID to Feedback”
• Create a new lookup column based on it and pointing to the boolean “Times are accurate”
• Compare the new column to the lookup column in the Trips table “Feedback/look Feedback is complete”

[nathanaelb]

1. You create a single relation.
2. Then edited that single relation and made it multiple.
3. Then you created a separate multiple (with the same settings as the first)
4. They show different results.

Is that correct?

[HeartwoodTreeCo]

Not quite -
3. Created a separate lookup from the same relation

[ThinhDinh]

Please submit a ticket to the support team, thank you!

[nathanaelb]

The original lookup didn’t update? That’s interesting.

[Darren_Murphy]

I’ve observed this behaviour before. I’m not sure if it would be considered a bug or not, and I’ve never tested whether it affects the published App (I suspect it doesn’t). I’ve found that simply reconfiguring any dependant columns usually resolves it in the Data Editor. I would suspect that a browser refresh would do the same.

[HeartwoodTreeCo]

You’re absolutely right, reconfiguring the problem lookup column fixes it. For the record, Support is calling it a limitation, not a bug.

Refreshing the browser (and clearing the cache) did not change the situation, though.
I also tested whether the published app is affected by replicating in a simple app, and the lookups match the data editor, so yes, it does affect the published app.

If I can change the configuration of a column in a way that breaks other columns, without limitations or cautions, and it persists and affects the live version, I’m classifying it as a bug.