I am using the checkbox collection to add users to lists using. works great. What I also need to do is capture the current time when the checkbox was selected.
Any help appreciate.
A check box or checklist itself can’t call an action, but two thoughts.
- Create an IF column that returns two different images or emojis when the boolean is checked or not. Then use a regular list style for your collection and show the image/emoji. Then change the item click action to be a custom action that sets the boolean to true or false based on if it’s checked or not. Something I do here: Reset Multiple Rows At Once
- Another idea is to use a custom collection with a custom AI component that is a checkbox with an action.
4 Likes
Thanks for the feedback. I am currently using a choice component that displays a relation of the users playlists. my current checkbox list assigns the current item rowId to the rowid of the selected user playlist.
played with the AI. very confusing and I don’t see how to reconfigure what it did. hmmm. Will check the documentation for how to use this component.
Yeah, the AI component takes a lot of trial and error, but when I use it I just have a continuous conversation with it. Start with the initial request, and then keep asking for additional changes.
2 Likes
It wouldn’t get it right out of the box most of the times, but these can help:
- Prompt with an image that represents what you want.
- Use Tailwind vocabulary so the vocabulary you use is “closer to home” for the AI to work with.
- Same for CSS.
2 Likes
Feeling Dense. When I use the choice component - I am able to select where I write the *checkbox data. In my case I am saving the rowId of the current item to a different table.
When I use a *collection, and set column action I don’t see a way to select how to write into another table…
Also - love the way you list the buttons and the title all on one line. I imagine this is custom CSS? (on maker plan so I don’t think I can tweak)
Would it be crazy to request that Glide support custom actions on choice components?
Thanks much
This gets a little tricky. What you need is to somehow create a single relation in the collection source table that links to the row you are trying to update. Then a set column action can set a value through the relation. How that works depends on a few things be generally you would store the RowID of the row you are editing somewhere, then use a single value column to bring it into choice source table, and then create the relation from that. I’m not doing anything like that in my sample app. I’m not really using it like a choice component. Moreso like a checklist style collection.
There is no CSS involved in my example. There are no buttons. Although I am using a classic app (really need to rewrite this as a new app template so it can be copied), it’s just a standard list and I’m just displaying an emoji as an image.
Not at all. This is something that is sorely needed. There’s already at least one request out there.
2 Likes
That makes perfect sense. Dumb question how do i store the rowId of the screen I’m looking at in a temp field? what action triggers - hey store the rowId of the current screen?
on a related note - something I’ve been thinking that would might be helpful - Does the Glide community do any kind of “office hours” with experts or code reviews with each other? I would love to share my screen while I’m building stuff and have others chime in with suggestions/tips/ etc.
Now that I have made many many mistakes I have a better sense of things that noobs likely miss and would be happy to help other noobs in this way
Usually you can store that when opening the screen. If you get there from a collection for example, you can adjust the action to first set a value (maybe into the user profile), followed by showing the screen.
1 Like
Last q of day - you are so helpful. I have a table with rows that are categoried. simple. I have created a query column from users that shows just cat1, or cat2, or cat3 for the user. cool.
I have added the collection 3 times to a screen. first collection using query cat1, second using cat 2, etc.
works great. BUT - when I click into the item the details screen, Glide forces the source to use the same relation column no matter what query is used. I update the collection to use the desired query source but this gets overwritten. so the data for cat 1 for example is listed on ALL three query views. grrrrr.
ideas?
Sounds like it’s the default option for details view. You’re trying to view a details view of an item, but depends on what “query collection item” was clicked, you wanted to display different things?
On entry to the details view, add a step to set the value that determines the “query collection” that was clicked, to a user-specific column.
Drive the visibility of components based on that value.
2 Likes
Correct. When its one type of list I display X propterties in the collection. Y props when its the Y query.
Will give this a shot. thanks so much
1 Like
setting a query as a collection source view then having that selected view overwritten by a “default view” strikes as odd and maybe even a bug. But hey I’m sure there’s a reason for this behavior but it doesn’t make sense to me.
I will make a video of the behavior and share it with the Glide support peeps
I’m not sure what you mean here. Can you explain more?
thanks for the follow up. I used your workaround and this is working. thanks.
1 Like