# Issue with filtering relation values **URL:** \ **Category:** Ask for Help\ **Created:** [December 30, 2025, 9:39am UTC](https://community.glideapps.com/t/issue-with-filtering-relation-values/85819 "2025-12-30T09:39:29Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Joas\_MATOTO](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/joas_matoto/32/83225_2.png) [@Joas\_MATOTO](https://community.glideapps.com/u/Joas_MATOTO)\ **Post date:** [December 30, 2025, 9:39am UTC](https://community.glideapps.com/t/issue-with-filtering-relation-values/85819/1 "2025-12-30T09:39:29Z")
Hello Glide Support, I’m experiencing an inconsistency when filtering values that come from a relation. - I have a relation from my current table to the **Facture** table. - From that relation, I pull two columns: **Statut** and **Type de facture**. - When I filter on **Statut** (e.g. “includes en attente”), it works correctly. - But when I try to filter on **Type de facture** (e.g. “includes Facture de deuxième acompte”), the filter refuses to return the expected results. Important details: - In the **Facture** table itself, filtering directly on `Type de facture` works fine. - The problem only appears when I filter on `Type de facture` through a relation in another table. - I have tried different approaches (lookup, template, if‑then‑else, single value), but the issue persists. - Glide sometimes even blocks saving a Single Value column with the error: _“This computed column is not supported on this data source.”_ It seems that `Statut` is treated as a clean, filterable value, while `Type de facture` (even though it comes from the same relation) is not being indexed or recognized properly in queries. Could you please clarify why this difference exists, and whether there is a recommended way to make `Type de facture` filterable through relations, just like `Statut`? Thank you for your help! ---
**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\ **Post date:** [December 30, 2025, 9:55pm UTC](https://community.glideapps.com/t/issue-with-filtering-relation-values/85819/2 "2025-12-30T21:55:12Z")
Based on your description, it sounds like you are using a Glide Big Table which has some limitations including when using computed columns in that big table for filtering. Is the Facture table a Big Table? I’m assuming your Statut column is a basic column, but is your Type de facture column a computed column in the Facture table? If so, the computed column combined with coming from a Big Table would explain why you are having issues. I don’t use big tables, so someone else would have to advise on the best workaround. Basically the problem is that Glide will not process all computed columns in a big table unless necessary, unlike a glide table where it may process all computed columns at once. ---
**Author:** ![Joas\_MATOTO](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/joas_matoto/32/83225_2.png) [@Joas\_MATOTO](https://community.glideapps.com/u/Joas_MATOTO)\ **Post date:** [December 31, 2025, 8:18am UTC](https://community.glideapps.com/t/issue-with-filtering-relation-values/85819/3 "2025-12-31T08:18:27Z")
Hello Glide Support, I’m facing an inconsistency when filtering values from a relation. - My **Facture** table is a large table. - In that table, both **Type de facture** and **Statut** are basic columns (not computed). - When I pull them into another table through a relation + lookup, both values appear correctly. - However, when I use them inside a query: - Filtering on **Statut** works as expected. - Filtering on **Type de facture** refuses to return the correct results. Since both columns are native text fields in the Facture table, I don’t understand why one is accepted in queries while the other is not. Could you clarify why this difference exists, and whether there is a recommended way to make `Type de facture` filterable through relations in the same way as `Statut`? Thank you for your help! ---
**Author:** ![nathanaelb](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nathanaelb/32/43079_2.png) [@nathanaelb](https://community.glideapps.com/u/nathanaelb)\ **Post date:** [December 31, 2025, 9:12am UTC](https://community.glideapps.com/t/issue-with-filtering-relation-values/85819/4 "2025-12-31T09:12:46Z")
Have you seen Jeff’s response to you? Have you tried using the Query column instead of the Relation column? * * * Access-vous remarqué la réponse de Jeff ? Avez-vous essayé la colonne Query à la place de la colonne Relation ? > [@Issue with filtering relation values](https://community.glideapps.com/t/issue-with-filtering-relation-values/85819/2): > > Based on your description, it sounds like you are using a Glide Big Table which had some limitations including when useing committed columns in that big table for filtering. Is the Facture table a Big Table? I’m assuming your Statut column is a basic column, but is your Type de facture column a computed column in the Facture table? If so, the computed column combined with coming from a Big Table would explain why you are having issues. I don’t use big tables, so someone else would have to ad… ---
**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\ **Post date:** [December 31, 2025, 12:36pm UTC](https://community.glideapps.com/t/issue-with-filtering-relation-values/85819/5 "2025-12-31T12:36:44Z")
Can you share some screenshots showing some of the data and showing how you have the filter set up?