00:03 Using Softr's one-click update action buttons makes saving records easier. 01:31 Setting up well-structured data in Airtable is crucial for future tasks. 03:09 Adding favorite functionality in Softr 04:49 Using one-click update to link a temporary user with a record ID 06:34 Link favorite to user and clothing 08:13 Testing and using Softr features 09:56 Conditional filters applied for relevant favorites 11:38 Implementing one-click update for changing status to deleted without actually deleting the record Crafted by Merlin AI.
Hi Dan, thanks for sharing. The solution is very interesting. My suggestion is to trigger airtable automation upon the update of the temporary user field and not delete the content at the end of the "add to favorites" cycle. This way we reduce the risk con concurrent favorites from different users. What you do think?
Hey Dan, thanks, this is quite helpful. Did I miss something , as my related detailed list pages that refer to the item fields in the favorite list block don't open as their content actually comes from another table in airtable?
Hey Dan, Thanks for the video! My problem with this approach is that there are just way too many combinations of items and users then. If I have 6,000 users liking 10,000 different jobs, this table will get massive. Have you come across any way of doing this that doesn't require an extra table? I'm trying to save the records directly via the one-click update button. That works as long as two users don't save the same item at the same time, I have not figured out how to circumvent that issue. Would be really curious to hear if there are different approaches :) Thanks so much!
Yeah, Airtable record limits always seem to be an issue ;) Perhaps you could do a straight N:N relationship between the record and the user? Not necessarily the best architecture, but could possibly get the job done. You'd still have to temporarily store the record ID and then append it to the list of favorited objects for that user. Deleting favorites might get a little tricky.
How do I use the one-click feature if users unfavorite a resource one day then the next day would like to favorite the same resource? The way you have it setup if the person unfavorites a resource they are unable to like it again
Hi I just figured this out. In softr, create a visibility condition for the favorite button. Make it such that if the logged in user's email is in your products table (remember Airtable automatically creates a linked field back to your favorites table) then the button should be hidden. This will make the button disappear once a user likes something.
@@Lanseninsane Hey Dan, thank for that great video! I’m interested in the idea to let the button disappear in case a user clicks on it. I didn’t get you description well. Would you be so kind and specify?
00:03 Using Softr's one-click update action buttons makes saving records easier.
01:31 Setting up well-structured data in Airtable is crucial for future tasks.
03:09 Adding favorite functionality in Softr
04:49 Using one-click update to link a temporary user with a record ID
06:34 Link favorite to user and clothing
08:13 Testing and using Softr features
09:56 Conditional filters applied for relevant favorites
11:38 Implementing one-click update for changing status to deleted without actually deleting the record
Crafted by Merlin AI.
Hi Dan, thanks for sharing. The solution is very interesting. My suggestion is to trigger airtable automation upon the update of the temporary user field and not delete the content at the end of the "add to favorites" cycle. This way we reduce the risk con concurrent favorites from different users. What you do think?
Hey Dan, thanks a lot for this! would be great if Softr can add a feature for one-click add record or one-click create for this
Hey Dan, thanks, this is quite helpful. Did I miss something , as my related detailed list pages that refer to the item fields in the favorite list block don't open as their content actually comes from another table in airtable?
Hey Dan,
Thanks for the video!
My problem with this approach is that there are just way too many combinations of items and users then. If I have 6,000 users liking 10,000 different jobs, this table will get massive.
Have you come across any way of doing this that doesn't require an extra table?
I'm trying to save the records directly via the one-click update button. That works as long as two users don't save the same item at the same time, I have not figured out how to circumvent that issue. Would be really curious to hear if there are different approaches :)
Thanks so much!
Yeah, Airtable record limits always seem to be an issue ;)
Perhaps you could do a straight N:N relationship between the record and the user? Not necessarily the best architecture, but could possibly get the job done. You'd still have to temporarily store the record ID and then append it to the list of favorited objects for that user. Deleting favorites might get a little tricky.
How do I use the one-click feature if users unfavorite a resource one day then the next day would like to favorite the same resource? The way you have it setup if the person unfavorites a resource they are unable to like it again
How did you create the formula for the name in the favourites table?? I can't figure it out and I am sure it's the missing piece.
I can't get this system to work can you help me?
Thanks for your kind video. But I've failed again and again. If possible, can you share your DB table template and Softr Template?
Hey, there's a better way to do this now with one click updates. The video is coming out next week
How’s the fit on those Super Novas?? 🍺🍻🍻
Hahaha, can't say you'd catch me wearing them in real life 🤣
This is so helpful! Is there a way to have a user share their page of favorites with friends?
I plan on creating a video on sharing a "wish list" of sorts, like Amazon? Think that will hit the mark of what you're looking for?
Hey Dan, how do I make it so that a user can't like an article more than once?
Hi I just figured this out. In softr, create a visibility condition for the favorite button. Make it such that if the logged in user's email is in your products table (remember Airtable automatically creates a linked field back to your favorites table) then the button should be hidden. This will make the button disappear once a user likes something.
@@Lanseninsane Hey Dan, thank for that great video! I’m interested in the idea to let the button disappear in case a user clicks on it. I didn’t get you description well. Would you be so kind and specify?