I have a problem that looks like a bug with the “choice” component and the “filters”.
My use case is simple: I have a child profile table “Kids” and a table “catalog” of illustrated cards. I what to associate some cards to children profiles as rewards. The “choice” component allows me to enter the row id of a child profile in a column of the table “catalog”. There is a relationship column in the child table that checks if its name is associated with a card, this allows the displayed cards that the child collects to be shown in its own screen and it works well.
However, when I want to add filters to the “choice” component, ie a “number of gold pieces greater than or equal to 20” and “collection column” in the child table does not contain the name of the card", the behavior changes: each choice becomes unique and erases the previous one, even if “allow selecting multiple” is selected."
I really do not understand why filters would be wrong, but even, they seems to change the way the choice is made, from “multiple” to “only one”?
The “choice” component allows me to enter the row id of a child profile in a column of the table “catalog”.
Does a card can be associated to multiples kids?
What it the type of the columns you use for the filters? Especially the collection columns? If it’s only text (“card1,card2”) you have to split it and use this split columns. I think it would work if the issue comes from this of course.
Yes, I can see why. It’s because the column you are trying to filter on is a Lookup that’s returning an array. “Does not contain” only works with strings, not arrays. What you could do is add a Joined List column that targets your Lookup column, and then use that Joined List column in your filter condition.
So you only want to show names that are not already associated with the Thing in question?
If so, the filter on your choice component should be “relation to things is empty”.
I want to hide the child because he already owns this specific thing, as he will have already collected other things.
In this example, once user click on the “Rombi” item, the choice component should only show “Julien” because “Paul” and “Marie” own already “Rombi”. It seems easy, but couldn’t find the filter that do the trick !
I didn’t catch the user experience so maybe it won’t fit your needs, but let us know.
Anyway, I think you would need to add other columns to deal with the ownership thing.
Yes, I am trying to do something similar, but the user ID is the same : user is one parent that may have multiple children. And I want that these children can collect some illustrated cards.
The way I found was this screen with a choice component that write the name (or row id) of the child into the table of cards, so child can have their own separate collection. (I wanted to do that directly from each child 's screen, where a child could just touch a button like “buy this card” to collect the item, but I didn’t success to find a proper for now).
On the app, a user is on the cards list, open one and is directed into the card’s details page
When he clicks on a name (to make it owner) the selected name is added into the card’s owner on the cards table.
Yes. In my simple use case, user is on the “things” list, touch 1 item, that open the page (slide in) with the choice component. the choice component shows the child and write the chosen name into the column “choice component” of the things table. (and it works, but without using the filter).
In the User tab, there is a relation between the User name AND the card owner’s name in the cards tab (split owner’s name)
You then retrieve the names of the name with a lookup in the owned card.
Is that right?
Your choice component has as a data source the users tab right?
If yes my example should work since it’s this exact workflow (or i’m going crazy)
It is not into the user tab, it is into another table “children” :
I’ve made also made several columns into the “things” table to get the information owner/owned in both table, hoping I could use one of them to a find a way to filter :
I would love to see a screen recording, because for now it is not working (and yes I am going crazy as it seems to me like at least 3 filters I tried should work… )
In your kids table, is your “rel with split already owner” match multiple? If not, the data in your lookup will be a text, which is why then in your choice component filter you don’t have the “doesn’t contain”.
Once match multiple selected, reconnect your lookup
)… ?)
!
