Ok thanks Darren, I appreciate you being this helpful. Just a moment…
Okay, that helps.
I can definitely see a problem with your choice component configuration.
You are reading values from the Type column, and writing back to the same column. The result of that is that you’ll be overwriting the existing values.
What you need to do is create a new (user specific) column and have your choice component write to that. You can then use that as a screen filter.
This might not be the whole solution, but it will get you back on the right track.
Also…
1 Like
Thanks Darren. This is definitely a step forward. I am hoping since I have simplified the filter down to only two types that I can find a solution.
I think this is just going to be a whole lot easier to create a quick example for you. Your screenshots are overly redacted, and I’m not sure I understand how you went from one column in the compensation Types table to four columns. I’m not following what Name, A, and B are in a table that should only contain a list of payment types. Since you are changing things that I wouldn’t expect you to change, It’s just hard to get a full visual of how you have everything set up in your app.
Below, I’ve included an example app of how I would do it. I was originally suggesting a simpler filter, but now that I see that you have the “Allow selecting multiple” option selected for your choice component, that changes and complicates things a bit. I’m assuming that you do in fact want to be able to select multiple payment types and filter any sellers that contain at least one of those selected payment types. For that reason, I altered my example to account for that. If that was not what you intended and you only want to filter by one payment type at a time, then let me know, because that is a whole lot easier to set up and explain. I don’t think it’s worth going into too much detail about how I set up the filter for multiple selected payment types. You are better off just copying my example and playing around with it.
2 Likes
Name is the Sellers name, A is payment Type A and B is payment Type B.
“Since you are changing things that I wouldn’t expect you to change, It’s just hard to get a full visual of how you have everything set up in your app.”
-I agree
I have simplified to not needing a select multiple choice since there are only two choices now.
“If that was not what you intended and you only want to filter by one payment type at a time, then let me know, because that is a whole lot easier to set up and explain. I don’t think it’s worth going into too much detail about how I set up the filter for multiple selected payment types”
-This is true now but thanks for sending over because I’d like to if I can in the future. For now, I resorted back to a simple filter
Also, I am using Cards style, does that matter?
I have managed to implement the Select Payment Type column in my Sellers sheet. Now, the app automatically selects all Sellers to display. All i need to do is get my Choice for each Payment Type to filter by Sellers who accept the respective Payment Type. (Working on Tab sheet)
I have configured almost identical to your test app. The only problem I have run into (all else looks good) is that I am unable to Write to Selected Payment Type on the Tab sheet. Instead, the only options I have are the columns from the Sellers list.
That’s because your choice component is on a screen/tab that’s connected to the Sellers table. If the screen is connected to the Sellers table, then that’s the table you are editing when you have editable components on the screen.
So I am unable to use Compensation Types (seperate sheet I created) as the source of my Choice then? Or change the data source for the entire screen?
Do you have any advice since I have migrated to a two options Choice without multi select?
You can use it as the source of your choice, but not as the target.
A choice component can only write to the table that the parent screen is attached to.
1 Like
I know. So the final answer is Users are unable to filter a Details Style screen that has an Inline list of Card style listings?
Yes, of course it’s possible.
I didn’t respond to your second question because I’m leaving that for Jeff. I expect that when he has time he’ll adjust his sample App to use a single choice selection.
Ahh. Ok, thank you, I simplified the app a bit for that reason.
Of course you can. That’s exactly what I’m showing in my example app, so of course it’s definitely possible.
Just forget everything you think you know about the choice component and start fresh. First you have a screen. That screen is attach to a row in a table. I don’t know which row in which table you have chosen, but it sounds like the screen is attached to the Sellers table. Then you have a choice component on that screen. Any choice you you choose will write to a column of your choosing in the Sellers table, because I’m assuming that’s the source table of the screen that your choice component is on.
This is what each setting represents in a choice component:
- Write To: is the column in the source table of the screen.
- Source: is the source table of the choices you want to display in your choice component.
- Values: is the column that contains the values you want to display in the choice component.
- Images: don’t worry about that for now.
- Display As: Use this only if you want to display certain values in your choice component, but actually save the underlying value of the selected choice. Imagine showing a list of names, but saving the underlying row id instead. You don’t need to worry about this setting for now.
I’m not going to change the example app for now. I’m pretty sure that once I do, you’ll end up wanting the multi select anyway. We need to get past how a choice component works first. Plus I’m on vacation this weekend. Read through the documentation and watch the videos I linked to above regarding the Choice Component. It should be pretty straightforward, but I think you’ve made some assumptions about how it works, which is making things confusing.
1 Like
The screen is attached to my Sellers table correct. Then, I chose which row when configuring my inline list. I have definitely fallen into a cave of confusion…I apologize for this. Something I noticed in your app is that you have your screen’s data source as your Tab table while mine is my Sellers sheet…
The screen/tab can be sourced/attached to any table you choose. The inline list can be sourced/attached to the same table or a different table. It’s up to you, but it’s important to differentiate between the two. When I talk about the screen, I’m talking about the whole detail screen, which includes all components on that screen. When I talk about the inline list, I’m talking specifically about the inline list component.
1 Like
It might be helpful to start at the beginning of the documentation to learn the basics. Watch the tutorials. Try some of the examples.
1 Like
Im curious as to how you get the folders to appear. Especially “Filter”.
Hey dont mind this…I am making progress
It’s the naming convention. Name your headings with a slash /. They will become groups.
1 Like