Recursive workflows in Bubble (OR, HOW TO LOOP THROUGH A LIST)
Vložit
- čas přidán 27. 08. 2024
- Recursive workflows are a powerful way to make changes to large datasets in Bubble. In this video will learn what they are, and how to set them up.
🎓 For more videos like this, check out my complete Bubble course (45+ hours of lessons) 👉 thinkitbuildit.co
Hi Matt,
Very comprehensive explanation about recursiveness in Bubble. 👏🏻
Instead of counting loops from 1 to n, you could have counted from n to 0. You would not have needed the "count" parameter.
However, there's another way to loop through the list which is, in my opinion, more efficient: in each loop, I process the first item of the user_list parameter, and reschedule the workflow with the user_list's items from #2 (only when the user_list's item#2 is not empty). It only needs 1 parameter, and the list gets smaller with each loop.
This video is like liquid gold. Without Matt, I think my Bubble journey would have stopped many months ago. This dude just changed my life.
Thanks so much, happy to help 😁
Thank you so much, Matt. You are indeed one of the best at teaching and explaining things.
Hi Matt, could you please do a tutorial how to create reports in PDF using a pluggin as PDF conjure, setting up the report fields, styles and fonts based on a thing. Thanks for your well explained classes.
Thanks a lot Matt, you have just explained that in a very simple method.
21:24 Step 2's "only when" condition should switch to "count" variable to save capacity then.
30:45 Looking forward to the Xano comparison video:)
Yes good spot!
You are one of the best things that happened to the bubble community. Love you❤
Thank you very much Matt ! It was clear as source water ! ( french expression )
Thanks for the vid Matt, appreciate you sharing your knowledge.
Thanks Briggsy
Legend! very good video explaining this!!! keep up the good work here!
21:45 pizza shop domino ;)?
only when in api, is index < count yes? not still users:count. ?
Thank you Matt! Very well explained. I managed to follow easily and implement into my app. Thank you, thank you!
Can I use a repeating group with a data type, and some user fillable inputs, to create a different data type data new data with this API Workflow? Here you are changing data of same type, I want to create new data of different type. Many thank again.
Another amazing tutorial video!
THANKSSSSS!
Great video! Love the Miro board
Thanks
Well presented that man! 🎖
Great video; thank you!
Love the thumbnail!
Thanks for the video.
Hi ! Thank your for this video. Why not using schedule API workflow on a list ?
Historically this hasn’t been very performant but Bubble has improved that recently.
Recursion is still good though to control the order of operations (I.e. complete loop 1 before loop 2) whereas if you just run on the list you have no control over that (Bubble will execute them concurrently).
Recommend checking out this part of Bubbles docs manual.bubble.io/help-guides/maintaining-an-application/database-maintenance/bulk-operations#what-are-bulk-operations
great video thanks boss
Hi Matt! Good content
Can be great to explain how to use external database (basically post and get content of the external storage), and respect the privacy rules.
Because bubble storage capacity is very expensive.
Is the same to use aws/wasabi, and external sqls?
sometimes i feel bubble would be alot easier with a simple IF/Else logic rather than a do/when logic. i know its implementation is there but its slightly more workaround-ish. Some of these tasks are actually easier on JavaScript than bubble
I thinks that is the downside of no-code, when you need something complex it becomes very clumpsy or spagetty. Ive used labview no code too before and it seems easy to learn at first but when it gets complicated then it need a lot of visual space to handle loops and conditions.
A hero
Hi Matt, thank you for making this video. I'm building a marketplace. So I need an automated workflow to take down the listing once it hits the expiry date or it's out of stock. My understanding with this technique, I would need a trigger from the actual page whereas I don't want any trigger. I want it to automatically taken down without any trigger. So could I use this as well?
Ive heard Supabase , the new kid on the block is really nice for this. Less expensive than firebase,xano and backendles. Im thinking that even having an external server instance in Replit for example for this type of heavy calculations and then send back via API bubble the results. Or just having a custom JS code in runing in a html event.